Main Description |
An operation specification has the following outline:
-
Description
-
Input/Output Parameters
-
Non-functional requirements:
-
These are derived from the non-functional requirements associated with the steps in the various Use Cases
that this operation supports.
-
The context in which the operation is used (i.e. a particular Use Case) may be not be captured (e.g. it may
be specified in terms of supporting the minimum performance requirement when all Use Cases are considered)
-
Pre-conditions
-
Post-conditions
-
Superordinate system traceability
-
Optional: use-case (steps) traceability
In most of the cases, the Operations are defined for the system under development and the main subsystems, going with
the decomposition as deep as needed, in a recursive fashion. The Operations are grouped around interfaces along the
main responsibilities of the (sub)system under consideration.
Depending on the granularity level and the usage context, different roles specify, define, refine or use operations as
main inputs for their associated tasks:
-
Architects will describe the main services supported by the architecturally significant elements.
-
Analysts will work with the Architects for mapping the use-case steps into the system's operations.
-
Designers will use them as inputs during the refinement and refactoring stages, the operations being the
building blocks for the Interface Design Specifications.
-
Testers will derive their test cases based on the specified operations.
-
Managers will use them as a basis for phase and iteration planning.
|