Browse Prior Art Database

Method & apparatus for bringing requirements into Test management tools

IP.com Disclosure Number: IPCOM000218014D
Publication Date: 2012-May-15
Document File: 6 page(s) / 216K

Publishing Venue

The IP.com Prior Art Database

Abstract

Today’s enterprise demand integration between multiple tools and technologies. Disclosed is a method for integrating a requirement management tool with a test management tool for better requirement traceability and avoiding manual mapping. It also describes a method to automate the requirement creation in the test management tool with the appropriate metadata and structure avoiding manual effort and saving time. It discusses about establishing traceability between the original requirements without actually embedding the requirement management tool inside the test management tool while avoiding duplication of requirements.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 6

Method & apparatus for bringing requirements into Test management tools

By definition Test management tools contain test definitions. The test definitions include test plans where test cases are associated with product requirements or application requirements. After execution (automatic or manual) of the test cases, the test results are stored and compared with the expected results. Differences are examined and can lead to the opening of defects that should be removed from the software or application. The key to all the test plans are traceable requirements. In all the test management tools the requirements are either created manually or fed in from flat files. The test cases created are mapped to the requirements and test plans manually for the validation testing. In an enterprise these requirements are stored in the enterprise wide requirement management tools. Since there is no way to communicate to these tools the effort to bring in these requirements is duplicated.

The disclosed method is a generic approach for bringing in requirements from requirement management tools to test management tools and vice-versa without the need of a point- to-point integration.

This consists of the following

i) A method for connecting to the test management tools from requirement management tools and vice-versa


ii) Viewing the appropriate requirements that need to be brought inside the test management tool


iii) Exporting the selected requirements into the test management tool


iv) Creating them in the test management tool in the appropriate structure.


v) Creating the requirements inside the test management tool with relevant details.

These have been described in detail as below.

The system proposes a method for connecting to the test management tools like HP Quality center/ Rational quality manager from requirement management tools like Requisite-pro, rational DOORs etc. and vice-versa. Then the system describes an apparatus for implementing the same method as shown in the figure I.

Flow chart I : Connecting from a Test Management Tool to a Requirement Management tool

1


Page 02 of 6

As a part of this implementation the service oriented architecture concept is leveraged there by reducing the tight coupling or point to point integration of the requirement management tool with the test management tool. Based on this the test management tool can connect to the requirement management tool using a web service based URL, an user id and a password.

The system also provides an apparatus for viewing these requirements before bringing them inside the test management tool.

An additional UI interface is provided to view the requirements from the Test management tool before bringing them into the Test management tool. The UI interface is a graphical interface containing all the necessary details fo...