1. Day 4 – Process Modeling cont’d Today’s Goals  More on Process Models  Leveling DFDs  Exercise 5 – in class  Group Project / Client Project reminders  Modeling with pictures (Context Diagram)

2. Walter Golding  Senior, MIS Major  Tennis, biking, cooking  Client Project = Structured Motivation  Summer: Google  Tips for Success on Client Project  Meet weekly with your client  Learn any new languages before you even try to start working

3. Garrett Kreitman

4. Important to note that…  Every company will have a preferred diagramming process. You (probably) will have to learn new techniques.  We have tried to demonstrate some of the diagrams. We’ll expect you to use some form of modeling and diagramming on client project.  More examples….

5. An old friend – ERD

6. Use case diagrams Has some similarities to DFD’s – but more focused on presenting system concepts to management

7. Inheritance / Encapsulation

8. Business Process Flows

9. Business Process (w/ Swimlanes)

10. DFDs are “data” (not process) focused  Context Diagram  A simplified data flow diagram (DFD) of the scope of an organizational system that shows the system boundaries, external entities that interact with the system and the major information flows between the entities and the system  Fig-0 Diagram  A data flow diagram (DFD) that represents a system’s major processes, data flows and data stores at a high level of detail. It is decomposable.

11. EE1 Employee Time card w/ hours worked Payroll System Paycheck Context Diagrams usually aren’t this simple

12. Usually more complicated in a company

13. DFDs are “data” (not process) focused  Context Diagram  A simplified data flow diagram (DFD) of the scope of an organizational system that shows the system boundaries, external entities that interact with the system and the major information flows between the entities and the system  Fig-0 Diagram  A data flow diagram (DFD) that represents a system’s major processes, data flows and data stores at a high level of detail. It is decomposable.

14. Data Flow Diagramming Rules 1.Inputs to a process are always different than outputs 2.Processes must have both an input and an output 3.Objects always have a unique name In order to keep the diagram uncluttered, you can repeat external entities & data stores on a diagram 4.No more than seven processes on one diagram 5.A process has a verb phrase label 6.Data only flows in one direction at a time 7.Data flows are nouns 8.Data must be transformed by a process (cannot be moved directly from one store to another or from an external entity to a data store). 9.Data store has a noun phrase label 10. NOTE: It’s okay if Fig 0 has no actors

15. Overview of a Leveled DFD Context Diagram Fig 0 Diagram Fig 4 Diagram Fig 4.5 Diagram Drill down to show more detailed processes, data flows, and data stores. Level 1 Level 2

16. Context Diagram How many external elements interface with the Proposed Skill Set System? How many data flows are going to system? How many data flows are going from system?

17. Compare the two levels

18. Compare Figure 0 and Figure 3 # 3.1 # 3.2 Level 1 DFD

19. Celis Figure 3 DFD

20. Celis Fig 3.2 DFD -- drill down detail Notice that DFDs read from left to right, and top to bottom, like a written page.

21. Celis fig 3.2 DFD -- drill down detail The Data Store #’s should match the higher level DFDs. This is a Level 2 DFD. S10 S11 S6

22. DFD Summary  The DFD models the flow of data in an information system and is data focused  DFD modeling begins with the Context Diagram, which depicts the entire system in a single bubble surrounded by external entities  The (Figure 0) shows the major functional components of the system as processes, connected by data flows to external entities, data stores  As needed, more detailed levels are developed to give full view of system  Figures are named by the Process, not level.

23. Reality & DFD creation  DFDs are usually created from messy notes.  What you think initially might be the best organization of the process usually isn’t what will be the final version.  So, assume you will start with a messy first draft and then clean up the process by leveling the DFDs:  Figuring out what the major processes are for the Figure 0 DFD and then creating the lower level DFDs with the details  TIP: DFD Summary and Rules on Resources pageDFD Summary and Rules

24. Multi-level DFD exercise  Multi-level DFD  Take a look at the exercise 5 sheets  Context diagram and several levels of DFDs  In pairs or alone, do this exercise on a separate sheet to paper to turn in. Be sure to put your name on it. 1.Briefly describe the system (quick overview) 2.What errors can you find? Hints: Be picky. Look at naming. Check data flows.

25. SageStats: Things done well  All External Entities are labeled and consistent.  All figures are numbered and labeled— top to bottom & left to right.  Names are descriptive and unique.  Process names use verbs.  Data is transformed or changed with each process

26. SageStats: Errors Data Flow Diagram – Level 3Data Flow Diagram – Level 0  Context Diagram to Figure 0—flows to EE2 don’t match  Figure 0 & Level 1 — No Process Name  Figure 0 to Level 1—Process 4 is exploded, not Process 3  Figure 0 to Level 1—NOT Level 3, but Level 1, Figure 3  Figure 0 to Level 1—Sports-Books Data is represented twice on Figure 0 Figure 3 (4) Record Bets SageStats Figure 0

27. Caution about Group Project DFDs Unlike the Client Project, you read text to create your DFDs. Instead of leaving the leveling process (the drill down process) wide open, the text was written with a sense of what the main processes are. The assignment is very specific. Best approach? 1.Maybe create a messy detail DFD, then look back at the process bubbles listed in the requirements. 2.Or maybe start with the process bubbles in the requirements and figure out what needs to be added. 3.No one “right” way…

28. Reminders & Tips  Send email to both professors for faster response  Group Project #1 due Mon Feb 8 @ 5pm to one of our offices or in class (CBA 3.414 or 3.410) or to the IROM Dept. office, CBA 5.202  Hard copy at office  Soft copy submitted through Canvas

29. Group Project #1  Do not bind your report  Put team number in footer w/page number  Peer evaluations are due on Mon 8 th by 6pm  Don’t give all 10’s. You have a chance to explain, so if you feel this was the Best Group In The World, you can tell us.  It does not improve your grade  It makes you look bad  CONFIDENTIAL  No one will ever see it except your professors  NOTE: We look at your peer evals in all groups

30. Client Projects  By Friday (5 th ) at 5pm-- select and register your team for the Client Project  One person will be the team admin  Team name doesn’t change after it’s set  We will have 9 teams of 5 (Can’t do 6)  Can we establish teams now?  Next Friday (12 th ), submit client choices  Admin must be available at noon sharp to submit  Who doesn’t have a team yet?  Monday Feb 15 th – meet client / pizza – 6:30pm

31. Context Diagramming  Context Diagramming is becoming more common as we become more “user centric” in designing applications  Similar to DFD but less structured

32. Context Diagramming  5 Tips for Effective Sketching 1.Title your sketch 2.Combine simple shapes 3.Express emotion or state 4.Label each noun 5.Arrows demonstrate relationships  Exercise in groups to context diagram Latinitas  Work in pairs to draw out a context diagram for Latinitas.  Include key entities, actions, and data