- called also data flow diagram (DFD)
- describe system distribution into module smaller
- will make user less will realize computer area to will understand system that be done
context diagram
- consist of one process and describe scope from a system
- be level highest from DFD that describe entire input to system and outpur from system
- system is limitted by boundary (described by line broken offs)
- there may not be any storage (storage)
diagram zero
- describe process from DFD
- give opinion according to comprehensive hit system that handled, show function or principal process, data current and eskternal entity
- in level this maked data existence storage
- for process is not detailed again in level furthermore so added simbol ‘*’ or ‘p’ by the end of process number
- balance input and output (balancing) between diagram 0 with context diagram must be taked care
detail diagram
- be diagram that elaborate what process is there in diagram zero or level at on it
- numberization level in DFD:
| Name Level | Name Diagram | process number |
| 0 | Context |
|
| 1 | Diagram 0 | 1.0, 2.0, 3.0, ... |
| 2 | Diagram 1.0 | 1.1, 1.2, 1.3, ... |
| 3 | Diagram 1.1 | 1.1.1, 1.1.2, ... |
- in one level best not found more than 7 process and maximal 9, when more so dekomposisi
process specification
- every process in DFD must has process spesification
- in top level method that used to describe process can by using descriptive sentence
- in level detailer that is in process most under (functional primitive) want spesification structureder
- process spesification will be guide for programmer in will make program (coding)
- method that used in process spesification: process explanation in the form of story, decision table, decision tree
unitary outside
- something that beyond system, but he gives data into system or give data from system
- symbolized with notation box
- external entity doesn't belong part from system
- nomenclature:
· terminal name shaped noun
· terminal may not has name same except the object really same
data current
- be place currences information
- described with straight line that connect component from system
- data current is showed with arrow direction and line is given name on data current that flow
- data current flows between process, data storage and show data current from data shaped input for system
- name gift guide:
· data current name that consist of several word currents relateds with line continues
· there may not be any data current the name same and name gift must reflect its contents
· data current that consist of several elements can be declared with element group
· koid word use ‘data’ and ‘informasi’ to give name in data current
· sedapat may be data current name is written complete
rule other:
· data current name that come into a process may not equal to secretory data current name from process
· data flow that step into or out from data storage unnecessary given whose name:
· simple data current and easy understood
· data current describes entire item datas
· there may not be any data current from terminal to data storage or on the contrary because terminal not part from system, terminal connection with data storage must pass process
process
· process is what done by system
· process can cultivate data or data current enters to be data current out
· process functioneds mentransformasi one or several input datas is one or several product datas as according to desirable spesification
· every has one process or several inputs with produce one or several products
· process often also called bubble
process name gift guide:
· process name consists of verb and noun that reflect process function
· don't use process word as part from name a bubble
· there may not be any several process that has names same
· process must be given number. sequence number sedapat may be follow current or sequence process, but such sequence meaningless number absolutely is sequence process chronologically
data savings
· data storage be existing data repository in system
· symbolized with a pair parallel line or two lines wrongly one sides side opened
· process can take data from or give data to database
· name gift guide:
· name must reflect data storage
· when does the name more than one word so be must be given sign continue
data dictionary
· functioned to help system executant to interpret application in detail and mengorganisasi all data element that used system according to exactly so that user and has base explanation same about input, product, storage and process
· in analysis stage, data dictionary is used as a means of communication between system analyst with user
· in system planning stage, data dictionary is used to design input, report and database
· data current in dad has global, explanation detailer visible in data dictionary
data dictionary holds the followings:
· data current name: must be registerred so that reader that need furthermore explanation about a data current can look for it easily
· alias: alias or name other from data can be written if (there are) any
· data form: used to group data dictionary into its use sewaktu system planning
· data current: show from which data flows and where does data aim
· explanation: give explanation about meaning from data current
balancing in DFD
· data current that come into and out from one process must equal to data current that comes into and out from process details in level/stage at under it
· data current name that come into and out from one process must equal to data current name that enters to into and out from process details
· total and name entitas outside from a process must equal to total and name entitas outside from process details
· matters that must be payed in DFD that has more than one level:
· must found balance input and output between one level and level next
· balance between level 0 and level 1 seen in input/output from data current to or from terminal in level 0, while balance between level 1 and level 2 seen in input/output from data current to/from process concerned
· data current name, data storage and terminal in every level must same if the object same
prohibition in DFD
· data current may not from entitas outside direct aim entitas outside another without pass a process
· data current may not from direct data savings aim to entitas outside without pass a process
· data current may not from direct data savings aim another data savings without pass a process
· data current from one direct process aims another process without pass a data savings best may be avoided
