Requirements Management

Verona-RM provides a framework for controlling the requirements lifecycle, providing clear definition of release content, with end-to-end traceability. Verona-RM benefits all stakeholders by ensuring there is one common set of requirements for the project, and that all changes in status are communicated.
Requirements may be entered into a release-independent repository for initial screening, or directly into a specific release.

Requirements Capture

Requirements are captured using a WYSIWYG Rich Text editor. A standard template is provided with fields for requirements title, description, and priority. User-defined fields may be added for tailoring to your organization's specific needs.

Requirements Analysis

Once requirements have been proposed, the stakeholders have the opportunity to comment on the details, propose refinements and suggest implementation priorities. Resolution of contradictory or conflicting requirements also occurs during this process. Once the customer-facing requirements have begun to emerge, detailed technical requirements can be added at a level that is implementable and testable. Verona supports this classification and nesting structure with unique requirements identifiers and a classification scheme.

Requirements Review/Approval

Prior to review, requirements need to be packaged into the appropriate level and type of requirements specification, for example a Market Requirements Specification or an Engineering Specification. Verona users can organize and export requirements into the appropriate type of specification, and then select a set of reviewers to confirm the correctness of the requirements. Approvers are typically people who have the authority to assign resources to the project or people who will be responsible for managing its delivery (project managers and line managers). Verona's document control module makes this a very smooth and simple process. The system will also maintain all of the records you need to satisfy a typical quality system audit like ISO 9001, or TL 9000.

Release Baselining

One the requirements have been reviewed and approved they must be baselined. Release baselining is the process whereby individual requirements are allocated and committed to specific releases for implementation. A simple interface is provided to support the allocation of requirements individually or via bulk import from the requirements database. Throughout each of these process steps all requirements evolve through a set of state transitions from submitted to committed.

Requirements Change Control

Changing requirements is a reality for many organizations. Built in change control ensures that all proposed changes are reviewed and approved. The updates are communicated to the entire team via email alerts, and a revision history is maintained.

Requirements Test Coverage and Traceability

Requirements may be linked other development artifacts and also test cases. Visibility is provided to demonstrate traceability between market requirements, technical requirements test cases and test defects. Reports are provided to show test coverage for each requirement in a release, and to expose and gaps in test plans.