Professional Documents
Culture Documents
Resume
Npm : 1910631030065
Class : 3G / S1 Accounting
Task : Buat resume terkait dengan "Flowchart" dan "Activity Diagram" dengan lengkap.
Bahasa bebas bahasa Inggris ataupun bahasa Indonesia!
Answer :
FLOWCHART
DEFINITION OF FLOWCHART
Adelia (2011) states that a flowchart is a graphic depiction of the steps and sequence of
procedures of a program. Flowcharts help analysts and programmers to solve problems into
smaller segments and help in analyzing other alternatives in operation. Flowcharts usually make it
easier to solve a problem, especially problems that need to be studied and evaluated further.
Flowchart is a form of image / diagram which has a flow in one or two directions sequentially.
Flowcharts are used to represent and design programs. Therefore flowcharts must be able to
represent components in a programming language.
Jogiyanto (1990) states that a flowchart is a graphical depiction of the steps and sequence
of procedures of a program. Flowcharts help analysts and programmers to solve problems into
smaller segments and help in analyzing other alternatives in operation. Flowcharts usually make it
easier to solve a problem, especially problems that need to be studied and evaluated further.
3. Detailed diagrams
Is a diagram that describes what processes are in the Zero diagram.
Data Flow Diagrams (DFD) are modeling tools that allow system professionals to
describe the system as a network of functional processes that are linked to one another by
data flows, either manually or computerized.
DFD is a modeling tool that is often used, especially when the system functions are a
more important and complex part of the data manipulated by the system. In other words,
DFD is a modeling tool that emphasizes only on system functions.
DFD is a system design tool that is oriented to data flow with the concept of
decomposition. It can be used to describe analysis and system design that is easily
communicated by system professionals to users and program makers.
Data Flow Diagrams (DFD) GUIDELINES
1. Understand the system. Develop this understanding by observing organization data flows,
observing and interviewing those who use and process the data or having them complete a
questionnaire; by reading a narrative description of the system; or by walking through system
transactions.
2. Ignore certain aspects of the system. A DFD is a diagramof the origins, flow, transformation,
storage, and destinations of data. Only very important error paths are included; unimportant error
paths are ignored.Determining how the system starts and stops is notshown.
3. Determine system boundaries. Determine what to include and exclude. Include all relevant data
elements, because excluded items will not be considered during system development.
4. Develop a context diagram. A context diagram depicts system boundaries. In the diagram's
center is a circle with the name of the system. Outside entities the system interacts with directly
are in boxes on either side, connected by data flows depicting the data passed between them.
DFDs in successively more detail depict data flows inside the system.
5. Identify data flows. Identify all data flows (significant movement of data) entering or leaving
the system, including where the data originate and its final destination. All data flows come from
and go to a transformation process, a data store (file), or a source or destination. Data flows can
move in two directions, shown as a line with arrows on both ends (see G in Figure 3-3).
6. Group data flows. A data flow can consist of one ormore pieces of datum. Data elements that
always flow together should be grouped together and shown as one data flow until they are
separated. If the data do not always flow together, show them as separate data flows.
7. Identify transformation processes. Place a circle wherever work is required to transform one
data flow into another. All transformation processes shouldhave one or more incoming and
outgoing data flows.
8. Group transformation processes. Transformation processes that are logically related or occur at
the same time and place should be grouped together. Don't combine unrelated items into a single
transformation process. If data are not processed together, or are sometimes processed differently,
separate them.
9. Identify all files or data stores. Identify each temporary or permanent data repository, and
identify each data flow into and out of it.
10. Identify all data sources and destinations. Include them on the DFD.
11. Name all DFD elements. Except for data flows into or out of data stores (the data store name
is usually sufficient to identify the data flow), data elements should be given unique and
descriptive names representingwhat is known about them. Data namingflows first forces you to
concentrate on the all-important data flows, rather than on the processes orstores. Processes and
data stores typically take their names from the data inflows or outflows. Choose activeand
descriptive names, such as "update inventory"and "validate transaction," rather than "inputdata
"or" update process. " Process names should include action verbs such as update, edit,
prepare,reconcile, and record.
12. Subdivide the DFD. A cluttered DFD is hard to readand understand. If you have more than
five to seven processes on a page, decompose the context diagram into high-level processes.
Explode these high-levels processes into successively lower-level processes.
13. Give each process a sequential number. Giving each process a sequential number (lower to
higher) helps readers navigate among the DFD levels.
14. Refine the DFD. Work through data flows several times. Each subsequent pass helps refine
the diagram and identify the fine points. Organize the DFD to flow from top to bottom and from
left to right.
15. Prepare a final copy. Do not allow data flow lines to cross each other; if necessary, repeat a
data store or destination. Place the name of the DFD, the date prepared, and the preparer's name
on each page.
References
Jogiyanto. (1990). Analisis dan Desain Sistem Informasi: Pendekatan Terstruktur. Yogyakarta:
Andi Offset.
Adelia. (2011). Implementasi Customer Relationship Management (CRM) Pada Sistem Reservasi
Hotel Berbasis Website Dan Desktop. Jurnal Sistem Informasi, 6 (2), hlm. 113-126.
Kusrini dan Koniyo, A. (2007). Tuntunan Praktis Membangun Sistem Informasi dengan Visual
Basic dan Microsoft SQL Server. Yogyakarta: Andi Offset.
Munir, Fahmi Latief. 2016. Pengertian, Jenis – Jenis, Fungsi dan Contoh Flowchart. Retrieved
https://fahmilatiefmunir.blogspot.co.id/2016/01/pengertian-jenis-jenis-fungsi-dan.html
Perdana, M. R. (2016). Pengertian Flowchart dan Jenis-Jenisnya. Retrieved from
http://divisi11.blogspot.co.id/2016/09/pengertian-flowchart-dan-jenis-jenisnya.html
Marshall B Romney. Accounting Information System.(2015)
ADE PUSPITA S. (2013) Understanding Data Flow Diagrams (DFD) and examples of DFD
images. Retrivied https://adepuspita28.wordpress.com/2013/10/26/pengentuk-data-flow-diagram-
dfd-dan-contoh-gambar-dfd/