Building techniques in a development architecture framework

• US 6,405,364 B1
• Filed: 08/31/1999
• Issued: 06/11/2002
• 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): Dam, Tuan Q.
• Assistant Examiner(s): INGBERG, TODD D
• Application Number:
  US09/386,619
• Time in Patent Office: 1,015 Days
• Field of Search: 717/1, 717/11, 717/101, 717/102, 717/103, 717/106, 717/107, 717/108, 717/120, 717/124
• US Class Current: 717/101
• 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

Abstract

A system is provided for building systems in a development architecture framework. The present invention is directed to both a system to be built and an implementation strategy to fulfill system requirements. Software components of the system are encapsulated with wrappers. The wrappers are adapted to be changed upon other software components of the system being changed while the encapsulated software components of the system remain unchanged. In one embodiment of the present invention, specifying the requirements of the system to be built and the implementation strategy to fulfill the requirements may be carried out using tools such as data modeling tools, process modeling tools, event modeling tools, performance modeling tools, object modeling tools, component modeling tools, reuse support tools, prototyping tools, application logic design tools, database design tools, presentation design tools, communication design, and usability test tools. In another embodiment of the present invention, improving the performance and maintenance of the system may be carried out using tools such as interactive navigation tools, graphical representation tools, extraction tools, repository tools, restructuring tools, and data name rationalization tools.

Claims

1. A method for building systems in a development architecture framework comprising the steps of:

(a) specifying requirements of a system to be built and an implementation strategy to fulfill the requirements;

(b) building the system according to the implementation strategy;

(c) improving performance and maintenance of the system by using information relating to a previous system, and using tools selected from the group of tools consisting of interactive navigation tools, graphical representation tools, extraction tools, repository tools, restructuring tools, and data name rationalization tools;

(d) encapsulating software components of the system with wrappers, the wrappers adapted to be changed upon other software components of the system being changed, wherein the encapsulated software components of the system remain unchanged;

(e) testing the system to ensure that the requirements are fulfilled;

(f) defining quality assurance standards, quality assurance tools and quality assurance procedures;

(g) implementing quality assurance standards, quality assurance tools and quality assurance procedures;

(h) managing service to a developer of the system based on at least one of service level agreements with the developer and operations level agreements with the developer;

(i) performing a plurality of system management operations on the system selected from the group of system management operations consisting of start-up and shut-down operations, back-up and restore operations, archiving operations, security operations, and performance monitoring operations; and

(j) planning service to the developer in order to anticipate and implement changes in the system.

2. A method as recited in claim 1, wherein the step of specifying the requirements of the system to be built and the implementation strategy to fulfill the requirements is carried out using tools selected from the group of tools consisting of data modeling tools, process modeling tools, event modeling tools, perfonnance modeling tools, object modeling tools, component modeling tools, reuse support tools, prototyping tools, application logic design tools, database design tools, presentation design tools, communication design, and usability test tools.

3. A method as recited in claim 1, wherein the system is built using tools selected from the group of tools including source code editor tools, compiler/linker/interpreter tools, source code debugger tools, generation tools, quality assurance utility tools, code/object library tools, and media content creation tools.

4. A method as recited in claim 1, wherein the system is tested using tools selected from the group of tools consisting of test data management tools, test data manipulation tools, test planning tools, test execution tools, performance management tools, emulation tools, test result comparison tools, and test coverage measurement tools.

5. A computer program embodied on a computer readable medium for building systems in a development architecture framework comprising:

(a) a code segment that specifies requirements of a system to be built and an implementation strategy to fulfill the requirements;

(b) a code segment that builds the system according to the implementation strategy;

(c) a code segment that improves performance and maintenance of the system by using information relating to a previous system, and using tools selected from the group of tools consisting of interactive navigation tools, graphical representation tools, extraction tools, repository tools, restructuring tools, and data name rationalization tools;

(d) a code segment that encapsulates software components of the system with wrappers, the wrappers adapted to be changed upon other software components of the system being changed, wherein the encapsulated software components of the system remain unchanged;

(e) a code segment that tests the system to ensure that the requirements are fulfilled;

(f) a code segment that defines quality assurance standards, quality assurance tools and quality assurance procedures;

(g) a code segment that implements quality assurance standards, quality assurance tools and quality assurance procedures

(h) a code segment that manages service to the system based on at least one of service level agreements with the developer and operations level agreements with the developer

(i) a code segment that performs a plurality of system management operations on the system selected from the group of system management operations consisting of start-up and shut-down operations, back-up and restore operations, archiving operations, security operations, and performance monitoring operations; and

(j) a code segment that plans service to a developer in order to anticipate and implement changes in the system.

6. A computer program as recited in claim 5, wherein the code segment that specifies the requirements of the system to be built and the implementation strategy to fulfill the requirements is carried out using tools selected from the group of tools consisting of data modeling tools, process modeling tools, event modeling tools, performance modeling tools, object modeling tools, component modeling tools, reuse support tools, prototyping tools, application logic design tools, database design tools, presentation design tools, communication design, and usability test tools.

7. A computer program as recited in claim 5, wherein the system is built using tools selected from the group of tools including source code editor tools, compiler/linker/interpreter tools, source code debugger tools, generation tools, quality assurance utility tools, code/object library tools, and media content creation tools.

8. A computer progrm as recited in claim 5, wherein the system is tested using tools selected from the group of the tools consisting of test data management tools, test data manipulation tools, test planning tools, test execution tools, performance management tools, emulation tools, test result comparasion tools, and test coverage measurement tools.

9. A system for building systems in a development architecture framework comprising:

(a) logic that specifies requirements of a system to be built and an implementation strategy to fulfill the requirements;

(b) logic that builds the system according to the implementation strategy;

(c) logic that improves performance and maintenance of the system by using information relating to a previous system, and using tools selected from the group of tools consisting of interactive navigation tools, graphical representation tools, extraction tools, repository tools, restructuring tools, and data name rationalization tools;

(d) logic that encapsulates software components of the system with wrappers, the wrappers adapted to be changed upon other software components of the system being changed, wherein the encapsulated software components of the system remain unchanged;

(e) logic that tests that system to ensure that the requirements are fulfilled;

(f) logic that defines quality assurance standards, quality assurance tools and quality assurance procedures;

(g) logic that implements quality assurance standards, quality assurance tools and quality assurance procedures;

(h) logic that manages service to a developer of the system based on at least one of service level agreements with the developer and operations level agreements with the developer;

(i) logic that performs a plurality of system management operations on the system selected from the group of system management operations consisting of start-up and shut-down operations, back-up and restore operations, archiving operations, security operations, and performance monitoring operations; and

(j) logic that plans service to the developer in order to anticipate and implement changes in the system.

10. A system as recited in claim 9, wherein the logic that specifies the requirements of the system to be built and the implementation strategy to fulfill the requirements is carried out using tools selected from the group of tools consisting of data modeling tools, process modeling tools, event modeling tools, performance modeling tools, object modeling tools, component modeling tools, reuse support tools, prototyping tools, application logic design tools, database design tools, presentation design tools, communication design, and usability test tools.

11. A system as recited in claim 9, wherein the system is built using tools selected from the group of tools including source code editor tools, compiler/linker/interpreter tools, source code debugger tools, generation tools, quality assurance utility tools, code/object library tools, and media content creation tools.

12. A system as recited in claim 9, wherein the system is tested using tools selected from the group of tools consisting of test data management tools, test data manipulation tools, test planning tools, test execution tools, performance management tools, emulation tools, test result comparison tools, and test coverage measurement tools.