Note: Hierarchical requirement relationships should not be confused with traceability relationships. A traceability relationship is generally established between different types of requirements, like software and test requirements, whereas hierarchical relationships group requirements of the same type, at the same level of the requirement traceability tree. To create child requirements in a document: In the requirements document, select the information that defines the requirement. Click the tabs and enter the appropriate information to define the requirement.
On the Hierarchy tab, select a parent from the Parent list. To create child requirements in a view: Open an Attribute Matrix based on the requirement type of the requirement you want to create.
Select the requirement that you want to be the parent of the new requirement. You can create a child requirement in a view only if the selected requirement which will become the child's parent is also located in a view that is, it is not located in a document.
Type a description for the child requirement. Create requirement traceability You can use traceability to manage dependencies. As implied in the description of requirement types, no single expression of a requirement stands alone.
The process of decomposing user needs into derived requirements implies relationships between high-level expectations and subsequent artifacts needed for implementation and validation. In effect, one traces to many or vice versa. For example, stakeholder requests are related to the product features proposed to meet them. Product features are traced to individual requirements for specific functional behavior.
Test cases are traced from the requirements they verify and validate. To determine the impact of changes and feel confident that the system conforms to expectations, team members must understand, document, and maintain these traceability relationships.
Traceability is an essential tool for accommodating change and ensuring complete coverage. Establishing clear requirement types can help make traceability easier to implement and maintain.
Select the Traceability Matrix view type. Select one requirement type for the rows and one for the columns of the matrix. In the Traceability Matrix, select a cell that intersects the two requirements for which you want to create a traceability relationship. Use a multiple select action to select multiple cells.
Right-click on the cell and select Trace To or Trace From. A relationship between requirements becomes questionable or suspect if RequisitePro detects that one of the requirements in the relationship has been modified. Moreover, you can define attributes that, when modified, cause traceability relationships to become suspect. Query to retrieve and organize requirements by attribute values or traceability.
The RequisitePro query features provide a method for filtering and sorting requirements in views by limiting the values of one or more attributes or by limiting traceability and specifying the order in which the filtered requirements are displayed. Filtering restricts the information being displayed; sorting determines the order in which information is displayed.
Clicking this button closed the importer. You should now log into SpiraTest using the same user name and password that was used for the import to view the imported project. Once you have completed this initial import, you will now have two systems that can be used together to manage your project's lifecycle.
How they should be used together depends on which methodology you have been using in your RequisitePro project:. Traditional Mode -- In this mode, RequisitePro only contains product requirements and software requirements. These are both loaded into SpiraTest's requirements matrix and can be used as a starting point for developing the necessary test case coverage. In this mode, requirements are managed in RequisitePro and all other artifacts are managed in SpiraTest. Use Cases Mode -- In this mode, RequisitePro contains features, supplementary requirements and use cases.
The features and supplementary requirements are loaded into SpiraTest's requirements matrix, and the use cases are loaded into SpiraTest's test case list. Note that these use cases do not contain any test steps. Note: If you change the install location of either the AppServer, Plug-ins, or Toolbox, you might need to make the same change for the others. Location: Cape Town, South Africa. No comments:. Newer Post Older Post Home. Subscribe to: Post Comments Atom. Simply brilliant! Really offers you the ability to offe
0コメント