Managing information in an integrated development architecture framework

• US 6,662,357 B1
• Filed: 08/31/1999
• Issued: 12/09/2003
• 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): INGBERG, TODD D
• Application Number:
  US09/386,891
• Time in Patent Office: 1,561 Days
• Field of Search: 717/1, 717/10
• US Class Current: 717/120
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A system, method, and article of manufacture are provided for managing information in a development architecture framework. Common information that is used by a plurality of components of a system is allowed to be accessed in a single, shared repository. Unique information that is unique to the components of the system is stored in corresponding designated folders. Media content communicated in the system is managed based on metadata thereof.

Claims

1. A method for managing information in a development architecture framework comprising the steps of:

(a) providing configuration management tools for;

(i) providing a reference program code, (ii) receiving a plurality of sets of updated program code representing different versions of the program code, (iii) comparing the sets of the updated program code with the reference program code in order to identify information relating to changes, (iv) classifying the information relating to the changes, and (v) providing change control tools for performing management of different versions of the program code;

(b) providing development tools, including productivity tools, collaborative tools, and process integration tools for creating sharing and sequencing documents, wherein the configuration management tools are inseparable from the development tools;

(c) allowing common information that is used by a plurality of components of a system to be accessed in a single, shared repository;

(d) storing unique information that is unique to the components of the system in corresponding designated folders, and

(e) managing media content communicated in the system based on metadata.

2. A method as recited in claim 1, and further comprising the step of managing the repository to avoid redundancies and inconsistencies among the common information.

3. A method as recited in claim 1, wherein the folders include a first set of folders for unfinished work product and a second set of folders for finished work product.

4. A method as recited in claim 1, wherein the folders allow access to the unique information based on a user profile.

5. A method as recited in claim 1, wherein the metadata includes at least one of a media type, a media setting, usage details, a source, and legal information relating t the media content.

6. A method as recited in claim 1, wherein the media content of the system is further managed based on a storage method and a version thereof.

7. A computer program embodied on a computer readable medium for managing information in a development architecture framework comprising:

(a) a code segment that provides configuration management tools that;

(i) provide a reference program code, (ii) receive a plurality of sets of updated program code representing different versions of the program code, (iii) compare the sets of the updated program code with the reference program code in order to identify information relating to changes, (iv) classify the information relating to the changes, and (v) provide change control tools for performing management of different versions of the program code;

(b) a code segment that provides development tools, including productivity tools, collaborative tools, and process integration tools for creating sharing and sequencing documents, wherein the configuration management tools are inseparable from the development tools;

(c) a code segment that allows common information that is used by a plurality of components of a system to be accessed in a single, shared repository;

(d) a code segment that stores unique information that is unique to the components of the system in corresponding designated folders; and

(e) a code segment that manages media content communicated in the system based on metadata.

8. A computer program as recited in claim 7, and further comprising a code segment that manages the repository to avoid redundancies and inconsistencies among the common information.

9. A computer program as recited in claim 7, wherein the folders include a first set of folders for unfinished work product and a second set of folders for finished work product.

10. A computer program as recited in claim 7, wherein the folders allow access to the unique information based on a user profile.

11. A computer program as recited in claim 7, wherein the metadata includes at least one of a media type, a media setting, usage details, a source, and legal information relating to the media content.

12. A computer program as recited in claim 7, wherein the media content of the system is further managed based on a storage computer program and a version thereof.

13. A system for managing information in a development architecture framework comprising:

(a) logic that provides configuration management tools that;

(i) provide a reference program code, (ii) receive a plurality of sets of updated program code representing different versions of the program code, (iii) compare the sets of the updated program code with the reference program code in order to identify information relating to changes, (iv) classify the information relating to the changes, and (v) provide change control tools for performing management of different versions of the program code;

(b) logic that provides development tools, including productivity tools, collaborative tools, and process integration tools for creating sharing and sequencing documents, wherein the configuration management tools are inseparable from the development tools;

(c) logic that allows common information that is used by a plurality of components of a system to be accessed in a single, shared repository;

(d) logic that stores unique information that is unique to the components of the system in corresponding designated folders; and

(e) logic that manages media content communicated in the system based on metadata.

14. A system as recited in claim 13, and further comprising logic that manages the repository to avoid redundancies and inconsistencies among the common information.

15. A system as recited in claim 13, wherein the folders include a first set of folders for unfinished work product and a second set of folders for finished work product.

16. A system as recited in claim 13, wherein the folders allow access to the unique information based on a user profile.

17. A system as recited in claim 13, wherein the metadata includes at least one of a media type, a media setting, usage details, a source, and legal information relating to the media content.

18. A system as recited in claim 13, wherein the media content of the system is further managed based on a storage system and a version thereof.