2 Unified Modeling Language (UML)Object-oriented development approach – some times called OO modeling or OO techniquesUse Case Diagrams most common UML techniqueUML can be used with any OO methodologyOO 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• 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:Source of illustration:UML intro, Day 10, Tech Mod C2

3 Use Case Diagrams in SDLCUse case diagrams aid in the analysisand documentationof high level requirements forscope & stakeholdersDrill down use case diagramsaid in defining functional requirements one moduleat a time.Drill down to design each module.FinalConstructionPhase(s)InceptionPhase(s)3

4 Use Case Diagram FormatThe System is inside the rectangleOvals depict each use case – a system action.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 systemAutomation 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).Figure 1 in the UML-Use Case Diagram reading for today.UML intro, Day 11

6 Actors are roles or systems that interact with systemUse Case diagram – with VisioActors are roles or systems that interact with systemUse Case diagram – Visio version for eStore that shows the names of each part of a use case diagram.UML intro, Day 11

9 Example for Latinitas’ CaseThis Use Case diagram was created by 2007 UT MIS grad, Gretel Paronzini-FredetteGretel was on the Latinitas team. She now creates use case diagrams as a consultant at Deloitte in Austin. *As a business analyst, Gretel creates Use Case Scripts for each of the Use Cases in a Use Case Diagram* The Austin Bearing Point office is now a Deloitte office.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.UML intro, Day 11

11 High Level Use Case DiagramNotes, re: DFDsEvent (use case) names are verb-object like DFD processesNo data storesFocus is on interaction of Actors (system users) with the systemNo arrow heads for lines connecting actor and use case, since considered two-wayFigure 3 in UML-Use Case reading today.UML intro, Day 11

27 Exercise 10: In class Client Project Team workStakeholders TableHigh Level use case diagram for system (e.g. Figure 3 in Use Cases reading for ASTA)Drill down use case diagram for one use case (e.g. Figure 4 in Use Cases reading for ASTA)Note: option due Tues. 2/28 - noonUML intro, Day 10, Tech Mod C27

28 Exercise 10 reference: High Level Use Case Diagram from ReadingNote: the Visio diagrams on the Resources Page may be copied and edited for your Client Project.

About project

Feedback

To ensure the functioning of the site, we use cookies. We share information about your activities on the site with our partners and Google partners: social networks and companies engaged in advertising and web analytics. For more information, see the Privacy Policy and Google Privacy &amp Terms.
Your consent to our cookies if you continue to use this website.