Report: Locality Subsystem Operations and Supplementary Requirements |
 |
 |
Extracted from the System Deployment Model , the report records, for each locality (and associated connections), the following: The subsystem operations that are hosted at each locality this determines the computing requirements to be supported at the locality. A description of derived supplementary requirements (derived from System Supplementary Specifications) which specify quality (reliability, maintainability, safety, and so on.), physical and environmental requirements, and development constraints (cost, technical risk, and so forth). From these requirements, the actual characteristics (of each locality and connector) are determined; obviously, these are chosen to meet the explicit requirements at least, but might exceed the requirements if sound engineering practice dictates this for example, to cope with unexpected capacity demands. This report is used to communicate the requirements and design decisions about localities and connections to interested stakeholders. |
|
Relationships
Main Description
Identification and overview
Briefly identify the system and enumerate the localities which this report describes.
Locality Model
Diagram
Include the Locality Diagram from the System Deployment Model. Identify each locality and connection.
Localities
For each locality, include a paragraph which describes the locality (identify the locality and briefly explain its
purpose). Then, for each locality, describe:
Subsystem operations
For each subsystem or subsystem operation hosted at each locality, identify the subsystem, then identify
and briefly describe the hosted subsystem operation.
Supplementary requirements
Describe supplementary requirements (derived from System Supplementary Specifications) which specify quality
(reliability, maintainability, capacity, safety, and so on), physical, environmental requirements and
development constraints (cost, technical risk, and so forth).
Connections
For each connection attached to a locality, identify the connection, then describe link parameters, such as
data rate and supported protocols, and other constraints such as cost and technical risk.
|
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
| |
|