Product specification

Author: ELCO | Last edited: 11.07.2020

The performance specification and the functional requirement specification are conditional and can be regarded as one side of the same coin. A functional specification defines the minimum requirements for the desired solution. The requirements specification is based on the performance specification and defines the realization of these requirements. The results of a service are evaluated on the basis of the requirements specification.

The requirement specification may contain additional points that were added during the planning and implementation phase or it may only represent a part of the requirement specification because some points will not be implemented at all or not until later.

The requirement specification may contain additional points that were added during the planning and implementation phase or it may only represent a part of the requirement specification because some points will not be implemented at all or not until later.

Topic Performance Specifications

  1. What goals should be achieved by the use of the product?

  2. For which application areas and target groups is the product intended?

  3. What are the main functions of the product from the client's point of view?

  4. What are the main features of the product from the client's point of view?

  5. Are there special requirements for certain functions, for example in terms of speed, quantity or accuracy?

  6. To which quality requirements is particular importance attached?
    For example throughput, reliability, robustness, user-friendliness, etc.

  7. Are there any exceptional requirements?

Topic Requirement Specifications

  1. Definition of all important terms to ensure uniform terminology

  2. Which mandatory criteria, desired criteria, delimitation criteria are required?

  3. Which areas of application (purpose), target groups (who has which qualifications), operating conditions (operating time, supervision)?

  4. Which materials, software, hardware and organisational goods are required?

  5. What does the product do from the user's point of view?

  6. What additional, long-term values/information is available from the user's perspective

  7. Which time and scale related requirements are there?

  8. What are the basic usability requirements?

  9. Which quality requirements, for example, reliability, robustness, usability, efficiency and conformity are particularly important?

  10. What are typical scenarios that the product must meet?

  11. What materials, space, software, hardware and organisational goods are required for development?

  12. Special requirements not yet covered.