Carry out prototyping
Purpose
With prototyping, simplified but largely functional solution approaches can be created and tested. This permits checking of the feasibility or usability of the focused solution, and where applicable its helpfulness and acceptance. In addition to the technical and functional criteria, the appearance or the dimensions and proportions of the product and the visualized idea for services can also be assessed.
Basic idea
The creation of a prototype - or perhaps only a model in the case of products - is a risk-minimizing measure. Prototyping can be carried out once or several times in different phases depending on the project situation. A prototype can be reusable or disposable. Depending on the findings, the next steps are determined.
HERMES-specific
As needed, prototyping is carried out once or several times over the course of the project. The required basis/prerequisites depend on the needs and the project status.
The objectives and the concept as well as the outcomes of the prototype are recorded in the prototype documentation.
The prototype is developed and the outcomes from the prototyping are evaluated.
Basis/prerequisites
Activities
-
Develop objectives, concept, and methodology for the prototype.
-
Create prototype.
-
Evaluate prototype.
-
Document outcomes and conclusions and incorporate them into further planning.
-
Destroy prototype or ensure reusability.
Outcomes
Relationships
Module | Task | Task responsibility | Outcome | Involved in creation of outcome |
---|---|---|---|---|
Project foundations | Carry out prototyping | Developer | Prototype realized | Developer, User representative , IT architect |
Prototype documentation | Developer, IT architect | |||
Product | Carry out prototyping | Developer | Prototype realized | Developer, User representative |
Prototype documentation | Developer | |||
IT system | Carry out prototyping | Developer | Prototype realized | Developer, User representative , IT architect |
Prototype documentation | Developer |