Requirements management

QPack SDLC Requirements tool for product requirements definition makes it very easy to work with content. By capturing various requirement types, the user can easily create a basic product structure, along with priorities and effort estimations, submitted to predefined dataflow and automatic redirection of data. QPack SDLC tracks requirements' progress at all times, helping organizations to optimize the Software development Lifecycle process.

As a complementary tool for market requirement definition module, which define the problem space, QPack SDLC Product Requirements definition module defines the solution space.

The advantages of QPack SDLC requirement tool over other requirements tools, is that the content management and future release planning capabilities are part of the end-to-end development lifecycle.

Using QPack SDLC Requirements tool, the system architect can easily build a product/project requirements tree based on the predefined market requirements. This tree will be the basic template for all preceding development phases.

QPack SDLC Requirements tool allows the R&D department to add software specifications and development tasks to each requirement, and the QA department to add test cases and test execution sets as part of the testing lifecycle.

The following image shows the product tree, along with test cases under each requirement in a hierarchical manner:

The following image shows a coverage view of all requirements defined for version 4.0, including tasks, defects, test runs, test cases, etc..

Version content management
With QPack SDLC it is easy to plan the content for current and future versions, to change requirements target version, and track content changes, since QPack SDLC is built to mange multiple projects and multiple versions environments.
User can easily define which requirements will be in each version, can defer requirements to future version, can add requirements and change requests to a version-independent pool and later on add them to specific version
User can track each version changes and design the tests required to cover changes.
User can easily map market requirements to product requirements and track market requirements traceability.

The following image shows traceability of market requirements and product requirements

User can schedule and track requirement implementation into releases and iterations, and trace and manage requirement relations to improve understanding and assess impact of changes.

View the following image of requirement relations