1. Day 11 – UML and Use Case Diagrams
Unified Modeling Language (UML)
Use Case Diagrams
Exercise 10 (in class today, one per CP team) Use Cases for Client Project
2. Stakeholders Table
Exercise 11 (due Monday, one per CP team) – Functional Requirements Priority Table Non-Functional Requirements
UML intro, Day 11

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
• 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 C 2

3. Use Case Diagrams in SDLC
Use case diagrams aid in the analysis
and documentation
of high level requirements for
scope & stakeholders
Drill down use case diagrams
aid in defining functional requirements one module
at a time.
Drill down to design each module.
Final
Construction
Phase(s)
Inception
Phase(s) 3

4. Use Case Diagram Format
The System is inside the rectangle
Ovals 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 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).
Figure 1 in the UML-Use Case Diagram reading for today.
UML intro, Day 11

5. Quick System Diagram – hand-drawn
Use Case diagram – hand drawn preliminary drawing for eStore shows actors that system must handle.
UML intro, Day 10, Tech Mod C
UML intro, Day 11 5

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

7. Visio Software and Database Category
DFD tools
UML tools
UML intro, Day 10, Tech Mod C 7

8. Exercise 10 Resource: Use Case Diagrams from Reading

9. 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.
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

10. High Level Use Case Diagram – ASTA Skill Set System*
* Drill down use case details for
Search Skill set are provided in
Figure 4
Figure 3 in UML-Use Case reading today.
UML intro, Day 11

11. High Level Use Case Diagram
Notes, re: DFDs
Event (use case) names are verb-object like DFD processes
No data stores
Focus is on interaction of Actors (system users) with the system
No arrow heads for lines connecting actor and use case, since considered two-way
Figure 3 in UML-Use Case reading today.
UML intro, Day 11

12. High Level Use Case Diagram
Provide employee information extends Request search
Figure 4
in UML-Use Case reading today.
Select skills uses Request search
UML intro, Day 11

13. Goal of Analysis:
Learn what needs coding before coding

14. Client Project Question 1
On a scale of 1 – 5, how similar is your project to 333k?
1 = not similar 5 = very similar

15. Client Project Question 2
On a scale of 1 – 5, how clear is your scope?
1 = not clear 5 = very clear

16. Client Project Question 3
On a scale of 1 – 5, how clear is your list of stakeholders?
1 = not clear 5 = very clear

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

18. Meeting 3: Evaluation Table

21. Web Flow Example – Judy Paul Website
Judy’s public pages (customer side)
 Paypal manages payments.
Judy’s private pages for managing her site.

22. Functional Priorities – Judy Paul Website
Exercise 11 – Create this week (recommended);
full credit
‘til 3/5
UML intro, Day 10, Tech Mod C 22

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

24. Web Flow As Basis for Assigning Functional Expertise
Judy’s public pages (customer side)
 Paypal manages payments.
Judy’s private pages for managing her site.

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

26. Exercise 11 Reminder: Bring to Class Monday 3/5
Create for review with your client for your client project meeting this week:
Functional Requirements Priority Table (draft)
Non-Functional Requirements Summary (draft)
Turn in one print copy for your client project team.
UML intro, Day 10, Tech Mod C 26

27. Exercise 10: In class Client Project Team work
Stakeholders Table
High 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 - noon
UML intro, Day 10, Tech Mod C 27

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

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