Chapter 5 Overview: Use Cases and Modeling Techniques
Call Kai
Learn
Practice Test
Spaced Repetition
Match
Flashcards
Knowt Play1/9
There's no tags or description
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai |
|---|
No analytics yet
Send a link to your students to track their progress
10 Terms
Use Case Description
A detailed narrative describing how a user interacts with the system, including actors, flow, and exceptions.
Activity Diagram
To show the flow of actions, decisions, and loops within a use case.
System Sequence Diagram (SSD)
A UML diagram showing input/output messages between an actor and the system object for a use case.
Notation for messages in SSDs
[condition] returnValue := messageName(parameterList), with * for loops and [ ] for conditions.
Frame types in SSDs
Loop Frame: for repeating actions; Opt Frame: for optional behavior; Alt Frame: for if-else conditions.
CRUD
Create, Read (or Report), Update, Delete.
Purpose of CRUD analysis
To ensure all domain classes are fully supported by corresponding use cases.
Steps of CRUD analysis
1. Identify domain classes 2. Verify CRUD coverage 3. Fill in CRUD matrix 4. Add missing use cases 5. Assign responsibility.
Importance of model integration
To ensure consistency and completeness across all diagrams and specifications.
Models consistent in use case modeling
1. Use case descriptions 2. Activity diagrams 3. System sequence diagrams (SSDs).
