1 / 38

Day 11 – UML and Use Case Diagrams

Day 11 – UML and Use Case Diagrams. Unified Modeling Language (UML) Use Case Diagrams Exercise 10 (in class) – Use Cases for Client Project Exercise 11 (soon ) – Functional Requirements Table. Unified Modeling Language (UML).

kesia
Download Presentation

Day 11 – UML and Use Case Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Day 11 – UML and Use Case Diagrams • Unified Modeling Language (UML) • Use Case Diagrams • Exercise 10 (in class) – Use Cases for Client Project • Exercise 11 (soon ) – Functional Requirements Table

  2. Unified Modeling Language (UML) Object-oriented development approach – some times called OO modeling or OO techniques Use Cases most common UML technique

  3. Iterative Development – MIS 374 Use Case Diagramsare techniques to learn requirements

  4. High Level Agile SDLC from Ambler Reading Use Case Diagramsare techniques to learn requirements Figure 4, Agile SDLC, Scott Amblerhttp://www.ambysoft.com/essays/agileLifecycle.html “Model Storming” to learn detailed requirements is part of Construction Iterations (aka A-D-C-R loops).

  5. At Microsoft you live and die by your ability to white board.

  6. Scott Ambler’s agilemodeling.com Start with a quick diagram showing all system users. Figure 2 in the reading today by Scott Ambler.

  7. Use Case Diagram Format The To-Be System is inside the rectangle Ovals depict each use case -- an event or system uses by someone (or some system) that interacts with the proposed system. Figure 1 in the UML-Use Case Diagram reading today.

  8. Quick System Diagram – hand-drawn

  9. Use Case diagram – with Visio Actors are roles or systems that interact with system

  10. Visio Software Design Shapes DFD tools UML tools

  11. Example for Latinitas’ Case This Use Case diagram was created by 2007 UT MIS grad, Gretel Paronzini-Fredette Gretel 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.

  12. High Level Use Case Diagram –ASTA Skill Set System * Figure 3 in UML-Use Casereading today. * Drill down use case details for Search Skill set are provided in Figure 4

  13. High Level Use Case Diagram Notes, re: DFDs Event (use case) names are verb-noun like DFD processes No data stores Focus is on interaction of Actors (system users) with the system Figure 3 in UML-Use Case reading today.

  14. High Level Use Case Diagram Actors pointing to other actors indicate types. Create proposal uses Search Skill Set Figure 3 in UML-Use Casereading today. Update skill set extends Create Skill Set

  15. The reality of requirements analysis

  16. Analysis Techniques – List from Requirements Section of Project Charter Analysis Techniques + Organizational Impact Analysis in the Organization Section of the Charter

  17. 333k Process: Written Specs  Software

  18. UPOD Team Members: Alex Gold Alyssa Rains (the lone junior) Nick Russell Rachel Krebs Joe Rennemeyer

  19. Meeting 2: Team used existing site like click through prototype with clients Stakeholders List Root Cause Analysis Organizational Impact Analysis

  20. Meeting 3: Evaluation Table

  21. Last row a mix of functional & non-functional requirements

  22. eVision Examples – Judy Paul Website Judy’s public pages (customer side)  Paypal manages payments. Judy’s private pages for managing her site.

  23. eVision Examples – Judy Paul Website Exercise 11 – Create this week (recommended); full credit ‘til 3/8

  24. From: Austin Masterton, Sp 09 gradDate: July 12, 2009 Sharon and Eleanor,When I was in class in the spring, I did not see why any individual would want to create a DFD or why any organization would pay someone to put together a use case diagram.

  25. From: Austin Masterton, Sp 09 gradDate: July 12, 2009 I recently began my position as a business analyst with Chevron, and I can safely say that I’ve utilized more of the ideas and tools presented in your course than from any other I class I took in 4 years at UT.

  26. After seeing the systems that my business unit develops and maintains, I realize there is no better way to get a handle on a complex tool than the methods you required for our class projects.

  27. Because I entered Chevron with a better skill setthan BAs who had been here for months, I was able to hit the ground running and impress my manager in the process. Thanks, Austin

  28. Page 1 of 50-page DFD

  29. Page 9 of 50-page DFD

  30. Day 11 – UML and Use Case Diagrams • Unified Modeling Language (UML) • Use Case Diagrams • Exercise 10 (in class) – Use Cases for Client Project • Exercise 11 (soon ) – Functional Requirements Table

  31. Client Project Question 1 On a scale of 1 – 5, how clear are your team roles? 1 = not clear5 = very clear

  32. SOLUTION: SCOPE CREEP

  33. Client Project Question 2On a scale of 1 – 5, how set are your software tools ? 1 = not at all set5 = absolutely set

  34. IDENTIFYING THE LIST OF ACTORS AND STAKEHOLDERS FOR A SYSTEM AND THEN LISTING THEIR GOALS PROVIDES THE BASIS FOR THE USE CASES A stakeholder is someone or something that has a vested interest in the behavior of the use case The primary actor is the stakeholderthat is calling on the system toperform some service (user goal) View customer order history Buy a movie online Etc. You may want to build an Actor Profile table that defines and describes the actors of a system

  35. USE CASES SHOULD BE WRITTEN IN AN ITERATIVE, BREADTH-BEFORE-DEPTH MANNER AND INCORPORATE STAKEHOLDER FEEDBACK EARLY & OFTEN Use cases should be written following 4 steps or iterations Step 1: Actor, Stakeholder and Use Case Lists (with brief description) Step 2: Main Flow completion (start with high-priority & high-risk) Step 3: Alternate and Exception Flow List Step 4: Alternate and Exception Flow details Write use cases in an iterative, breadth-before-depth manner To gain perspective, assemble a balanced team of business analysts and developers to write and review use cases Solicit stakeholder feedback early and often Prioritize use cases early and often

  36. Case StudyLarge Investment Bank CEO Senior VP CIO PMO Business Sponsor IT Program Manager Architecture Governance Business Manager Development Manager Infrastructure Manager Compliance Users Business Analysts Development Team Infrastructure Team Audit QA/Testing Team Quick iterations (aka sprints) require a close working environment for developers and users. More detailed docs are needed when the development team can’t work directly with users. Deployment Team

  37. Exercise10:In classClient ProjectTeam work • Stakeholders list – include “end user” designation for all direct system users • High Level use case diagram for system (e.g. Figure 3 in reading for ASTA) • Drill down Use case diagram for one use case (e.g. Figure 3 in reading for ASTA) • Note: e-mail option due Fri. 3/4-noon

More Related