Chapter 4: Business Process and Functional Modeling

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/23

flashcard set

Earn XP

Description and Tags

Vocabulary practice flashcards covering terms, notations, and concepts from Chapter 4 on Use Cases and Activity Diagrams.

Last updated 10:43 PM on 9/20/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

24 Terms

1
New cards
<p>Use Case</p>

Use Case

A logical model that illustrates the activities performed by users of a system without specifying how those activities are implemented or discussing technology.

2
New cards
<p>Actor</p>

Actor

A person or external system that derives benefit from and is external to the subject, depicted as a stick figure or as a rectangle containing <> for nonhuman actors.

3
New cards
<p>Subject Boundary</p>

Subject Boundary

A rectangle representing the scope of the subject (such as a system or individual business process), labeled with the subject's name inside or on top.

4
New cards
<p>Association Relationship</p>

Association Relationship

A relationship line in a use-case diagram that links an actor with the use case or use cases with which it interacts.

5
New cards
<p>Include Relationship</p>

Include Relationship

A relationship representing the inclusion of one use case's functionality within another, drawn as a dashed arrow labeled <> pointing from the base use case to the used use case.

6
New cards
<p>Extend Relationship</p>

Extend Relationship

A relationship representing the extension of a use case to include optional behavior, drawn as a dashed arrow labeled <> pointing from the extension use case to the base use case.

7
New cards
<p>Generalization Relationship</p>

Generalization Relationship

A relationship representing a specialized use case or actor linked to a more generalized one, denoted by a line with a hollow arrowhead pointing to the base/superclass.

8
New cards

Overview Use Case

A type of use case that provides a high-level overview of the requirements.

high‐level overview of the requirements.



9
New cards

Detail Use Case

A type of use case that contains all information needed to fully describe the interaction.

10
New cards

Essential Use Case

A type of use case describing only the minimum essential issues necessary to understand the business processes, independent of technology.

minimum essential issues necessary to understand


11
New cards

Real Use Case

A type of use case that goes further than essential requirements to describe a specific set of implementation steps.

12
New cards
<p>Action</p>

Action

A simple, nondecomposable piece of behavior in an activity diagram that is labeled by its name.

13
New cards
<p>Activity</p>

Activity

A construct in an activity diagram used to represent a set of actions, labeled by its name.

14
New cards
<p>Object Node</p>

Object Node

A node in an activity diagram representing an object connected to a set of object flows, labeled by its class name.

15
New cards
<p>Control Flow</p>

Control Flow

A solid arrow in an activity diagram showing the sequence of execution.

16
New cards
<p>Object Flow</p>

Object Flow

A dashed arrow in an activity diagram showing the flow of an object from one activity (or action) to another.

17
New cards
<p>Initial Node</p>

Initial Node

A solid circle in an activity diagram portraying the beginning of a set of actions or activities.

18
New cards
<p>Final-Activity Node</p>

Final-Activity Node

A symbol consisting of a solid circle inside an outer ring, used to stop all control flows and object flows in an activity (or action).

19
New cards
<p>Final-Flow Node</p>

Final-Flow Node

A circle containing an 'X' used in an activity diagram to stop a specific control flow or object flow.

20
New cards
<p>Decision Node</p>

Decision Node

A diamond symbol representing a test condition to ensure control or object flow goes down only one path, labeled with decision criteria.

21
New cards
<p>Merge Node</p>

Merge Node

A diamond symbol used to bring back together different decision paths created using a decision node.

22
New cards
<p>Fork Node</p>

Fork Node

A horizontal or vertical bar used to split behavior into a set of parallel or concurrent flows of activities (or actions).

23
New cards
<p>Join Node</p>

Join Node

A horizontal or vertical bar used to bring back together a set of parallel or concurrent flows of activities (or actions).

24
New cards
<p>Swimlane</p>

Swimlane

A mechanism used to break up an activity diagram into rows and columns to assign individual activities or actions to responsible individuals or objects.