Product requirement specifications (also target concept, specialized fine technical or technical specification) are the contractually binding, detailed description of one achievement, for example the structure of a technical plant, which can be fulfilled, the construction of a tool or also the production of a computer program. Contrary to the work statement contents are precisely, complete and comprehensible as well as with technical definitions of the operating and maintenance environment linked.

Contrary to the technical Design (also technical specification) product requirement specifications describe the planned achievement - in our example the software program - as Black box. Accordingly it does not contain usually the solution of the problems (here the implementation problems).

It is proven practice to use with the production of product requirement specifications in and exclusion principle is called concrete cases explicitly to in or exclude.

After supply of the software frequently over an acceptance test it is determined whether the software fulfills the demands of product requirement specifications.

Structure

Product requirement specifications should be arranged as follows according to Helmut Balzert:

1. Goal regulation
   1. Having criteria: for the product indispensable achievements, which must be fulfilled in each case
   2. Desire criteria: the fulfilment of these criteria is aimed at
   3. Demarcation criteria: these criteria are not to be achieved consciously
2. Product employment
   1. Ranges of application
   2. Target groups
   3. Operating conditions: physical environment of the system, daily period of operation, constant observation of the system by operators or unsupervised enterprise
3. Product overview: short overview of the product
4. Product functions: exact and detailed description of the individual product functions
5. Product data: data from user view, which can be stored on a long-term basis
6. Product achievements: Requirements concerning time and accuracy
7. Quality requirements
8. Use surface: fundamental requirements, rights of access
9. Nichtfunktionale requirements: laws and standards which can be kept, safety requirements, platform dependence
10. Technical product environment
    1. Software: for servers and Client, if available
    2. Hardware: for servers and Client separately
    3. Orgware: organizational basic conditions
    4. Product interfaces
11. Requirements of the development environment
12. Arrangement into partial products

See also

• Work statement
• Requirement analysis
• Software requirement Specification

Related links

• Check lists for product requirement specifications from the IT-range
• Arrangements for product requirement specifications

Articles in category "Product requirement specifications"

We found here 22 articles.

Related Websites

We found here 6 related websites.

• How to write a software requirements specification
  How to write a software requirements specification.


• Modelling Software Requirements - Training Product Specification
  User requirements specifications must also provide the sole criteria for the validation of the end software product. In achieving these goals an effective ...


• Software Requirements Specification Document Template (14-Mar-1996)
  Software Requirements Specification Document Template ... Specifies if this product is intended to be stand-alone, or else used as a component of a larger ...


• Software Requirements Specification Template
  Software Requirements Specification. for. <Project>. Version 1.0 approved. Prepared by <author>. <organization>. <date created>. Table of Contents ...


• Volere Requirements Specification Template
  The other cost of requirements is the amount of money or effort that you have to spend building them into a product. Once the requirements specification is ...


• Writing Software Requirements Specifications
  For technical writers who haven't had the experience of designing software requirements specifications (SRSs, also known as software functional ...