Functional Modeling

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

1/11

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards for reviewing functional modeling concepts, including use cases, event decomposition, and UML diagrams.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

12 Terms

1
New cards

Use Case

An activity that the system performs, usually in response to a request by a user; defines functional requirements using Verb-Noun.

2
New cards

User Goal Technique

A technique to identify use cases by interviewing potential users and refining tasks into specific user goals.

3
New cards

Event Decomposition Technique

A technique to identify use cases by identifying events to which the system must respond, whether external, temporal, or state events.

4
New cards

External Event

An event that occurs outside the system, usually initiated by an external agent or actor.

5
New cards

Temporal Event

An event that occurs as a result of reaching a point in time.

6
New cards

State Event

An event that occurs when something happens inside the system that triggers some process (e.g., reorder point reached).

7
New cards

Use Case Diagram

A UML model used to graphically show use cases and their relationships to actors.

8
New cards

Actor

The UML name for an end user.

9
New cards

Automation Boundary

The boundary between the computerized portion of the application and the users who operate the application.

10
New cards

Includes Relationship

A relationship between use cases where one use case is stereotypically included within the other use case (like a called subroutine).

11
New cards

Use Case Description

A detailed description of a use case, including name, scenario, triggering event, brief description, actors, related use cases, stakeholders, preconditions, postconditions, flow of activities, and exception conditions.

12
New cards

CRUD Technique

A technique (Create, Read/Report, Update, Delete) used to validate use cases and ensure all classes have a complete “cover” of use cases.