This document specifies a simplified subset of ReqView version 1.0 functionality allowing users to capture requirements in a single structured requirement specification document.
Note: This is an example document, which is not complete.
The main purpose of this document is to provide new users a working example of a document describing high-level user needs by means of user stories.
Users should be able to:
1.3 User Roles
1.3.1 Requirements Architect
Requirements Architect defines requirements model and configure the requirements project for other users.
Requirements Architect is typically a QA manager or project manager.
Editor defines project requirements and creates requirements and tests documents.
Editor is typically a requirements engineer, business analyst, project manager, QA engineer or a tester.
Reviewer reads project documents, performs review and provides feedback for improving the content of the document.
Reviewer is typically an internal QA expert reviewing requirements and tests, customer or supplier commenting requirements and setting the requirement acceptance state.
2 User Stories
2.1 Requirements Storage
2.1.1 Document Files
[DEMO-NEEDS-58] As a(n) Editor I want to save document in a file so that users can open the document for further editing or review.
2.1.2 Document Templates
[DEMO-NEEDS-14] As a(n) Architect I want to save a document as a template file so that I can reuse the document structure and configuration of custom attributes for new documents.
[DEMO-NEEDS-33] As a(n) Editor I want to automatically persist my changes so that I do not lose my changes if the tool is unexpectedly terminated before saving into a file.
2.2 Define Requirements
2.2.1 Requirement Description
[DEMO-NEEDS-68] As a(n) Editor I want to specify requirements by a textual description so that the requirements can be reviewed by other users..
2.2.2 Unique IDs
[DEMO-NEEDS-32] As a(n) Editor I want to identify requirements by their unique ID so that I can reference requirements from other documents or communication.
2.2.3 Document Structure
[DEMO-NEEDS-12] As a(n) Editor I want to organize requirements in a tree document hierarchy with numbered sections so that I can easily navigate in the document structure.
2.2.4 Table View
[DEMO-NEEDS-73] As a(n) Editor I want to display a table of requirements so that I can review all requirements information in a single view.
2.2.5 Detailed View
[DEMO-NEEDS-74] As a(n) Editor I want to display all information about the selected requirement so that I can display details about any requirement which are not visible in the requirements table.
[DEMO-NEEDS-17] As a(n) Editor I want to attach images and other documents to requirements so that I can enhance textual requirements with visual content such as mockups, diagrams, etc..
[DEMO-NEEDS-35] As a(n) Editor I want to order requirements by a chosen custom attribute so that I can display requirements sorted by priority, risk, effort, etc..
Tool supports sorting requirements by:
2.3 Manage Requirements
2.3.1 Custom Attributes Configuration
[DEMO-NEEDS-19] As a(n) Architect I want to define additional requirements attributes so that the document can flexibly store additional requirement properties, such as requirement source, priority, status, etc..
2.3.2 Custom Attributes
[DEMO-NEEDS-69] As a(n) Editor I want to set a value of a chosen custom attribute for one or more selected requirements so that I can define additional requirements properties, such as requirements source, prioritize requirements, manage requirement status, define acceptance criteria, etc..
2.3.3 Traceability Configuration
[DEMO-NEEDS-16] As a(n) Architect I want to define types of relationships between requirements so that users can perform traceability analysis for a chosen group of links.
2.3.4 Traceability Links
[DEMO-NEEDS-21] As a(n) Editor I want to link related requirements so that I can analyze requirements coverage, gap in requirements and impact of requirement changes..
[DEMO-NEEDS-34] As a(n) Editor I want to filter requirements so that I can identify and manipulate requirements matching a condition.
Tool supports filtering requirements:
[DEMO-NEEDS-36] As a(n) Editor I want to find keywords so that I can identify and manipulate requirements containing the searched keyword(s).
Tool supports searching requirements containing a given keyword.
2.4 Review Requirements
[DEMO-NEEDS-24] As a(n) Reviewer I want to comment requirements so that I can provide feedback during requirements review.
2.4.2 Traceability Browser
[DEMO-NEEDS-30] As a(n) Reviewer I want to trace related requirements so that I can perform coverage, gap and change impact analysis.
[DEMO-NEEDS-29] As a(n) Reviewer I want to print a document view so that I can review requirements without the need to run the tool.
2.5 Audit Trail
2.5.1 History of Changes
[DEMO-NEEDS-26] As a(n) Editor I want to list all requirement changes so that I can understand how the requirement evolved in time.
2.5.2 Traceability Report
[DEMO-NEEDS-23] As a(n) Reviewer I want to generate a traceability report so that I can analyze coverage, gaps and impact of requirements changes.
2.6.1 Import from Word
[DEMO-NEEDS-27] As a(n) Editor I want to import a requirements specification from a MS Word document so that I can reuse existing requirements specifications or other structured documents.
2.6.2 Import from Excel
[DEMO-NEEDS-71] As a(n) Editor I want to import requirements from a MS Excel spreadsheet so that I can import or update list of requirements.
2.6.3 Export to Word
[DEMO-NEEDS-28] As a(n) Editor I want to to export structured requirements specification to MS Word so that I can share requirements specifications with users without the tool.
2.6.4 Export to CSV
[DEMO-NEEDS-72] As a(n) Editor I want to export filtered list of requirements to MS Excel so that I can reuse or update requirements in another application.
3.1 Startup Time
[DEMO-NEEDS-39] As a(n) Editor I want to quickly start the tool so that I do not need to wait long time for editing a project.
Tool starts in less than 10s even for large projects.
3.2 Edit Response Time
[DEMO-NEEDS-41] As a(n) Editor I want to edit effectively requirements in large documents so that I can work without waiting for tool responses.
Tool updates view after any edit operation in a document with 10000 requirements in less than 1s.
3.3 Document Size
[DEMO-NEEDS-44] As a(n) Editor I want to create large requirements specifications so that I can capture all requirements in a single document even for complex system development projects.
Tool can store documents with 10000 requirements and 100 attachments of total size 100 MB.
[DEMO-NEEDS-42] As a(n) Editor I want to store confidential information in the tool so that I can be sure that no confidential information is sent to the Internet or is compromised by an unauthorized application.
Tool stores all project data in an encrypted persistent application storage and does not send any project information to the internet without user consent.
[DEMO-NEEDS-51] As a(n) Editor I want to run the tool in a browser so that I run the tool on my computer running Windows, Linux or Mac operating system without a need to install it.
Tool runs in the latest version of Chrome and Firefox browsers on Windows PC, Linux PC and a Mac.