21 terms

401 Chapter 5 - Modeling System Requirements

use case
an activity the system performs
user goal technique
an approach for identifying use cases in which an analyst talks to all users to get them to describe their goals in using the system
CRUD technique
an approach in which an analyst looks at each type of data and includes use cases that create the data, read or report on the data, update the data, and delete the data
elementary business process
a task that is performed by one person, in one place, in response to a business event; it adds measurable business value and leaves the system and its data in a consistent state
an occurrence at a specific time and place that can be described and is worth remembering
event decomposition
an analysis technique that focuses on identifying the events to which a system must respond and then determining how the system must respond
external event
an event that occurs outside the system, usually initiated by an external agent or actor
temporal event
an event that occurs as a result of reaching a point in time
state event
an event that occurs when something happens inside the system that triggers the need for processing
system controls
checks or safety procedures put in place to protect the integrity of the system
perfect technology assumption
the assumption that events should be included during analysis only if the system would be required to respond under perfect conditions
event table
a catalog of use cases that lists events in rows and key pieces of information about each event in columns
a signal that tells the system that an event has occurred, either the arrival of data needing processing or a point in time
an external agent or actor that supplies data to the system
an output, produced by the system, that goes to a destination
an external agent or actor that receives data from the system
use case description
lists the processing details for a use case
in UML diagrams, a person who uses the system
scenario or use case instance
a unique set of internal activities within a use case that represents a unique path through the use case
conditions that must be true before a use case begins
conditions that must be true upon completion of the use case