IP Library Granted Patent US 8,397,208
Granted Patent B2
US 8,397,208 · App. 11/849,081 · Granted Mar 12, 2013

Method and system for baselining across multiple domains

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,397,208
App. No.
11/849,081
Granted
Mar 12, 2013
Kind
B2
Abstract

Techniques are provided for baselining across multiple domains. Relationship information that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A particular requirement object from the collection of requirement objects is determined. Based on the relationship information, one or more configuration management objects that are associated with the particular requirement object are determined. A baseline that includes copies of the one or more configuration management objects is created and stored, where the copies include specific versions of the one or more configuration objects.

Claims (100)

1. A computer-implemented method comprising:

storing relationship information that associates a collection of requirement objects with a set of configuration management objects;

wherein the collection of requirement objects is defined in a requirement management system for a software product;

wherein the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product;

determining, based on the relationship information, one or more configuration management objects, from the set of configuration management objects, that are associated with a particular requirement object; and

creating and storing a baseline that includes copies of the one or more configuration management objects, wherein the copies of the one or more configuration management objects include specific versions of the one or more configuration management objects.

2. The computer-implemented method as recited in claim 1 , wherein creating and storing the baseline further comprises including a copy of the particular requirement object into the baseline, wherein the copy of the particular requirement object includes a specific version of the particular requirement object.

3. The computer-implemented method as recited in claim 2 , further comprising storing audit trail information, wherein the audit trail information associates the baseline with the specific version of the particular requirement object.

4. The computer-implemented method as recited in claim 1 , wherein:

each requirement object in the collection of requirement objects is a set of data that specifies one or more intended characteristics of the software product; and

each configuration management object of the set of configuration management objects is used in the development of the software product.

5. The computer-implemented method as recited in claim 1 , further comprising:

determining that a change has been made to the particular requirement object; and

determining the one or more configuration management objects further comprises:

inspecting the relationship information to determine which configuration management objects, from the set of configuration management objects, are affected by the change made to the particular requirement object; and

determining that the one or more configuration management objects are those configuration management objects, from the set of configuration management objects, that are affected by the change made to the particular requirement object.

6. The computer-implemented method as recited in claim 1 , wherein storing the relationship information further comprises:

receiving first input that identifies the particular requirement object in the collection of requirement objects;

receiving second input that identifies the one or more configuration management objects in the set of configuration management objects; and

storing one or more links as at least part of the relationship information based on the first input and the second input, wherein the one or more links respectively identify the one or more configuration management objects in association with the particular requirement object.

7. The computer-implemented method as recited in claim 1 , wherein the particular requirement object is one or more of:

a functional requirement object that specifies one or more functional characteristics of the software product;

a design requirement object that specifies one or more design characteristics of the software product;

a marketing requirement object that specifies one or more marketing characteristics of the software product;

a customer requirement object that specifies one or more characteristics that are requested by a customer of the software product;

a security requirement object that specifies one or more security characteristics of the software product;

a hardware requirement object that specifies one or more hardware characteristics of the software product; and

a test-case requirement object that specifies one or more test cases that need to be performed in the development of the software product.

8. The computer-implemented method as recited in claim 1 , wherein the one or more configuration management objects include at least one of:

an item object that comprises a file and attribute information associated with the file, wherein the attribute information comprises a version of the file;

a change request object that comprises metadata information indicating one or more issues associated with the development of the software product; and

a development task object that comprises metadata information indicating one or more development tasks that need to be performed in the development of the software product.

9. The computer-implemented method as recited in claim 1 , wherein:

creating and storing the baseline further comprises including a copy of the particular requirement object into the baseline, wherein the copy of the particular requirement object includes a specific version of the particular requirement object; and

the specific versions of the one or more configuration management objects and the specific version of the particular requirement object are associated with a specific project version of the software product.

10. The computer-implemented method as recited in claim 1 , wherein:

the particular requirement object comprises a plurality of sub-requirement objects;

the one or more configuration management objects comprise a plurality of development task objects; and

storing the relationship information further comprises storing a plurality of links as at least part of the relationship information, wherein a particular link of the plurality of links associates a particular development task object of the plurality of development task objects with a particular sub-requirement object of the plurality of sub-requirement objects.

11. The computer-implemented method as recited in claim 1 , wherein determining the one or more configuration management objects further comprises:

inspecting the relationship information to determine which configuration management objects, from the set of configuration management objects, are associated with the particular requirement object;

determining that the one or more configuration management objects are those configuration management objects, from the set of configuration management objects, that are associated with the particular requirement object; and

comparing one or more criteria to attribute information of the one or more configuration management objects in order to determine the specific versions of the one or more configuration management objects that are to be included in the baseline.

12. The computer-implemented method as recited in claim 1 , further comprising:

determining a requirement object from the collection of requirement objects that is different than the particular requirement object; and

determining at least one configuration management object, from the set of configuration management objects, that is associated with the different requirement object based on the relationship information;

wherein creating and storing the baseline further comprises excluding any copies of the at least one configuration management object from the baseline.

13. The computer-implemented method as recited in claim 1 , further comprising:

based on the relationship information, generating impact analysis information which indicates that the one or more configuration management objects would be affected by a change to the particular requirement object; and

providing the impact analysis information to a user.

14. A non-transitory machine-readable medium comprising one or more stored instructions which, when processed by one or more processors, cause:

storing relationship information that associates a collection of requirement objects with a set of configuration management objects;

wherein the collection of requirement objects is defined in a requirement management system for a software product;

wherein the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product;

determining, based on the relationship information, one or more configuration management objects, from the set of configuration management objects, that are associated with a particular requirement object; and

creating and storing a baseline that includes copies of the one or more configuration management objects, wherein the copies of the one or more configuration management objects include specific versions of the one or more configuration management objects.

15. The non-transitory machine-readable medium as recited in claim 14 , wherein the instructions that cause creating and storing the baseline further comprise instructions which, when processed by the one or more processors, cause including a copy of the particular requirement object into the baseline, wherein the copy of the particular requirement object includes a specific version of the particular requirement object.

16. The non-transitory machine-readable medium as recited in claim 15 , wherein the one or more stored instructions further comprise instructions which, when processed by the one or more processors, cause storing audit trail information, wherein the audit trail information associates the baseline with the specific version of the particular requirement object.

17. The non-transitory machine-readable medium as recited in claim 14 , wherein:

each requirement object in the collection of requirement objects is a set of data that specifies one or more intended characteristics of the software product; and

each configuration management object of the set of configuration management objects is used in the development of the software product.

18. The non-transitory machine-readable medium as recited in claim 14 ,

further comprises instructions which, when processed by the one or more processors, cause determining that a change has been made to the particular requirement object; and

wherein the instructions that cause determining the one or more configuration management objects further comprise instructions which, when processed by the one or more processors, cause:

inspecting the relationship information to determine which configuration management objects, from the set of configuration management objects, are affected by the change made to the particular requirement object; and

determining that the one or more configuration management objects are those configuration management objects, from the set of configuration management objects, that are affected by the change made to the particular requirement object.

19. The non-transitory machine-readable medium as recited in claim 14 , wherein the instructions that cause storing the relationship information further comprise instructions which, when processed by the one or more processors, cause:

receiving first input that identifies the particular requirement object in the collection of requirement objects;

receiving second input that identifies the one or more configuration management objects in the set of configuration management objects; and

storing one or more links as at least part of the relationship information based on the first input and the second input, wherein the one or more links respectively identify the one or more configuration management objects in association with the particular requirement object.

20. The non-transitory machine-readable medium as recited in claim 14 , wherein the particular requirement object is one or more of:

a functional requirement object that specifies one or more functional characteristics of the software product;

a design requirement object that specifies one or more design characteristics of the software product;

a marketing requirement object that specifies one or more marketing characteristics of the software product;

a customer requirement object that specifies one or more characteristics that are requested by a customer of the software product;

a security requirement object that specifies one or more security characteristics of the software product;

a hardware requirement object that specifies one or more hardware characteristics of the software product; and

a test-case requirement object that specifies one or more test cases that need to be performed in the development of the software product.

21. The non-transitory machine-readable medium as recited in claim 14 , wherein the one or more configuration management objects include at least one of:

an item object that comprises a file and attribute information associated with the file, wherein the attribute information comprises a version of the file;

a change request object that comprises metadata information indicating one or more issues associated with the development of the software product; and

a development task object that comprises metadata information indicating one or more development tasks that need to be performed in the development of the software product.

22. The non-transitory machine-readable medium as recited in claim 14 , wherein:

the instructions that cause creating and storing the baseline further comprise instructions which, when processed by the one or more processors, cause including a copy of the particular requirement object into the baseline, wherein the copy of the particular requirement object includes a specific version of the particular requirement object; and

the specific versions of the one or more configuration management objects and the specific version of the particular requirement object are associated with a specific project version of the software product.

23. The non-transitory machine-readable medium as recited in claim 14 , wherein:

the particular requirement object comprises a plurality of sub-requirement objects;

the one or more configuration management objects comprise a plurality of development task objects; and

the instructions that cause storing the relationship information further comprise instructions which, when processed by the one or more processors, cause storing a plurality of links as at least part of the relationship information, wherein a particular link of the plurality of links associates a particular development task object of the plurality of development task objects with a particular sub-requirement object of the plurality of sub-requirement objects.

24. The non-transitory machine-readable medium as recited in claim 14 , wherein the instructions that cause determining the one or more configuration management objects further comprise instructions which, when processed by the one or more processors, cause:

inspecting the relationship information to determine which configuration management objects, from the set of configuration management objects, are associated with the particular requirement object;

determining that the one or more configuration management objects are those configuration management objects, from the set of configuration management objects, that are associated with the particular requirement object; and

comparing one or more criteria to attribute information of the one or more configuration management objects in order to determine the specific versions of the one or more configuration management objects that are to be included in the baseline.

25. The non-transitory machine-readable medium as recited in claim 14 , wherein the one or more stored instructions further comprise instructions which, when processed by the one or more processors, cause:

determining a requirement object from the collection of requirement objects that is different than the particular requirement object; and

determining at least one configuration management object, from the set of configuration management objects, that is associated with the different requirement object based on the relationship information;

wherein the instructions that cause creating and storing the baseline further comprise instructions which, when processed by the one or more processors, cause excluding any copies of the at least one configuration management object from the baseline.

26. The non-transitory machine-readable medium as recited in claim 14 , wherein the one or more stored instructions further comprise instructions which, when processed by the one or more processors, cause:

based on the relationship information, generating impact analysis information which indicates that the one or more configuration management objects would be affected by a change to the particular requirement object; and

providing the impact analysis information to a user.

Assignments (13)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 11, 2026
From: SERENA SOFTWARE, INC.
To: MICRO FOCUS LLC
Reel/Frame 073758/0887 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
RELEASE OF SECURITY INTEREST REEL/FRAME 039136/0241 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: SERENA SOFTWARE, INC
Reel/Frame 062623/0123 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
NOTICE OF SUCCESSION OF AGENCY Recorded May 2, 2017
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 042383/0830 →
SECURITY INTEREST Recorded Jul 12, 2016
From: SERENA SOFTWARE, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 039136/0241 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY'S NAME PREVIOUSLY RECORDED AT REEL: 026073 FRAME: 0206. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY AGREEMENT. Recorded Jun 9, 2016
From: LEHMAN COMMERCIAL PAPER INC., AS RESIGNING ADMINISTRATIVE AGENT AND COLLATERAL AGENT
To: BARCLAYS BANK PLC, AS ADMINISTATIVE AGENT
Reel/Frame 038963/0840 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 032679/0596 Recorded May 2, 2016
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: SERENA SOFTWARE, INC.
Reel/Frame 038589/0480 →
RELEASE OF SECURITY AGREEMENT Recorded Apr 17, 2014
From: BARCLAYS BANK PLC, AS COLLATERAL AGENT
To: SERENA SOFTWARE, INC.
Reel/Frame 032712/0493 →
SECURITY INTEREST Recorded Apr 15, 2014
From: SERENA SOFTWARE, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 032679/0596 →
SECURITY AGREEMENT Recorded Apr 4, 2011
From: SERENA SOFTWARE, INC., A DELAWARE CORPORATION
To: BARCLAYS BANK PLC. AS ADMINISTRATIVE AGENT
Reel/Frame 026073/0206 →
PATENT SECURITY AGREEMENT Recorded May 1, 2008
From: SERENA SOFTWARE, INC.
To: LEHMAN BROTHERS COMMERCIAL PAPER INC.
Reel/Frame 020887/0052 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2007
From: BROWN, GARY; DERAKHSHAN, MIR; BAIRD, KERSTIN
To: SERENA SOFTWARE, INC.
Reel/Frame 020160/0309 →