1. Elaboration: Iteration 3

2. Elaboration: Iteration 3 Basics Inception and iteration-1 explored many basic OOA/D modeling basics. Iteration-2 narrowly emphasized object design. This third iteration takes a broader view again, exploring a variety of analysis and design topics, including: Process modeling with UML activity diagrams State Machine Diagrams and Modeling Architectural Analysis UML deployment and component diagrams

3. Elaboration: Iteration 3 UML Activity Diagrams and Modeling A UML activity diagram shows sequential and parallel activities in a process. They are useful for modeling business processes, workflows, data flows, and complex algorithms. Basic UML activity diagram notation is shown in Figure, illustrating an action, partition, join, and object node. This diagram shows a sequence of actions, some of which may be parallel.

4. Elaboration: Iteration 3 Activity Diagrams

5. Elaboration: Iteration 3 UML Activity Diagrams and Modeling There are two points: Once an action is finished, there is an automatic outgoing transition The diagram can show both control flow and data flow

6. Elaboration: Iteration 3 UML Activity Diagrams and Modeling A UML activity diagram having rich notation to show a sequence of activities, and parallel activities. It may be applied to any purpose But is popular for visualizing business workflows and processes, and use cases.

7. UML Activity Diagrams and Modeling Business Process Modeling The above Figure, example of applying UML activity diagrams to business process modeling. This is the model of a parcel shipping business. All this process can be captured in text (in use case text), in this activity diagrams is a great example of pictures being worth a thousand words. Activity diagrams used to understand the current complex business processes by visualizing them.

8. UML Activity Diagrams and Modeling Data Flow Modeling Started in the 1970s, Data flow diagrams (DFD) became a popular way to visualize the major steps and data involved in the software system processes. This is not the same as business process modeling; DFDs were usually used to show data flows in a computer system. DFDs were useful to document the major data flows.

9. UML Activity Diagrams and Modeling Data Flow Modeling See Figure 6.2 for an example DFD.

10. UML Activity Diagrams and Modeling Data Flow Modeling The information modeled in a DFD is useful, for documentation, But the UML does not include DFD notation. UML activity diagrams can satisfy the same goals. They can be used for data flow modeling, replacing traditional DFD notation.

11. UML Activity Diagrams and Modeling Data Flow Modeling Figure 6.3 illustrates the same information as the DFD in Figure 6.2, But using a UML activity diagram. Notice that in addition to object nodes being useful to show data flow, the UML datastore node is applicable.

12. UML Activity Diagrams and Modeling Data Flow Modeling Figure 6.3 illustrates the same information as the DFD in Figure 6.2