Академический Документы
Профессиональный Документы
Культура Документы
Each use case describes how an external user triggers an event to which the
system must repond.
TRIGGER EVENT
THE SYSTEM RESPONDS
PERFORMS ACTIONS BASED ON
THE USE CASE
RETURNS TO THE WAITING STATE
Preconditions- defines the state the system needs to be in before each use
case begin.
Normal Course- description of the major steps that are performed to execute
the response to the event, the inputs used for the steps, and the outputs produced
by the steps.
-include a column in which the information that flows in or out of
the steps is recorded.
Alternative Courses- the steps followed for alternative paths through the
use case are outlined. Alternative courses are included to depict branches in logic
that also will lead to a successful conclusion of the use case.
Postconditions- define the final products of this use case; serve to define the
preconditions for the next use case in the series.
Exceptions- describe any error conditions or exceptions that may occur as the
use case steps are performed. These are not normal branches in decision logic, but
are unusual occurrences or errors that could potentially be encountered and will
lead to an unsuccessful result
of the major inputs and outputs to the use case are listed, along with its source or
destination.
Use cases do explain the users interaction with the system, but they omit a
lot of details that are necessary to know before the system can be developed.
only convey the users point of view. Behind the scenes processing details are
probably not included in the use case.
Transforming the users view into the developers view by creating functional
requirements is one of the important contributions that the systems analyst
makes to the development project