ERD from above us see some of the shortfall on:

1. PUNYA on the relationship between the entities with the entity PROJECT PART cardinalities not yet complete, the entity has not been there cardinalities PROJECT
2. The occurrence of the Ternary PUNYA relationship between the entities that connect with the dependent entity PROJECT, which is where it does not have any relationship, so that the base of an over ERD  can be corrected as follows:

ERD from above normalization can be generated as below:

Description:
The table above forms because:

• First, if there is a relation 1-N key on the primary entity with cardinalities 1 will be a foreign key in the entity with cardinalities N
• Second, if there is a relation such as the MN relation KERJA into the new table with the primary key of the second entity.
• Third, if there is a relation such as the 1-1 relation PIMPIN then select cardinalities entity with the most high place and become a primary key foreign key
• Fourth, if there is a dependent relationship of the table primary key will be derived from the parent entity

So that the table above has formed 3NF because the dependence of field-field primary key should not be absolute (full dependent). This means there must be no transitive dependency

NORMALIZATION
The design database is required, so that we can have a database of compact and efficient in the use of storage space, quick and easy in the initialization manipulation (add, change, delete) data.

Database design process

Gather user needs / business, Develop a needs-based ER Model user / business, Convert E-R model to the set of relations (tables) normalize relations, to remove anomalies, Implemented to create a database with a table for each relationship that is normalize

DATABASE NORMALIZATION

Normalization process is the establishment of the database structure so that most of the ambiguity can be removed. The process of normalization is the process of grouping data elements into a table-table and show relationship entity. In the process of normalization is always tested in some cases, if there are difficulties at the time to add / insert, delete / delete, change / update, and read / retrieve on a Database

Normalization stage, starting from the most mild (1NF) to most stringent (5NF) usually only reach the level of 3NF or BCNF because already sufficient to generate the table-a table of good quality.

Normalization must be done because:

• · Optimization table structures
• · Increase the speed
• · Eliminate income data the same
• · More efficient use of storage media
• · Reduce redundancy
• · Avoiding anomalies (insertion anomalies, deletion anomalies, update anomalies).
• · Improved data integrity

A table saying good (efficient) or if the normal 3 to meet the following criteria:

• · If there is decomposition (decomposition) table, it must be guaranteed safe decomposition (Lossless-Join Decomposition). That is, after the table is described a new table-table, the table-table can generate a new table with the same exact.
• · Maintain the functional dependence on the change data (Dependency preservation).
• · Not violate Boyce-Code Normal Form (BCNF)

If the three criteria (BCNF) can not be met, then at least the table does not violate the Normal Form of the third stage (3rd Normal Form / 3NF).

FUNCTIONAL DEPENDENCY

Functional Dependency describes a relationship attributes in relation
An attribute said functionally dependant on the other, if we use the value attribute to determine the value of the other attributes.

Are used to specify formal measures of the “goodness” of relational designs And keys are used to define normal forms for relations, Are constraints that are derived from the meaning and interrelationships of the data attributes. A set of attributes X functionally determines a set of attributes Y if the value of X determines a unique value for Y. X -> Y holds if whenever two tuples have the same value for X, they must have the same value for Y, For any two tuples t1 and t2 in any relation instance r(R): If t1[X]=t2[X], then t1[Y]=t2[Y]. X -> Y in R specifies a constraint on all relation instances r(R), Written as X -> Y; can be displayed graphically on a relation schema as in Figures. (Denoted by the arrow FDs are derived from the real-world constraints on the attributes

Examples of FD constraints

• · Social security number determines employee name

o SSN -> ENAME

• · Project number determines project name and location

o PNUMBER -> {PNAME, PLOCATION}

• · Employee ssn and project number determines the hours per week that the employee works on the project {SSN, PNUMBER} -> HOURS

• · An FD is a property of the attributes in the schema R
• · The constraint must hold on every relation instance r(R)
• · If K is a key of R, then K functionally determines all attributes in R

o (since we never have two distinct tuples with t1[K]=t2[K])

FD’s are a property of the meaning of data and hold at all times: certain FD’s can be ruled out based on a given state of the database

Inference Rules for FDs

• · Given a set of FDs F, we can infer additional FDs that hold whenever the FDs in F hold

• · Armstrong’s inference rules:

o IR1. (Reflexive) If Y subset-of X, then X -> Y

o IR2. (Augmentation) If X -> Y, then XZ -> YZ

§ (Notation: XZ stands for X U Z)

o IR3. (Transitive) If X -> Y and Y -> Z, then X -> Z

• · IR1, IR2, IR3 form a sound and complete set of inference rules

o These are rules hold and all other rules that hold can be deduced from these

• · Some additional inference rules that are useful:

o Decomposition: If X -> YZ, then X -> Y and X -> Z

o Union: If X -> Y and X -> Z, then X -> YZ

o Psuedotransitivity: If X -> Y and WY -> Z, then WX -> Z

• · The last three inference rules, as well as any other inference rules, can be deduced from IR1, IR2, and IR3 (completeness property)

• · Closure of a set F of FDs is the set F⁺ of all FDs that can be inferred from F
• · Closure of a set of attributes X with respect to F is the set X⁺ of all attributes that are functionally determined by X
• · X⁺ can be calculated by repeatedly applying IR1, IR2, IR3 using the FDs in F

Equivalence of Sets of FDs

• · Two sets of FDs F and G are equivalent if:

o Every FD in F can be inferred from G, and

o Every FD in G can be inferred from F

o Hence, F and G are equivalent if F⁺ =G⁺

• · Definition (Covers):

o F covers G if every FD in G can be inferred from F

§ (i.e., if G⁺ subset-of F⁺)

• · F and G are equivalent if F covers G and G covers F

• · There is an algorithm for checking equivalence of sets of FDs

Minimal Sets of FDs

• · A set of FDs is minimal if it satisfies the following conditions:

1. Every dependency in F has a single attribute for its RHS.

2. We cannot remove any dependency from F and have a set of dependencies that is equivalent to F.

3. We cannot replace any dependency X -> A in F with a dependency Y -> A, where Y proper-subset-of X ( Y subset-of X) and still have a set of dependencies that is equivalent to F.

• · Every set of FDs has an equivalent minimal set

• · There can be several equivalent minimal sets
• · There is no simple algorithm for computing a minimal set of FDs that is equivalent to a set F of FDs
• · To synthesize a set of relations, we assume that we start with a set of dependencies that is a minimal set

4. E.g., see algorithms 11.2 and 11.4

Computing the Minimal Sets of FDs

We illustrate the above algorithm with the following:

Let the given set of FDs be E : {B → A, D → A, AB → D}.We have to find the minimum cover of E.

• · All above dependencies are in canonical form; so we have completed step 1 of Algorithm 10.2 and can proceed to step 2. In step 2 we need to determine if AB → D has any redundant attribute on the left-hand side; that is, can it be replaced by B → D or A → D?
• · Since B → A, by augmenting with B on both sides (IR2), we have BB → AB, or B → AB (i). However, AB → D as given (ii).
• · Hence by the transitive rule (IR3), we get from (i) and (ii), B → D. Hence AB → D may be replaced by B → D.
• · We now have a set equivalent to original E , say E′ : {B → A, D → A, B → D} No further reduction is possible in step 2 since all FDs have a single attribute on the left-hand side.
• · In step 3 we look for a redundant FD in E′. By using the transitive rule on B → D and D → A, we derive B → A. Hence B → A is redundant in E’ and can be eliminated.
• · Hence the minimum cover of E is {B → D, D → A}.

Normalization of Relations

• · Normalization:

o The process of decomposing unsatisfactory “bad” relations by breaking up their attributes into smaller relations

• · Normal form:

o Condition using keys and FDs of a relation to certify whether a relation schema is in a particular normal form

• · 2NF, 3NF, BCNF

o based on keys and FDs of a relation schema

• · 4NF

o based on keys, multi-valued dependencies : MVDs; 5NF based on keys, join dependencies : JDs (Chapter 11)

o Additional properties may be needed to ensure a good relational design

Practical Use of Normal Forms

Normalization is carried out in practice so that the resulting designs are of high quality and meet the desirable properties The practical utility of these normal forms becomes questionable when the constraints on which they are based are hard to understand or to detect, The database designers need not normalize to the highest possible normal form

· (usually up to 3NF, BCNF or 4NF)

Denormalization is The process of storing the join of higher normal form relations as a base relation—which is in a lower normal form

Definitions of Keys and Attributes Participating in Keys

A superkey of a relation schema R = {A1, A2, …., An} is a set of attributes S subset-of R with the property that no two tuples t1 and t2 in any legal relation state r of R will have t1[S] = t2[S], A key K is a superkey with the additional property that removal of any attribute from K will cause K not to be a superkey any more. If a relation schema has more than one key, each is called a candidate key.

• · One of the candidate keys is arbitrarily designated to be the primary key, and the others are called secondary keys.

A Prime attribute must be a member of some candidate key, A Nonprime attribute is not a prime attribute—that is, it is not a member of any candidate key.

First Normal Form (1NF)

• · Disallows

o composite attributes

o multivalued attributes

o nested relations; attributes whose values for an individual tuple are non-atomic

• · Considered to be part of the definition of relation

Normalization into 1NF

Normalization of nested relations into 1NF

Second Normal Form

Uses the concepts of FDs, primary key

• · Definitions

o Prime attribute: An attribute that is member of the primary key K

o Full functional dependency: a FD Y -> Z where removal of any attribute from Y means the FD does not hold any more

• · Examples:

o {SSN, PNUMBER} -> HOURS is a full FD since neither SSN -> HOURS nor PNUMBER -> HOURS hold

o {SSN, PNUMBER} -> ENAME is not a full FD (it is called a partial dependency ) since SSN -> ENAME also holds

• · A relation schema R is in second normal form (2NF) if every non-prime attribute A in R is fully functionally dependent on the primary key

• · R can be decomposed into 2NF relations via the process of 2NF normalization

Normalizing into 2NF and 3NF

Third Normal Form

• · Definition:

o Transitive functional dependency: a FD X -> Z that can be derived from two FDs X -> Y and Y -> Z

• · Examples:

o SSN -> DMGRSSN is a transitive FD

§ Since SSN -> DNUMBER and DNUMBER -> DMGRSSN hold

o SSN -> ENAME is non-transitive

§ Since there is no set of attributes X where SSN -> X and X -> ENAME

• · A relation schema R is in third normal form (3NF) if it is in 2NF and no non-prime attribute A in R is transitively dependent on the primary key

• · R can be decomposed into 3NF relations via the process of 3NF normalization

• · NOTE:

o In X -> Y and Y -> Z, with X as the primary key, we consider this a problem only if Y is not a candidate key.

o When Y is a candidate key, there is no problem with the transitive dependency .

o E.g., Consider EMP (SSN, Emp#, Salary ).

§ Here, SSN -> Emp# -> Salary and Emp# is a candidate key.

Normal Forms Defined Informally

· 1^st normal form

o All attributes depend on the key

· 2^nd normal form

o All attributes depend on the whole key

· 3^rd normal form

o All attributes depend on nothing but the key

Successive Normalization of LOTS into 2NF and 3NF

SUMMARY OF NORMAL FORMS based on Primary Keys

General Normal Form Definitions (For Multiple Keys)

· The above definitions consider the primary key only

· The following more general definitions take into account relations with multiple candidate keys

· A relation schema R is in second normal form (2NF) if every non-prime attribute A in R is fully functionally dependent on every key of R

· Definition:

o Superkey of relation schema R – a set of attributes S of R that contains a key of R

o A relation schema R is in third normal form (3NF) if whenever a FD X -> A holds in R, then either:

§ (a) X is a superkey of R, or

§ (b) A is a prime attribute of R

· NOTE: Boyce-Codd normal form disallows condition (b) above

BCNF (Boyce-Codd Normal Form)

· A relation schema R is in Boyce-Codd Normal Form (BCNF) if whenever an FD X -> A holds in R, then X is a superkey of R

· Each normal form is strictly stronger than the previous one

o Every 2NF relation is in 1NF

o Every 3NF relation is in 2NF

o Every BCNF relation is in 3NF

· There exist relations that are in 3NF but not in BCNF

· The goal is to have each relation in BCNF (or 3NF)

Boyce-Codd Normal Form

A relation TEACH that is in 3NF but not in BCNF

Achieving the BCNF by Decomposition

· Two FDs exist in the relation TEACH:

o fd1: { student, course} -> instructor

o fd2: instructor -> course

· {student, course} is a candidate key for this relation and that the dependencies shown follow the pattern in Figure 10.12 (b).

o So this relation is in 3NF but not in BCNF

· A relation NOT in BCNF should be decomposed so as to meet this property, while possibly forgoing the preservation of all functional dependencies in the decomposed relations.

o (See Algorithm 11.3)

· Three possible decompositions for relation TEACH

o {student, instructor} and {student, course}

o {course, instructor } and {course, student}

o {instructor, course } and {instructor, student}

· All three decompositions will lose fd1.

o We have to settle for sacrificing the functional dependency preservation. But we cannot sacrifice the non-additivity property after decomposition.

· Out of the above three, only the 3rd decomposition will not generate spurious tuples after join.(and hence has the non-additivity property).

· A test to determine whether a binary decomposition (decomposition into two relations) is non-additive (lossless) is discussed in section 11.1.4 under Property LJ1. Verify that the third decomposition above meets the property.

Reference : Modul_FD_dan_Normalisasi_B_Ina, Elearning UI

ENACh10_revised_sham_July13, Elearning UI

Part 6 – NORMALISASI, Agus Sanjaya

Definition of the database:

A set of data stored in the magnetic disk, optical disk or other secondary storage, collection of integrated data-related data of an enterprise (company, government or private)
for example:

Manufacturing companies have data in form production planning data actual production data material ordering data

The hospital has a patient data form of data, doctor, nurse, etc.

DATABASE MANAGEMENT SYSTEM

Definition

Collection / database combined with software applications that are based database Application programs are used to access and maintain databases The main purpose DBMS is to provide an environment that is efficient and easy to use, withdrawal and storage of data and information BIT, BYTE, Field Data bit is the part that contains the smallest value of 0 or 1 Byte is a set of bit-bit similar with the same 1 byte with 8 bits Field is a set of byte-byte similar, in the database used the term attribute

ER DIAGRAM COMPONENTS

Attribute / Field

It is the nature or characteristics of an entity that provides provide detail on these entities.
One entity will have specific values for each attribute. Each attribute has a set of values associated with it. This value is a set of data types, such as integer, string, and the other, And can also be given a certain range,

For example, an employee has a name, SSN, address, gender, date of birth.
A relationship can also have attributes

Type-Type Attribute

Single vs. multi value

Single

can only be filled at most one value

Example: SSN, Sex.

Multi value

can be filled with more than one value with the same type of

Example:
Color of a CAR

stated in the multi value: (color),

Atomic vs. composition

Atomic
can not be divided into the attributes of smaller

Composition
is a combination of several attributes of a smaller

Example:
Address (Apt #, House #, Street, City, State, Zip Code, Country)

Derived attribute

Attribute value can be derived from other attribute values, e.g. age resulting from the date of birth attribute

Null Value attribute

Attributes that have no value to a record attribute can have a null value if:

Mandatory attribute Value

Attributes must have values

RECORD / TUPLE

It is a line of data in a relationship Consists of the set of attributes where the attribute-attribute-attribute is to inform each other entity / relationship fully Record is a collection of field-field is structured in a format that has been determined. During the design of the system, records will be classified as fixed-length records or variable-length record.

Entity / FILE

File is a collection of similar records and have the same elements, the same attributes but different data value. A entities is an “object” (thing) or “object” (object) in the real world that
can be distinguished from all other objects. Entity sets are a set of entities
have the same type. This type of similarity can be seen from the attribute / property that
owned by the individual entities. E.g., group of people who save money on a

File Type

In processing applications, files can categorized as follows:

• Master File
• Transaction File
• File Report
• File History
• File Protection
• Job File

DOMAIN
Domain is the set of values that are allowed to reside in one or more attributes. Each attribute in a database relational is defined as a domain

KEY DATA ELEMENT

Key elements of record which is used to find these records at the time of access, or can also be used to identify each entity / record / line.

Elections key attributes:

Key is an attribute that does not change

Example: SSN, employee_ID, SKU (stock-keeping-units), license plate number.

Key values cannot be null, must have a valid value

Example: Date of students is a bad choice to be a key. Avoid the key that has a certain intelligence or codes built in

Examples: building codes (which can be changed later)

SPECIES OF KEY

Super key is one or more attributes of a table that can be used to identify entity / record of the table are unique (not all attributes can be super key) Candidate Key is a super key with minimal attributes. Candidate must not contain a key attribute of the table so that the other candidate key is certain super key but not necessarily vice versa Primary Key One of the key attributes of the candidate can be selected / specified a primary key with the three

Following criteria:

1. Key is more natural to use as reference
2. Key is more simple
3. Key is guaranteed unique

Alternate Key is an attribute of the candidate key is not selected to be primary key.
Foreign Key is any attribute that point to the primary key in another table. Foreign key will be going on a relationship that has cardinalities one to many (one to many) or many to many (many to many). Foreign key is usually always put on the table that point to many.
External Key is a lexical attribute (or set of lexical attributes) that values are always identifying an object instance.

ERD (ENTITY RELATIONSHIP DIAGRAM)

ERD is a model of a network that uses word order is stored in the abstract system. ERD is a model to explain the relationship between data in the database objects based on the data base that has the relation between relations. ERD for data model structures and relationships between data, to describe used for some notation and symbols. Basically there are three symbols that are used

Entity
In the ER Diagram Entity is described with the form of a rectangle. Entity is something that exists in the real system and the abstract where the data stored or where there are data.
Example

Individuals : employees, customers, students, and distributor.

1. Place: room, building, office, field, campus.
2. Object: books, motorcycles, software packages, products
3. Event: registration, reservation, billing
4. Concept: bank account, and qualification.

Relationship
ER diagram on the relationship can be described with a lozenge. Relationship is a natural relationship that occurs between entities. In general, the name given to the verb base making it easier to do the reading relation. A relationship connecting the two / more different entity with a specific meaning.

Relationship Degree

is the number of entities participating in a relationship. Degree which is often used in the ERD.

Degree of relationship

Unary Relationship

Model is the relationship between the entities originating from the same entity set.

Binary Relationship

Model is the relationship between 2 entities.

Ternary Relationship

is relationships between the instances of 3 types of entities are unilateral.

Cardinalities
Tupel indicates the maximum number that can be relation with entities on the other entity
There are 3 cardinalities relations, namely

One to One:

Relationship one to one relationship that each entity in a set of entities associated with at most one entity in the collective entity B.

One to Many or Many to One:

Each entity in a set of entities can be related to many entities in entity set B, but each entity in the entity B can be associated with one entity on the collective entity A.

Many To Many:

Each entity in a set of entities can be associated with many entities on the collective entity B.

Refrence :  Y .Primashanti Ida Ayu, Catatan Kuliah Analisis dan Perancangan Sistem.pdf

DATABASE and ER-DIAGRAM persentation of NGURAH AGUS SANJAYA ER, S.KOM,

]]> http://goesarymanuaba.wordpress.com/2009/04/17/database-and-er-diagram/feed/ 0 goesarymanuaba multivalue compution derived relasi-unary unary treenary 1on1 1onm-copy m-to-n http://goesarymanuaba.wordpress.com/2009/04/15/menambahkan-widget-ubuntu-rilis-pada-wordpress/ http://goesarymanuaba.wordpress.com/2009/04/15/menambahkan-widget-ubuntu-rilis-pada-wordpress/#comments Wed, 15 Apr 2009 10:43:28 +0000 goesarymanuaba http://goesarymanuaba.wordpress.com/?p=108 ]]> Mungkin anda sudah pernah mencoba menambahkan widget countdown rilis ubuntu ke dalam wordpres anda dan al hasil script yang anda copi tidak bisa muncul. hal ini disebabkan karena wordpress tidak mengijinkan kita untuk memasang javasricpt selain vendor-vendor yang sudah bekerjasama dengan wordpress.

Tapi hal itu bisa kita akalin dengan cara menredirect linknya alias convert ke HTML nah ini codenya

<a href="http://www.ubuntu.com/"><img src="http://www.gelora-batam.org/nano/ubuntu_cdown.php?j=1" alt="Ubuntu: For Desktops, Servers, Netbooks and in the cloud" width="180" border="0" height="150" /></a>

<a href="http://www.ubuntu.com/"><img src="http://www.gelora-batam.org/nano/ubuntu_cdown.php?j=2" alt="Ubuntu: For Desktops, Servers, Netbooks and in the cloud" width="180" border="0" height="150" /></a>

nah sekarang silakan masukan code di atas pada widget wordpress anda… sealamat mencoba

sebenarnya saya mau sedikit curhat tentang XL UNLIMITED yang saya gunakan. pertama saya mengenal layanan ini adalah dari forum2 di internet, pada saat itu tepat sebulan yang lalu saya membaca sebuah forum yang berisikan tentang cara mendaftar XL UNLIMITED, tanpa berfikir panjang saya langsung membeli SP XL yang pada saat itu hargana cuma 4rb perak, dan langsung topup pulsana dengan 100rb+10rb, karena menurut forum pulsa minimal untuk aktifasi XL ini adalah 110rb. pada saat itu saya sangat senang sekali karena ingin cepet bisa aktivasi XLnya, sesampaina di KOS yang letaknya di dekat sawah yang sejuk dan asri heheheh berlebihan kayakna hehe.. nah langsung saya mengikuti intruksi dari forum yang sebelumna sudah saya save ke FD saya. langkah2 kurang lebih seperti di bawah ini

1. aktivasi SP XL dengan data yang lengkap
2. TOPUP sampai pulsana minimal 110rb
3. aktivasi XL UNLIMTED, untuk proses aktivasi ini ada 2 cara yaitu melalui sms dan langsung ke *868#
4. untuk aktivasi sms anda bisa mengirimkan sms ke 868 dengan format XLDAY30,XLDAY7,XLDAY1, angka di belakang mengindikasikan hari aktifasina.
5. untuk yang *868# hanya tersedia untuk 30hr saja, tetapi ini lebih mudah karena kita hanya mengikuti perintah2 yang sudah ada. setelah selesai aktivasi maka kartu anda tidak bisa langsung di digunakan disebabkan kita harus mengatur terlebih dahullu APN,USERNAME dan passwordna denngan format seperti di bawah ini
6. APN : www.xlgprs.net, UNAME: xlgprs, PSSWD : proxl

ok kita lanjut lagi ke cerita hehehe (seneng banget si cerita) nah sesudah saya berhasil koneksi sayapun mulai browsing ke internet, saya sangat terbantu sekali dengan adanya internet ini, coz gk susah2 saya ke warnet…………….nah singkat cerita setalah berjalan 20hr saya membaca tentang XL UNLIMITED sudah di tutup, denger hal tersebut saya langsung menghubungi 817 untuk mencari penjelasan dan hal hasil ternyata memang benar tetapi sedihnya lagi langganan saya tidak bisa diperpanjang lagi, begitu kata OP XLnya,

dan setelah 30hr saya nekat TOUP pulsa XL dengan yang 100rb dan pas jam 24wib pulsa saya dikurangi 99rb dan sayapun masih bisa menggunakan XL UNLIMITED sampai sekarang. hehehehheheheh

TETAPI XL MASIH BELUM SIAP DENGAN program ini karena SP KHUSUS INTERNET UNLIMITED BELUM SAMPAI DI BALI, disisi lain ini sangat menguntungkan saya karena trafic masih sepi hahahahahahahahahhahaha

DFD is a logical data model or process that is made to describe the origin of the data and the destination where the data out of the system, where data is stored, the process that produces the data and the interaction between the data stored and the process is imposed on data.
DFD are often used to describe a system that already exists or the new system will be developed logically without considering the physical environment where the data flows, or where data are stored.

DFD is a tool that is used in the system development methodology is structured. Excess primary data flow approach, namely:

1. Freedom from the implementation of technical systems.

2. Understanding more about the relation to one another in the system and subsystem.

3. Communicate knowledge of the system with the user through the data flow diagram.

4. Analyzing the proposed system to determine whether the data and processes required are defined.

Besides, there are additional advantages, namely:

1. Can be used as a useful exercise for analyst, so it can better understand the relation to one another in the system and subsystem.

2. Differentiate the system from the environment by placing boundaries.

3. Can be used as a device to interact with users.

4. Allows analyst describe each component used in the diagram.

CONTEXT DIAGRAM

Type the first Context diagram, data flow diagram is the top level (Top Level DFD), the diagram is not the most detail, from an information system that describes the stream-flow data in and outside the system and to the outside and to external entities. (CD describes the system in a loop and relationships with outside entities. Circle shows that the overall process in the system).
Some of the things that must be considered in drawing a CD:

· * Terminology system:

· – Delivery System is a line between “the interests of the system”.

· – Environmental System is all things that relate or affect the system.

· – Interface is the flow of a system that connects with a circle system.

· * Using a symbol of the process,

Note:
The entry in the context of the circle (the symbol) is an activity information processing (Delivery System). Activity is taking information from the data file, transform data, or doing filing data, such as preparing documents, enter, check, classifying, organize, sort, calculate, summarize data, perform filing and data (either manually or do that would be conducted terotomasi ).

· * The name / description of symbols in the process according to the functions of the system.

· * Between External Entity / Terminator is not allowed direct communication

· * If there are terminator that have many inputs and outputs, are described for more than one so that to prevent the drawing is too complex, with a sign asterisk (*) or cross-line (#).

· * If the Terminator represents individuals (personnel) should be represented by the role that these ridiculed personnel.

· * Flow of data to process and output information as the outgoing flow of data is different.

ZERO DIAGRAMS

· Describe the process of the DFD

· Provide views on the overall system in which, showing the main function or process that is, the flow of data and entity sterna

· At this level of data storage possible

· For processes that do not specified again on the next level then added the symbol ‘*’ or ‘P’ at the end of the process

· input and output balance (balancing) between 0 to diagram context diagram should be maintained

LEVELED DFD

DETAILED DIAGRAM

• It is a process diagram that decipher what is in the diagram zero level or above
• numbering level in the DFD:
• 

• In the one level there should be no more than 7 units and the maximum of 9, when more should be done in the decomposition

SPECIFICATION PROCESS

• Each process in the DFD must have a specification process

• At the top level method is used to describe the process can use a sentence with descriptive

• On a more detailed level, namely on the bottom (functional primitive) requires specification of a more structured

• specification process will be the guideline for the programmer to make this program (coding)

• Methods used in the specification process: the process of disintegration in the form of a story, decision table, decision tree

ON FOREIGN

• Something that is outside the system, but it provides data in the system or to provide data from the system

• Symbolized with the notation

• External entity not part of the system including

• Naming:

· The name of the form of noun

· Terminal may not have the same name except the object same

DATA FLOW

• It is a place to flow information

• Described the straight line that connects the components of the system

• Flow data is shown with the direction arrows and the name on the flow of data that flows

• Flow data flow between processes, data storage and data flow indicates that the form of data input for the system

• Guidelines of the name:

• Name of the flow of data that consists of some words associated with the flow lines connect

• No flow data is the same name and the name should reflect its content

• Flow of data that consists of several elements can be expressed with the group element

• Avoid using the word ‘data’ and ‘information’ to give a name to the flow of data

• the extent possible the flow of data is complete

• Terms of others:

§ Name of the flow of data into a process may not be the same as the name of the data flow out of the process

§ Data flow into or out of data storage does not need to be given a name if:

· Flow of data simple and easy to understand

· Flow of data describes all data items

· No flow data from the terminal to the data storage, or vice versa because the terminal is not part of the system, the relationship with the terminal data storage must be through a process

PROCESS

• The process is what is done by the system

• The process can process data flows or data entry into the flow of data out

• The transform function of one or more of data input into one or more of the output data in accordance with the desired specifications

• Each process has one or more inputs and produce one or more output

• The process is also often called bubble

• Guidelines of the process:

§ Name of the process consists of a verb and noun, which reflects the function of the process

§ Do not use the process as part of the name of a bubble

§ There may be some process that has the same name

§ The process should be given a number. Order number wherever possible to follow the flow of the process or sequence, but the sequence number does not mean that the absolute is a process in chronological order

DATA STORAGE

• Data storage is a storage place for data that exists in the system. Symbolized with a pair of parallel lines or two lines with one of the side open, process can retrieve data from or provide data to the database
• Guidelines of the name:

§ The name should reflect the data storage

§ If the name more than one word must be marked with the number

DFD SYMBOL

DATA DICTIONARY

• Working to help the system to interpret the application in detail and organize all elements of the data used in the system precisely so that the system analyst and have a basic understanding of the same input, output, storage and process
• At the analysis stage, the data dictionary is used as a means of communication between the systems analyst with the
• At the system design, data dictionary is used to design input, reports and databases
• Flow data on the global DAD, further details can be seen in the data dictionary
• load the data dictionary as follows:
  • Name of the data flow: must note that readers who need further explanation about a flow of data can find it easily
  • Alias: alias or other name of the data can be written when there is
  • The form of data: used to segment the data dictionary to use when designing the system
  • Flow data: indicates from which data flows and where the data
  • Description: provides an explanation about the meaning of the data flow

Sample data dictionary:

BALANCING IN THE DFD

• Flow of data into and out of a process must be the same as the flow of data into and out of the details of the process on the level / levels below
• Name of the data flow into and out of the process must match the name of the flow of data into and out of the details of the process
• Number and name of an entity outside the process must be equal to the number of names and entities outside of the details of the process
• The issues that must be considered in the DFD which have more than one level:
  • There should be a balance between input and output of one level and next level
  • Balance between level 0 and level 1 at the input / output of stream data to or from the terminal on level 0, while the balance between level 1 and level 2 is seen on the input / output of stream data to / from the process concerned
  • Name of the flow of data, data storage and terminals at each level must be the same if the object same

RESTRICTIONS IN DFD

• Flow data may not be from outside the entity directly to other outside entities without going through a process

• Flow data may not be from the savings directly to the data to outside entities without going through a process

• Flow data may not be saving the data directly from the savings and other data without going through a process

• Flow of data from one process directly to the other without going through the process of saving data should / be avoided as much as possible

Reference :

NGURAH AGUS SANJAYA ER, S.KOM, M.KOM, Slide Persentation DFD

Pengembangan Sistem Informasi, 1998. Leman, PT Elex Media Komputindo, Jakarta

Pengantar Sistem Informasi Bisnis, 1995. Lani Sidarta, PT Elex Media Komputindo, Jakarta

]]> http://goesarymanuaba.wordpress.com/2009/04/03/data-flow-diagram-dfd-quiz-5/feed/ 0 goesarymanuaba levelisasi-dfd1 penomoran simbol kamus-data http://goesarymanuaba.wordpress.com/2009/03/27/analysis-and-design-information-system-fourth-quiz/ http://goesarymanuaba.wordpress.com/2009/03/27/analysis-and-design-information-system-fourth-quiz/#comments Fri, 27 Mar 2009 10:53:45 +0000 goesarymanuaba http://goesmvn.oggix.org/2009/03/27/analysis-and-design-information-system-fourth-quiz/ ]]>

Problem (problem) is gap between the goal system and the actual system conditions, with the understanding why other systems failed to achieve the goals that the system has been determined previously. To know the things that have been what caused the failure of the system, the analyst should conduct an investigation before taking action to improve the system. With the investigation, an analyst will better understand the problem and the system flow more depth, even detect the problem is known but the problem still describe the size of the course.

Many reports in the detection problem may not actually be real or cannot be solved. This may be because:

·         The goal is too ideal

•        Lack of resources and / or attitudes

•        Measurement system is less accurate

•        The purpose of the system is lagging

•        The difference between the ideal system and the system temporarily

In solving the problem, should provide an explanation of

·         Formulation system that is running through the investigation in detail

·         Obtain consensus that the ideal system

·         Develop several alternatives to reduce the difference between the ideal system with a system that runs

·         Selecting the best alternative

Task start point is 1 to 4 will take a very long time including the necessary costs.

The objective of the investigation is to stabilize or show the actual problem occurred while analysts as a way to understand the system in depth.

CONSTRAINTS SYSTEM IN INVESTIGATION

Conduct investigations in several problems that often appear are:

o   Time

Analysts lack of resources (resource) time, so just do some investigative activities. Usually when dealing with the issue of cost is required.

o   Cost

Often the costs incurred related to the length of time for activities investigation, so that management will provide cost limits

o   Finance

Manager information systems tend Junior told analysts that do not yet have the technical expertise or knowledge is sufficient, so that will impact on the results of investigations that are less deep, or more mature

o   Politics

Management or the parties may distribute certain issues which aim to restrict the investigation activities.

o   Mix of There are parties

Who try to intervene or manage investigation in activities that will disrupt or cause a disruption?

RECOMMENDATIONS
Results of the investigation is a recommendation that includes, among others, the following:

a)      Not to take any action because it found no problems. This can happen as they may in the preliminary report, the problem contrived so that at the time of the investigation is done-the problem does not happen or was not found.

b)      Conducting system maintenance for problems that small. Maintenance of the system that made every day (short period) will help minimize the problems that appear in so fast and to always be better controlled.

c)      Improve the ability or skills in the run or use the information system.

d)     Consider modifications to the system in total, so the need to replace it with the thought that the new system.

e)      Placing the plan going into the development system that is immediately done.

TACTIC INVESTIGATION

a.       Listen, do not lecture.

If you know all the answers, you certainly will not conduct investigations. So that in the investigation should provide enough time for the management or the user to explain in clear and complete, and system analysts do not dominate discussion.

b.      Do not provide solutions to the initial problem.

This means do not try showing ideas to solve the problem, before the investigation is completed all the activities conducted, so that the solutions are part-part.

c.       Comparing the story (compare stories).

Different people mean different views of the same problem, so the need to involve the supervisor and subordinate in providing a clear view of the problem and can be trusted. Should not hear from one source so that there is only one view (opinion). When the user has a difference of views, should find the differences and then seek the views that have similarities.

d.      Note the reluctance responses (look for reluctant responses).

Reluctance to give responses that indicate something is hidden. Too many problems the system  can also causes confusion, so not able to explain in full.

e.       Note the logical inconsistency problems (probe for logical inconsistencies).

Inconsistency is the logical termination of the data flow where data is missing, or suddenly appear certain data. Some things related to this issue:

• There are data its inserts but no output (black hole).

• There are outputs (output), but no data its inserts (miracles).

f.       Notice the impact you (observe your effect).

Given the differences of when you attend and when you do not attend. Rating referred directly to the internal probe. External probe, while the assessment is made known by anyone without (searching external materials), such as by analyzing reports, history the problems tools, and sources of other secondary investigation.

g.      Require hard work, giving rise to boredom (expect hard, boring work).

Be a detective professionals and patient in dealing with problems in the system bertahap.dan sustainable.

h.      Avoid problems politic (avoid politics).

Mission analyst system is not the judge the facts (your mission is fact, not judgment).

TECH INVESTIGATION

In general, techniques of investigation include 2 activities, namely:

a. Directly

Namely to find out of directly what is happening in the environment. There are three techniques to investigate directly, that is with:

•        Questionnaire.

This technique is very appropriate, if in the investigation have the time and cost constraints. Although responded to get through from blank fields. This is the best of the questionnaire as a document that can show differences that occurred in the respondents.

•        Frequently asked questions.

These activities require time and special expertise. Not everyone can do it successfully. Interview questions can be used for the sequence in depth in addition to more flexible with the condition field.

•        Observation.

It is a strong internal probe. Sit together with the system by making observations with a more specific question. Why you do this activity? Or where this document will be moved? Each question may be able to demonstrate problem-solving mysterious.

b. Indirectly

Activities that can be done quickly and not visible from the operational personnel, so that the outside can see or something that is hidden from the user community. This activity will dominate at the beginning of the SDLC activities, to further deepen internal probe.

•        Flow of the procedure.

Operational procedures are the means (vehicles) for new employees understand their work and experience to handle employee problems. If the procedure does not flow properly, the system information cannot be operated correctly as well. Use the system flowchart for the path information as explanation Operating procedures. If there is any problem in procedure, problems may arise in the actual operations.

•        Reviewing documents (document review).

Is to find and gather important documents (critical document). If problems occur in many customer orders, collect the original source documents from customer orders, which used as its data-entry, interactive screen format, transaction detail, summary and report errors that occur.

•        Sampling (sampling).

In this case, for example, you need to improve the quality of data on a network, then you must have the data to improve the quality of the network, and for that you need to have the data on it that can be taken where randomly.

•        Tabular (Tabular tools)

Also called the matrix, the check list (checklists) to find the conflict (discrepancies) in the transaction flow.

CURRENT SYSTEM DESCRIPTION

Determine system performance at this time will have difficulty if the company does not have a standard performance measurement system. Unfortunately, companies tend not to update (to update) documentation systems that are running. Therefore, analysts refine the document during the investigation system.

Description of the system includes a clear explanation at this time:

a.       Inputs (inputs)

b.      Outputs (outputs)

c.       Files (files)

d.      Data elements (data elements)

e.       Volume of transactions and documents action (action document and transaction volume)

f.       Data flow diagrams (data flow diagrams)

ANALISIS’S REQUIREMENT

Stage of intensive interaction between the systems analyst with the end user where the system shows the development team expertise to get feedback and trust so that the user get a good participation.

-          The 4 Goals achieved:

•        Explain the complete system

•        Describe the ideal information system

•        Bringing information system to the ideal conditions at this time with attention to resource constraints

•        Provide a stimulus to the user confidence in system development

-          Method

•        FAQ

•        Questioner

•        Observation

•        Procedure analysis

•        Observation document

-          Resource constraints

•        Time

•        Money

•        Expertise

•        Technology

•        External Factors

-          Document the needs analysis

•        Referral analysis: Relationships with end users, watch process, problems in data collection

•        User Requirements: Requirements actual, reporting requirements, training needs and the influence of the new system

•        obstacle System: Explaining the cost and time constraints, expertise, technology, and external factors

•        Document the form of data collection instruments, statistical consensus, the logical flow of data and physic, data elements in the initial data dictionary.

GENERATING SYSTEMS ALTERNATIVES

-          How do I approach the condition of the system at this time with the condition of the ideal system?

•        Create an alternative to solve the problem of information system

•        Alternative is best applied wisely

-          Options Strategies

•        Distributed versus centralized processing, change the decision from the information to the centralized data processing end user Decentralized responsibility center

•        Integrated versus dispersed database, the system designer must consider the data are entered in the data base and the entrance to the File

•        Surround System Strategy of Development, Environment around important strategy in the case of company takeovers because the information system of other companies may vary with the company at this time.

-          Options Tactic

Selection is done before the design operational

Designing Operational Options can be grouped into

•        Input

·         Online Vs Off Line Data Entry

·         Keyed Vs Machine Readable Data Entry

·         Centralized Vs Decentralized Data Entry

•        Processing

·         Batch Vs Real-time record update

·         Sequential Vs Direct Access to records

·         Single Vs Multiple Users update of records

•        Output

·         Traditional Vs Turn Around Documents

·         Structured Vs based Inquiry reports

SELECTING THE PROPER SYSTEM

-          Compare Tactic: System comparison based on the costs and benefits are relative; There are 3 ways said system A system is superior to the other if:

·         A cost is lower than B, and the benefits of both

·         A cost is lower than B and A yield advantage of more than B

·         A and B have the same but the cost advantage generated a lot more.

-          Some Compares Method System

·         Break Even point Analysis

·         Payback Period

·         discounted payback period

·         Internal Rate of Return

SELECTING THE PROPER SYSTEM

-          Cost categories

o   Hardware

o   Software

o    People

o    Suppliers

o    Telecommunications

o    Physical sites

-          Cost Details

Comparing the cost of information systems through the life of the system, analysts project how cost changes for the future and there are 3 models cost information system, namely Linear, and exponentially Step Function

-          Cost information system can occur only once and can also occur on an ongoing basis.

o   Cost of information systems that occur once only cost that is onetime and development costs that occur during the development of the system.

o   Cost of information systems that occur on a continual basis are recurring cost and operational cost where the cost of this is the case when the operating system information every day.

FACTORS INTO INFORMATION SYSTEM

-          Qualitative factors that lead the performance information system that both of them

o   Reducing the level of error

o   Reduce the time to fix errors

o   Reducing the response time from the workstation alternative

o   Accelerating the provision of information

o   Increase the security system

o   have update the source record is active

o   Increase the satisfaction of the

FACTORS INTO CORPORATE STRATEGY

o   Consumer Satisfaction

o   Level sales increased

o   Commitment of consumers and vendors

o   The information product marketing

PRESENTING LEARNING SYSTEM

o   Make a short presentation

o   Reduce the techniques detailed explanation

o   clearly presentation with visual aids

o   If using a model using a tool such as a laptop so that more informative

o   Emphasize the benefits of the proposed system with some information that there are alternative suitable conditions experienced by the company.

CONTINUING DECISION OR NOT

o   If the company decided to develop the information system, the department will do the next process, namely Design System.

o   If the System Development and Life Cycle (SDLC) will be terminated.

o   Often can found problems with the system and the study and top management will usually ask for the fulfillment of the re-study system.

o   Model can describes some of the stages of the repeated and sometimes the information will make a decision before the repeat stage system of study.

o   With the alternative, the decision to repeat a previous phase or SDLC is not Go – No-Go Decision.

—————————————————————————————————————–

Reference :  http://kuliah.dinus.ac.id/ika/asi6.html (in bahasa)

http://kuliah.dinus.ac.id/ika/asi7.html (in bahasa)

Agus Sanjaya, Slide Presentation.

Development of the system means a system set up a new, to change the old system as a whole or improve the existing system. This is caused by several factors, namely:

1.      There is a problem in the old system, among other

a.       Irregularity : irregularity in the old system this does not cause the system to function optimally.

b.      Growth organization : which caused the growth of the organization the development of a new system, such as the information needs of the area, volume data processing, etc. has been increasing, therefore the old system is not effective anymore because it already cannot meet these needs organization.

2.      To seize opportunities

With such an information system organization will be able to seize the opportunity to compete in – opportunities that exist. For example: get a new market such as the bid to participate in the tender as viewed from the previous performance, improve services to customers such as at a cafe to provide free internet voucher when already playing a few hours in the cafe.

3.      There is instructions

Preparation of a system will be affected by external factors instructions of organization, for example: customers who to queue at the checkout that allows them not so saturated and shopping, this complaint is the organization must change the way of payment at the checkout for example by using RFID which enables customers only through at the checkout and everything is counted.

Third case above is also the goal of the development of a system. A system will be developed to overcome all the problems that arise, to get every opportunity available, and fulfill the instructions given in both in and outside the company environment.

Organization Expectations after Implementing A New System In An Organization

a.       Performance (performance)

Performance improvement that the new system to be more effective. Performance can be measured from the throughput and respond time. Throughput means the amount of work that can be done at a certain time. Response time is the average time the pending transaction between the two plus the response time to respond to the job.

For example: a shop that was using a manual bookkeeping which is in the search for the previous year certainly will be very time consuming and cannot be real time, but with the system information that can be done in real time.

b.      Information (information)

Organizations get all the information accurately and quickly.

For example: The making of a report that the organization can be issued in a certain period.

c.       Economy (economic)

The new system is expected to increase the benefits or advantages to the company so that it also expected a decline to the cost of going.

For example: In a supermarket, of course, the stock has very much, with the manual this is sure to need very many employees but with uses information system we can reduce expenditure for payment employees.

d.      Control (control)

From the new system, we can do to control everything from within the organization.
For example: in a supermarket now in controlling the goods using the barcode and the latest is to use RFID, so that it can be in control.

e.       Efficiency

Efficiency this related to how a company utilizes the resources available with the – well

f.       Service

With the new system, companies can improve service to customers.
For example: Internet Banking, which can be accessed from anywhere without the need to queue the bank teller to do a transaction.

 SYSTEM DEVELOPMENT PRINCIPLES
some principles to be considered by system developers are:

a.       System management

System developed for the purpose of management, so that future systems must be able to support the needs of management

b.      System is a large investment

Information system is identical with the use of technology, so it requires a large capital to develop it. So every investment capital should consider 2 things, namely:

·         All alternatives should be investigated in order to minimize the opportunity cost. Several alternatives should be in the investigation to determine the most profitable alternative.

·         Must be the best investment value, said new investment profitable if the value has. That is the benefit or result greater than the cost to obtain it. Cost benefit analysis or cost analysis Effectiveness can be used to determine whether the project is worth investigation or not

c.       System developed need educated people who

In this case the relevant person must not educate about the system, but that person can do on the job training to run the system.

d.      Stages in the development of the system

At this stage a planning required to achieve maximum employment as a method to apply SDLC Waterfall and other methodology.

e.       Development of the system does not need Ascending

At this stage we do not have to wait another plan because we can make with the same time.

f.       Do not be afraid to cancel the project
In this case means we are allowed to provide the advice or input when a project is not feasible in the more developed or continued, and if necessary cancel the project directly.

g.      Documentation

This is necessary to do in the build or develop a system, because on the day in the future can use as reference in the renewal system.

 

 

SYSTEM DEVELOPMENT LIFE CYCLE

Waterfall Method

In the process of planning a system there are several methods you can use one of them is a waterfall, which is the first system is:

-          Conduct analysis requirement from the user, namely understanding the nature of the system will be built.

-          Analysis of system design that will be created, in this phase of the system focused on the structure of the data to be in the adoption, interface design, and detail algorithm.

-          At the design stage to translate into computer language that is understandable and start building the system. After the system has been completed then the process is done the continue

-          Testing at this stage in the test system and sought bug . When in the testing stage is a good system can then be implemented directly.

-        The last stage is the stage system is maintenance. Waterfall model is the only recurring maintenance phase only.

 

 Iterative  Method
In the Iterative Model are almost the same as the phases of the waterfall, but in this model is to analyze the stage when the error occurred in the system that was made when the need to fix it will be repeat of the planning process and proceed with the next stages.

                   

Spiral Method

This method is the analysis of risk. If the risk analysis to provide results that is not bound to the needs, the development of this system can be stopped. There are 6 phases, namely:

-          Communications customer, communication must be built between the developer effectively with customers to determine the needs of the maximum.

-          Planning, defining the resources, time limit and project information related other.

-          Analysis of risk, determine the risks that will occur during the development of the system.

-          Engineering, create one or more applications to represent the system works.

-          Construction and launch of the stages required for the construction, test, install and provide training to customers.

-          Evaluate customers, to obtain feedback from customers to the system are made.

        

 

DEVELOPMENT SYSTEM APPROACH

There are several approaches to develop a system that is

View from methodology used namely:

1. The classical approach is called the classical or traditional approach conventional approach is the approach in the development of systems that follow the stages in the life cycle without a system provided with the tools and techniques are adequate. On this approach, there are problems, namely:

Problems: the development of hard, expensive treatment, the possibility of error, success is less assured, the problems in the implementation of

1. It is a structured approach to the development of the new system is equipped with several tools and techniques so that the result was successful. Through this approach, complex problems can be solved in the organization and results of the system will be easy to maintain, flexible, and more satisfied, have good documentation, on time and in accordance with the budget cost of development, can improve productivity and quality will be better

 

View from the targets achieved, namely:

a.       The piece is an approach that emphasizing on an application or activities regardless of the overall goals of the organization.

b.      The approach is a system approach emphasizing that the achievement of overall objectives and see the system as a whole is unity.

 

Views of how to determine the needs of the system are:

a.       Ride-down approach (bottom-up), this approach starts from the bottom of the operational level, this is a discrete classical approach. This approach is also known by the term data-analysis

b.      Top-down approach (top-down), this approach starts from the top-level planning and strategy is a discrete structured approach, this approach is also known to the decision-analysis

 

Views of how to develop are:

1. System-comprehensive approach, this approach to develop the system simultaneously and comprehensively. Is a discrete approach to classical
2. Modular approach, this approach to solve a complex system into parts that simple. System to be developed on time, it’s easy to be understood and maintained. Is a discrete approach to structured

 

Views of technology, namely:

1. The far-jump (great-loop approach), this approach to develop the system simultaneously using advanced technology but high-risk and spend a lot of cost.
2. Developing approaches (evolutionary approach), this approach to apply advanced technology to specific applications. Developed for the needs, and cost-effective and can follow the development of technology.

SYSTEM DEVELOPMENT METHODOLOGY

 

• What is the methodology?

- Methods and procedures used in science

• What is the method?

- A systematic way to grind

  • What is the algorithm?

- Sort-sequence of procedures to solve a problem

 

 

CLASSIFICATION METHODOLOGY DEVELOPMENT

 

• Functional decomposition

-          Emphasizing the system subsystem solutions

-          Example: HIPO, Stepwise refinement, iterative stepwise refinement, information hiding

• Data-oriented

-          Emphasizes the characteristics of the data processed

-          Data-flow oriented: modules according to the type of data elements

-          Data-oriented structure: the structure of input and output

·         Prescriptive
Usually provided by the manufacturer of the software

 

 

SYSTEM DEVELOPMENT TOOLS

• Shaped graph: HIPO, SADT, Jackson’s diagram, and other

• Tools that use the chart:

-          Activity charting: describes the activities, for example: Gant chart, flowchart, etc.

-          Layout charting: describes the layout

-          Personal relationship charting: describes the relationship of personnel, for example: organization charts, work distribution chart

 

TECHNICAL DEVELOPMENT SYSTEM

• Technical project management for > scheduled project, for example: CPM and pert

• Technical > find facts and decide to collect data or facts

-          Interview

-          Observation

• Technical analysis of cost or benefit > cost and cost-benefit analysis Effectiveness

• Technical meetings run

• Technical inspection

 

ANALYSTS AND PROGRAMMERS

•         Analyst system: study of the problems and determine the needs of the system to identify solutions

•         programmers: write a program code based on the building design is created by the analyst

•         Analysts duty system bridge the knowledge gap that occurs between the user and system programmers

]]>