When you start ReqView the first time, the application starts a New User Tour and opens a sample Demo Project to help you get started with ReqView more easily.
To open the Demo Project later, close your current project and click the Demo Project button displayed in the center pane under the “No project is loaded.” message.
Note: You can edit the demo project without any limitation, even with the FREE plan.
The main purpose of this project is to provide new users a working example how to specify and manage requirements for a SW development project in ReqView.
This project describes user needs, risks, SW requirements, verification tests and solution architecture for a simplified functionality of ReqView application version v1.0.
Note: This is an example project, which is not complete.
Project Data Model
The following diagram illustrates project documents and types of traceability links:
- NEEDS: User Needs — the highest level user needs described as user stories and constraints, see also User Stories Example
- RISKS: Failure Mode and Effects Analysis — assessment of information security risks using the FMEA method
- SRS: Software Requirements Specification — low-level SW requirements derived from user stories or from corrective actions mitigating project risks, , see also SRS Example
- TESTS: Verification Tests — test cases verifying functionality described by the SW requirements
- ARCH: Architecture — the architecture of the application described by the SW requirements
- Satisfy — satisfaction links leading from downstream SW requirements to the related highest level user needs (M:N)
- Mitigate — mitigation links leading from downstream SW requirements to the related corrective action of a project information security risk (M:N)
- Verify — verification links leading from test cases to the related SW requirements (M:N)
- Implement — implementation links leading from SW components in the SW architecture to the related SW requirements (M:N)