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 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 top-level system 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.
The role responsible for the integrity of the operation set, should ensure that:
-
the operations are unique and there is no overlap between them
-
the related operations are logically grouped around interfaces
-
each operation is properly documented
-
the traceability relationships to other operations and/or use-case steps have been established
-
proper coverage of the use cases or system's operations, based on the scope of the current iteration
|
