Product concept

Project name

Classification	Select an element
Status	Select an element
Program name
Project number
Project manager	Project manager
Version	0.1
Date	Click here to enter a date
Project sponsor	Project sponsor
Author(s)
Distribution

List of changes

Version	Date	Change	Author
0.1

Table 1:	Change control

Description

The product concept describes the project outcome to be achieved. Its structure and level of detail vary depending on the project content. The product concept fleshes out the functional and qualitative requirements and the description of the chosen option in the form of specifications. The product concept is designed in sufficient detail in terms of content and planning to form a reliable basis for the realization (development or procurement) of the product. The product concept forms the basis for product acceptance as the project progresses.

Background

Reference to study

Reference to rough requirements

Reference to selected option

Product description

Intended use

Product classifications

Mass product, serial product, niche product, individual product, service, ...

Rough description and specifications

Conceptual rough description of the product

Product features/characteristics

Function description

Composition/components

A graphical representation of the product and its form helps to recognize the product features and to record the detailed requirements in a structured manner. The graphical overview can be created with various techniques.

Detailed requirements

Detailed description of the product features

Business organization requirements

Organizational requirements are not described here. They are documented in the business organization concept.

Functional requirements

Various techniques can be used to describe the requirements

Per requirement:

Rough requirement	n.nn	Source	Author	Dependence for	Date	13.12.21	Status
Name	Destruction of paper files
Brief functional description	Files are destroyed in such a way that they cannot be reproduced, security standard XY is complied with
Input	Paper files discarded for destruction
Processing steps/rules	Prepare paper files for destruction (remove paper clips) Destroy files with a shredder Empty shredder container and dispose of material
Output	Shredded and disposed files
Acceptance criteria	Paper files at least 3 cm high, paper format A3, paper shreds not reproducible according to security standard XY, destruction of 15 linear meters in 1 hour
Importance 1	Urgency 2	Risk 3	Outlay 4
1) Importance: 5 = mandatory implementation; 4 = very important; 3 = important; 2 = normal; 1 = not important 2) Urgency: 5 = must be implemented immediately, 4 = very urgent, 3 = urgent, 2 = normal, 1 = not urgent 3) Risk/critical nature: 5 = unacceptable risk, 4 = very high risk, 3 = medium risk, 2 = low risk, 1 = no risk whatsoever 4) Outlay: 5 = unacceptable outlay, 4 = very high outlay, 3 = high, 2 = reasonable, 1 = negligible or no outlay

Table 2:	Functional requirements – n.nn

Quality requirement, framework condition

Criteria that the product must meet in order to be approved

Per requirement:

Rough requirement	n.nn	Source	Author	Dependence for	Date	20.12.21	Status
Name
Description incl. quality tolerance
Quality control method (proposal)
Acceptance criteria
Importance 1	Urgency 2	Risk 3	Outlay 4
1) Importance: 5 = mandatory implementation; 4 = very important; 3 = important; 2 = normal; 1 = not important 2) Urgency: 5 = must be implemented immediately, 4 = very urgent, 3 = urgent, 2 = normal, 1 = not urgent 3) Risk/critical nature: 5 = unacceptable risk, 4 = very high risk, 3 = medium risk, 2 = low risk, 1 = no risk whatsoever 4) Outlay: 5 = unacceptable outlay, 4 = very high outlay, 3 = high, 2 = reasonable, 1 = negligible or no outlay

Table 3:	Quality requirements and framework conditions – n.nn

Requirement coverage

ID	Requirement	Assignment to subsystem/component	Assessment of requirement coverage
nn	100%
nn	100%

Table 4:	List of requirements with assignment and coverage

Abbreviations and glossary

Abbreviation/specialist term	Explanation
HERMES	Methodology for projects and programs HERMES 5 is an eCH standard

Table 5:	Abbreviations and glossary

Contents

List of changes	1

Description	1

1	Background	2

2	Product description	2

2.1	Intended use	2

2.2	Product classifications	2

2.3	Rough description and specifications	2

3	Detailed requirements	2

3.1	Business organization requirements	2

3.2	Functional requirements	3

3.3	Quality requirement, framework condition	4

4	Requirement coverage	5

Abbreviations and glossary	6

Contents	7

Tables	7

Tables

Table 1:	Change control	1

Table 2:	Functional requirements – n.nn	3

Table 3:	Quality requirements and framework conditions – n.nn	4

Table 4:	List of requirements with assignment and coverage	5

Table 5:	Abbreviations and glossary	6