CREATION OF A SPECIFICATION¶

The specification forms the bridge between good performance, cost control and scheduling. It also defines the goal-oriented requirements. Specifications are a means of ensuring that the project results (objectives) are defined before the project is implemented. To this end, the project manager clarifies with the core team what the service to be provided should look like, which important requirements must be observed and what must be taken into account. A service specification is drawn up for this purpose, which can be based on templates from the company's internal quality management system. If no template is available, the following exemplary structure can be used. With a little imagination and adaptation, this creates a basis for summarising all expectations and requirements.

Structure of a specification¶

1. General information
1.1 Scope of application
1.2 Documents and rules to be used
1.3 Description of the object (project deliverable)
1.4 Change procedure (form)

2. Quality
2.1 Functional quality
2.2 Operational quality
2.3 Constructive requirements

3. Environment
3.1 Climatic burdens
3.2 Mechanical burdens
3.3 Other environmental burdens

4. Interfaces
4.1 Overview
4.2 Descriptions

5. Testing and quality assurance
5.1 Test types
5.2 Test schedules
5.3 Licensing documents
5.4 Test synopsis

If it isn't possible to provide any information with regard to any of the above items, the names of team members and "to be defined" are written under the item in question. This indicates that the specification will be supplemented at this point. It also indicates where assumptions have been made.