Software Engineering Use Cases

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

1/14

flashcard set

Earn XP

Description and Tags

Flashcards for Software Engineering Use Cases Lecture

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

15 Terms

1
New cards

Use Case

Step-by-step description of how a user will use the system-to-be to accomplish business goals

2
New cards

Actors

Environmental agents or actors that will cooperate with the system

3
New cards

Use Case Diagram

Shows relations of the actors and use cases

4
New cards

Use Case Scenarios

Plans for realization of user goals or handling contingencies

5
New cards

Use Case Scenarios or Scripts

Show an envisioned sequence of cooperative interactions between the external actors and the system-to-be

6
New cards

Initiating Actor

Initiates the use case to achieve a goal

7
New cards

Participating Actor

Participates in the use case but does not initiate it

8
New cards

Supporting Actor

Helps the system-to-be to complete the use case

9
New cards

Offstage Actor

Passively participates in the use case, i.e., neither initiates nor helps complete the use case, but may be notified about some aspect of it

10
New cards

<extends> Relationship

Relationships that represent exceptional or seldom invoked cases

11
New cards

<include> Relationship

Relationships that represents behavior that is factored out of the use case for reuse, not because it is an exception

12
New cards

Traceability Matrix

Mapping system requirements to use cases

13
New cards

Purpose of Traceability Matrix

To check that all requirements are covered by the use cases, or that none of the use cases is introduced without a reason

14
New cards

Security and Risk Management

Identifying and preempting the serious risks to system’s safe and successful functioning

15
New cards

System Sequence Diagram

Similar to UML sequence diagrams, but for actor interactions instead of software object interactions