1. Systems Analysis & Design Methods Traditional Techniques: Data Flow Diagrams (see also handouts !)

2. 2Older techniques Structured Analysis & Data Flow Diagrams (DFD) 70ies and 80ies 70ies and 80ies Gane and Sarson, DeMarco/Yourdon Gane and Sarson, DeMarco/Yourdon Process-centered Process-centered Analysts draw a series of process models called ‘data flow diagrams’ along with their inputs, outputs and files. Analysts draw a series of process models called ‘data flow diagrams’ along with their inputs, outputs and files. The models show the flow of data together with places where data is stored. The models show the flow of data together with places where data is stored.

3. 3Older techniques DFD shapes Process: needs both input and output External agent: output must go to process, input must come from process File/database/datastore: output must go to process, input must come from process

4. 4Older techniques A simple DFD (part)

5. 5Older techniques Event driven Process Modelling (see handouts) (1) Context DFD: 1 proces ‘The System’ + many external agents (1) Context DFD: 1 proces ‘The System’ + many external agents ‘The System’ is exploded to form the decomposition diagram (2) Decomposition Diagram: tree of processes (2) Decomposition Diagram: tree of processes ‘The System’-proces is divided into functions ‘The System’-proces is divided into functions Functions are devided into events (4) Functions are devided into events (4) Each event gives rise to its own small DF diagram called event diagram Each event gives rise to its own small DF diagram called event diagram (5) Event diagrams (DFD) (5) Event diagrams (DFD) Event diagrams are combined to form the system diagram Event diagrams are combined to form the system diagram (6) System diagram (6) System diagram Each event process that requiress additional detail has its own primitive diagram: (7) Primitive diagrams (DFD) (7) Primitive diagrams (DFD) Note: The events are described in event lists. For each event this list gives the corresponding actor and response to the event. Note: The data passed to and from the processes can serve as a starting point for the data model in Entity-Relationship-modeling. Or you can do the data modeling first.

6. 6Older techniques Event list example ActorEventResponse Client Places order Generate member order confirmation. Create member order and member ordered products in the database (Time) 90 days after order Delete member order and member ordered products

7. 7Older techniques Data & Process model synchronisation: Data to process CRUD-matrix DFD’s are about process modeling (70ies) DFD’s are about process modeling (70ies) ER-diagrams are about data modeling (80ies). (For now, you can view an ER-model as a high level database model.) ER-diagrams are about data modeling (80ies). (For now, you can view an ER-model as a high level database model.) For every datastore in the process model, there should be exactly one entity (table) in the data model and vice versa. Furthermore, each entity should be created, read, updated and deleted by at least one process (not necessarily the same). For this, you can use a so-called CRUD matrix (see handouts).

8. 8Older techniques DFDs: an assessment We read: Whitten, …[2004] ‘Object-oriented analysis will eventually replace structured analysis’. (p 225) Whitten, …[2004] ‘Object-oriented analysis will eventually replace structured analysis’. (p 225)Conclusion: DFD’s may be interesting for the following purposes: to understand older system documents to understand older system documents maybe to aid business process reengeneering, even if they are not automated maybe to aid business process reengeneering, even if they are not automated definitely to model data-flows between systems (imports, exports) definitely to model data-flows between systems (imports, exports) Note: In general, when doing procedural programming, high level procedural code is often more readable than their corresponding diagrams: flow charts, sequence diagrams, acitivity diagrams.