Day 11 UML and Use Case Diagrams

1. Day 11 – UML and Use Case Diagrams

2. Unified Modeling Language (UML) Object-oriented development approach – some times called OO modeling or OO techniques Use Case Diagrams most common UML technique UML can be used with any OO methodology OO Modeling supports object programming. DFDs focus on processes for data flow, rather than actual program steps. There are two purposes for UML modeling 1) to show how the application is used (as opposed to DFDs which show the process or logic and 2) to show what state the application is in. UML is a notation used in OO modeling – it is a language • A preliminary version of UML was presented in 1995 • In 1997 UML was presented to the Object Management Group (OMG) as a standard modeling technique www.omg.org • OMG is a consortium of software vendors, developers and organization with the goal to provide a common architectural framework for OO applications.UML views information systems as a collection of interacting objects that work together to accomplish tasks. Source of illustration: http://www.uml-diagrams.org/use-case-diagrams-examples.htmlUML can be used with any OO methodology OO Modeling supports object programming. DFDs focus on processes for data flow, rather than actual program steps. There are two purposes for UML modeling 1) to show how the application is used (as opposed to DFDs which show the process or logic and 2) to show what state the application is in. UML is a notation used in OO modeling – it is a language • A preliminary version of UML was presented in 1995 • In 1997 UML was presented to the Object Management Group (OMG) as a standard modeling technique www.omg.org • OMG is a consortium of software vendors, developers and organization with the goal to provide a common architectural framework for OO applications.UML views information systems as a collection of interacting objects that work together to accomplish tasks. Source of illustration: http://www.uml-diagrams.org/use-case-diagrams-examples.html

4. Use Case Diagram Format A boundary is the dividing line between the system and its environment. Use cases are within the boundary. Actors are outside the boundary. A connection is an association between an actor and a use case. It depicts a usage relationship, but does not indicate data flow. The Use Case Diagram defines the requirements • A use case diagram is a graphical model that summarizes the information about the actors and use cases • During the use case analysis we try to identify all of the uses of the system • The uses derive from the events in the requirements list • We can think about a use case diagram as a functional description of the entire system, which identifies functions to be supported by the new system Automation Boundary and Organization • Figure above shows a use case diagram with two actors and four use cases • The boundary line drawn around the entire set of use cases is the automated system boundary or the automation boundary (it denotes the boundary between the environment, where the actors reside, and the internal functions of the automated system). A boundary is the dividing line between the system and its environment. Use cases are within the boundary. Actors are outside the boundary. A connection is an association between an actor and a use case. It depicts a usage relationship, but does not indicate data flow. The Use Case Diagram defines the requirements • A use case diagram is a graphical model that summarizes the information about the actors and use cases • During the use case analysis we try to identify all of the uses of the system • The uses derive from the events in the requirements list • We can think about a use case diagram as a functional description of the entire system, which identifies functions to be supported by the new system Automation Boundary and Organization • Figure above shows a use case diagram with two actors and four use cases • The boundary line drawn around the entire set of use cases is the automated system boundary or the automation boundary (it denotes the boundary between the environment, where the actors reside, and the internal functions of the automated system).

5. Quick System Diagram – hand-drawn Use Case diagram – hand drawn preliminary drawing for eStore shows actors that system must handle.Use Case diagram – hand drawn preliminary drawing for eStore shows actors that system must handle.

6. Use Case diagram – Visio version for eStore that shows the names of each part of a use case diagram. Use Case diagram – Visio version for eStore that shows the names of each part of a use case diagram.

7. Visio Software and Database Category

8. Exercise 10 Resource:  Use Case Diagrams from Reading

9. Example for Latinitas’ Case Note by Gretel Paronzini-Fredette, from the 2002 Latinitas team: This is Latinitas’ use case diagram. Please note that it this is only a part of the use case diagram because I only reflected what the actor does as a user. I left out the volunteer as an administrator of the system. In which case, you will have more use cases within the system. Note by Gretel Paronzini-Fredette, from the 2002 Latinitas team: This is Latinitas’ use case diagram. Please note that it this is only a part of the use case diagram because I only reflected what the actor does as a user. I left out the volunteer as an administrator of the system. In which case, you will have more use cases within the system.

10. High Level Use Case Diagram – ASTA Skill Set System

11. High Level Use Case Diagram

12. High Level Use Case Diagram

18. Meeting 3: Evaluation Table

22. Functional Priorities – Judy Paul Website

26. Exercise 11 Reminder: Bring to Class Monday 3/5

27. Exercise 10: In class Client Project Team work

28. Exercise 10 reference: High Level Use Case Diagram from Reading

29. Exercise 10 reference: Drill Down Use Case Diagram from Reading