Chapter 5 Overview: Use Cases and Modeling Techniques

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/9

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

10 Terms

1
New cards

Use Case Description

A detailed narrative describing how a user interacts with the system, including actors, flow, and exceptions.

2
New cards

Activity Diagram

To show the flow of actions, decisions, and loops within a use case.

3
New cards

System Sequence Diagram (SSD)

A UML diagram showing input/output messages between an actor and the system object for a use case.

4
New cards

Notation for messages in SSDs

[condition] returnValue := messageName(parameterList), with * for loops and [ ] for conditions.

5
New cards

Frame types in SSDs

Loop Frame: for repeating actions; Opt Frame: for optional behavior; Alt Frame: for if-else conditions.

6
New cards

CRUD

Create, Read (or Report), Update, Delete.

7
New cards

Purpose of CRUD analysis

To ensure all domain classes are fully supported by corresponding use cases.

8
New cards

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.

9
New cards

Importance of model integration

To ensure consistency and completeness across all diagrams and specifications.

10
New cards

Models consistent in use case modeling

1. Use case descriptions 2. Activity diagrams 3. System sequence diagrams (SSDs).