Term
|
Definition
| an activity that the system performs, usually in response to a request by a user |
|
|
Term
|
Definition
| a technique to identify use cases by determining what specific goals or objectives must be completed by a user |
|
|
Term
| Event decomposition technique |
|
Definition
| a technique to identify use cases by determining the external business events to which the system must respond |
|
|
Term
| Elementary business processes (EBPs) |
|
Definition
| the most fundamental task in a business process, which leaves the system and data in a quiescent state; usually performed by one person in response to a business event |
|
|
Term
|
Definition
| something that occurs at a specific time and place can be precisely identified and must be remembered by the system |
|
|
Term
|
Definition
| an event that occurs outside the system, usually initiated by an external agent |
|
|
Term
|
Definition
| a person or group that interacts with the system by supplying or receiving data |
|
|
Term
|
Definition
| an event that occurs as a result of reaching a point in time |
|
|
Term
|
Definition
| an event that occurs when something happens inside the system that triggers some process |
|
|
Term
|
Definition
| checks or safety procedures to protect the integrity of the system and the data |
|
|
Term
| Perfect technology assumption |
|
Definition
| the assumption that a system runs under perfect operating and technological conditions |
|
|
Term
|
Definition
| an acronym for create, read/report, update, and delete; a technique to validate or refine use cases |
|
|
Term
| Brief use case description |
|
Definition
| an often one-sentence description that provides a quick overview of a use case |
|
|
Term
|
Definition
| the UML model used to graphically show use cases and their relationships to actors |
|
|
Term
|
Definition
| the boundary between the computerized portion of the application and the users who operate the application but are part of the total system |
|
|
Term
|
Definition
| a relationship between use cases in which one use case is stereotypically included within the other use case |
|
|
