Difference between revisions of "Subsystem Specification Template"
m (→Design) |
m (→Large deployment) |
||
| Line 27: | Line 27: | ||
=== Large deployment === | === Large deployment === | ||
| + | |||
| + | A deployment diagram suggesting the deployment schema that maximizes scalability should be described there. | ||
=== Small deployment === | === Small deployment === | ||
Revision as of 17:37, 3 February 2012
Overview
A brief overview of the subsystem should be there. It should include the key features.
Key features
- Feature1
- Description
- Feature2
- Description
Design
Philosophy
This is the rationale behind the design.
Architecture
The main software components forming the subsystem should be identified and roughly described. A diagram should be there.
Deployment
Usually, a subsystem consists of a number of number of components. This section describes the setting governing components deployment, e.g. the hardware components where software components are expected to be deployed. In particular, two deployment scenarios should be discussed, i.e. Large deployment and Small deployment.
Large deployment
A deployment diagram suggesting the deployment schema that maximizes scalability should be described there.
Small deployment
Use Cases
The subsystem has been conceived to support a number of scenarios moreover it will be used to serve a number of scenarios. This area will collect these "success stories".
