3 min read
last updated: 06/24/2022
Templates for Requirement Engineering
ReqEdit offers templates for different use cases between customer and supplier according to Prostep ivip Recommendations. Please keep in mind that only ReqIF Archives (.reqifz) supports images/file attachments.
To open a template click File / New Archive … You can select from different templates.
Template prostep ivip – All attributes
You can use this template in relation with your suppliers for request clarification for a single product variant use case.
The template includes the necessary attributes, as
Customer status, with the options Not To Evaluate / To Evaluate / Accepted / Not accepted / To be clarified / Proposed to discard / Discarded.
Supplier status, with the options Agreed / Not Agreed / Agreed with comment/ To be clarified / Discard Deployed.
The attributes of this specification documents are:
Template prostep ivip – with Product variant
This template helps tracking the statuses of requests if there are more product variants.
The attributes Customer status and Supplier status have the same values as in case of template Template prostep ivip – All attributes.
Template prostep ivip – with Revision
This template includes an attribute Revision, for use cases where they are needed. The attributes Customer status and Supplier status have the same values as in case of template Template prostep ivip – All attributes.
Template prostep ivip – simple
This template includes only the main attributes of a requirement document. The attributes Customer status and Supplier status have the same values as in case of template Template prostep ivip – All attributes. Attributes as Revision or Product variant are not included.
We recommend to use ReqIFz (archive) for the following templates. You can add each of the templates to a single Archive with File / Add -> New document to the current file. So it’s possible to link user stories, bugs and test cases and add images/ file attachments.
Scrum – Backlog
This template can be used to have a list of the client’s requirements. You can write epics, user stories, or just mark text as information or heading (in the Type column). Different colors for each status help visually the user. Each requirement can have different status: New / Draft / Final / In Progress / Obsolete / Implemented / Duplicate. The template includes also “Business Value” and “Definition of Done” Columns.
Scrum – Buglist
This template collects and lists the bugs reported by users / customers / internal stakeholders. The user of the template can set in the Type column Bug / Heading / Information. The column Status can be set as New / Open / In implementation / Solved / Not Fixed. The Column Scope can be set as Installer / GUI / Business logic / Plugins. There are two additional attributes to add the sprint number/iteration, when a bug is fixed, and also a Bug identifier.
This template can be used for test documentation. The column Type can set texts as Heading / Information / Test Suite / Test Case / Test step. The Column Status sets as New / Draft / Final / Obsolete / Duplicate. The template includes place for Test description and Expected results.