System, method and article of manufacture for configuration management in a development architecture framework

• US 6,256,773 B1
• Filed: 08/31/1999
• Issued: 07/03/2001
• Est. Priority Date: 08/31/1999
• Status: Expired due to Term

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Bowman-Amuah, Michel K.
• Primary Examiner(s): Powell, Mark
• Assistant Examiner(s): Khatri, Anil
• Application Number:
  US09/387,656
• Time in Patent Office: 672 Days
• Field of Search: 717/1, 717/11, 707/200, 707/203
• US Class Current: 717/121
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A system, method, and article of manufacture are provided for affording consistency in a development architecture framework as components in the framework change. A reference program code is provided and a plurality of sets of updated program code are received which represent different versions of the program code. The sets of the updated program code are compared with the reference program code in order to identify information relating to changes and the information is classified in relation to the changes. Tools are also provided for managing the different versions of the program code.

Claims

1. A method for affording consistency in a development architecture framework as components in the framework change comprising the steps of:

(a) providing a reference program code;

(b) receiving a plurality of sets of updated program code representing different versions of the program code;

(c) comparing the sets of the updated program code with the reference program code in order to identify information relating to changes;

(d) classifying the information relating to the changes; and

(e) providing change control tools for performing management of the different versions of the program code,-wherein the management includes at least one of;

authorization, coordination, capturing ideas, identifying conflicting changes, identifying when a critical change is implemented, and evaluating the impact of implementing changes; and

(f) providing development tools including productivity tools, collaborative tools, and process integration tools for creating sharing and sequencing documents.

2. A method as recited in claim 1, wherein the information relating to the changes includes an identity of a user who made the change.

3. A method as recited in claim 1, wherein a time of the change is identified for tracking an order of the changes.

4. A method as recited in claim 1, wherein the information relating to the changes is classified by area affected, priority, estimated cost, and authorization.

5. A method as recited in claim 1, wherein the change control tools are adapted for performing the management of the different versions of the program code in order to facilitate packaging.

6. A method as recited in claim 1, wherein the change control tools are adapted for performing the management of the different versions of the program code as the program code is changed between various stages of development.

7. A method as recited in claim 1, wherein the change control tool classifies change requests into at least one of:

incidents, faults, and enhancements.

8. A method as recited in claim 7, wherein the change control tool updates the change request classifications.

9. A computer program embodied on a computer readable medium for affording consistency in a development architecture framework as components in the framework change comprising:

(a) a code segment that provides a reference program code;

(b) a code segment that receives a plurality of sets of updated program code representing different versions of the program code;

(c) a code segment that compares the sets of the updated program code with the reference program code in order to identify information relating to changes;

(d) a code segment that classifies the information relating to the changes; and

(e) a code segment that provides change control-tools for performing management-of the different versions of the program code, wherein the management includes at least one of;

a code segment that performs authorization, a code segment that performs coordination, a code segment that captures ideas, a code segment that identifies conflicting changes, a code segment that identifies when a critical change is implemented, and a code segment that evaluates the impact of implementing changes; and

(f) a code segment that provides development tools including productivity tools. collaborative tools, and process integration tools for creating sharing and sequencing documents.

10. A computer program as recited in claim 9, wherein the information relating to the changes includes an identity of a user who made the change.

11. A computer program as recited in claim 9, wherein a time of the change is identified for tracking an order of the changes.

12. A computer program as recited in claim 9, wherein the information relating to the changes is classified by area affected, priority, estimated cost, and authorization.

13. A computer program as recited in claim 9, wherein the change control tools are adapted for performing the management of the different versions of the program code in order to facilitate packaging.

14. A computer program as recited in claim 9, wherein the change control tools are adapted for performing the management of the different versions of the program code as the program code is changed between various stages of development.

15. A system for affording consistency in a development architecture framework as components in the framework change comprising:

(a) logic that provides a reference program code;

(b) logic that receives a plurality of sets of updated program code representing different versions of the program code;

(c) logic that compares the sets of the updated program code with the reference program code in order to identify information relating to changes;

(d) logic that classifies the information relating to the changes; and

(e) logic that provides change control tools for performing management of the different versions of the program code wherein the management includes at least one of;

logic that performs authorization, logic that performs coordination, logic that captures ideas, logic that identifies conflicting changes, logic that identifies when a critical change is implemented, and logic that evaluates the impact of implementing changes; and

(f) logic that provides development tools including productivity tools, collaborative tools, and process integration tools for creating sharing and sequencing documents.

16. A system as recited in claim 15, wherein the information relating to the changes includes an identity of a user who made the change.

17. A system as recited in claim 15, wherein a time of the change is identified for tracking an order of the changes.

18. A system as recited in claim 15, wherein the information relating to the changes is classified by area affected, priority, estimated cost, and authorization.

19. A system as recited in claim 15, wherein the change control tools are adapted for performing the management of the different versions of the program code in order to facilitate packaging.

20. A system as recited in claim 15, wherein the change control tools are adapted for performing the management of the different versions of the program code as the program code is changed between various stages of development.