Difference between revisions of "Resource Management Specification"

Revision as of 20:43, 23 February 2012

Overview

A brief overview of the subsystem should be here. It should include the key features.

Key features

Feature1

Feature 1 Description

Feature2

Feature 2 Description

Design

Philosophy

This is the rationale behind the design. An example will be provided.

Architecture

The main software components forming the subsystem should be identified and roughly described. An architecture diagram has to be added here. A template for the representation of the architecture diagram will be proposed together with an opensource tool required to produce it.

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 if appropriate. If it not appropriate, one deployment diagram has to be produced.

Large deployment

A deployment diagram suggesting the deployment schema that maximizes scalability should be described here.

Small deployment

A deployment diagram suggesting the "minimal" deployment schema should be described here.

Use Cases

The subsystem has been conceived to support a number of use cases moreover it will be used to serve a number of scenarios. This area will collect these "success stories".

Well suited Use Cases

UC: software registration

UC: Software Registration

UC: Software Removal

UC: Software Removal

UC: dynamic deployment

UC: Dynamic Deployment

Less well suited Use Cases

Describe here scenarios where the subsystem partially satisfied the expectations.