Software factory

• US 8,359,566 B2
• Filed: 04/13/2007
• Issued: 01/22/2013
• Est. Priority Date: 04/13/2007
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Chaar, Jarir K., Finlayson, Ronald D., Giraldo, Juan P., Lang, Steven R., Mitsumori, Naomi M., Rajagopal, Hari, Reddington, Francis X., Vines, Terri A.
• Primary Examiner(s): Kang, Insun
• Application Number:
  US11/735,275
• Publication Number:
  US 20080256516A1
• Time in Patent Office: 2,111 Days
• Field of Search: None
• US Class Current: 717/101
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A method, system and computer-readable medium for creating software in a standardized manner are presented. The method includes the steps of: receiving, at a software factory, a description of software needs from a customer; creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs; inducting the project proposal into the software factory, where inducting the project proposal initially evaluates the project proposal'"'"'s compatibility with a capacity of the software factory; parsing the project proposal into major functional areas; retrieving work packets that are appropriate for the project proposal, where the work packets are pre-stored, reusable, self-contained, discrete units of software code; assembling the work packets into a deliverable software; testing the deliverable software; and delivering the deliverable software to the customer.

Claims

1. A computer-implemented method for creating software in a standardized manner, the computer-implemented method comprising:

receiving, at a software factory, a description of software needs from a customer;

creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs;

inducting the project proposal into the software factory, wherein inducting the project proposal initially evaluates the project proposal'"'"'s compatibility with a capacity of the software factory;

parsing the project proposal into major functional areas;

retrieving work packets that are appropriate for the project proposal, wherein the work packets include pre-stored, reusable, self-contained, discrete units of software code, governance, and operational instructions, wherein each of the work packets is associated with a functional area of the custom software and comprises software code and operating instructions;

assembling the work packets by;

calling a work packet specific template,

calling artifacts needed by the work packet specific template,

calling metrics needed by the work packet specific template, and

assembling the work packets using the called work packet specific template, artifacts, and metrics;

processing the work packets to obtain a deliverable software;

testing the deliverable software; and

delivering the deliverable software to the customer.

2. The computer-implemented method of claim 1, wherein the method is performed in the software factory, and wherein the software factory comprises:

a software factory governance section that evaluates the project proposal for acceptance by the software factory;

a design center composed of a requirements analysis team and an architecture team, wherein the design center sections the project proposal into major functional areas that are to be handled by the requirements analysis team and the architecture team, and wherein the design center creates the work packets; and

an assembly line that receives and executes the work packets to create the deliverable software.

3. The computer-implemented method of claim 2, wherein the assembly line further comprises:

a published set of services and a published set of requirements for the assembly line, wherein the published set of services and the published set of requirements for the assembly line are published to the design center, and wherein the published set of services describes what assembly services for assembling work packets are offered by the assembly line, and wherein the published set of requirements describes what execution environment must be used by work packets that are provided by the design center for assembly in the assembly line.

4. The computer-implemented method of claim 3, wherein the work packets include governance procedures, standards, reused assets, work packet instructions, integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines.

5. The computer-implemented method of claim 2, wherein the assembly line includes software that automatically recognizes a project type for the project proposal, and wherein the assembly line assembles the work packets into the deliverable software in accordance with the project type that is recognized by the assembly line.

6. The computer-implemented method of claim 2, wherein the assembly line conducts an integration test, a system test, a system integration test and a performance test of the deliverable software, wherein the integration test tests the deliverable software for compatibility with the client'"'"'s system, the system test checks the client'"'"'s system to ensure that the client'"'"'s system is operating properly, the system integration test tests for bugs that may arise when the deliverable software is integrated into the client'"'"'s system, and the performance test tests the deliverable software for defects as it is executing in the client'"'"'s system.

7. A system comprising:

a processor;

a data bus coupled to the processor;

a memory coupled to the data bus; and

a computer-usable medium embodying computer program code, the computer program code comprising instructions executable by the processor and configured for creating software in a standardized manner by performing the steps of;

receiving, at a software factory, a description of software needs from a customer;

creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs;

inducting the project proposal into the software factory, wherein inducting the project proposal initially evaluates the project proposal'"'"'s compatibility with a capacity of the software factory;

parsing the project proposal into major functional areas;

retrieving work packets that are appropriate for the project proposal, wherein the work packets include pre-stored, reusable, self-contained, discrete units of software code, governance, and operational instructions, wherein each of the work packets is associated with a functional area of the custom software and comprises software code and operating instructions;

assembling the work packets by;

calling a work packet specific template,

calling artifacts needed by the work packet specific template,

calling metrics needed by the work packet specific template, and

assembling the work packets using the called work packet specific template, artifacts, and metrics;

processing the work packets to obtain a deliverable software;

testing the deliverable software; and

delivering the deliverable software to the customer.

8. The system of claim 7, wherein the instructions further comprise executable instructions for supporting the software factory that comprises:

a software factory governance section that evaluates the project proposal for acceptance by the software factory;

a design center composed of a requirements analysis team and an architecture team, wherein the design center sections the project proposal into major functional areas that are to be handled by the requirements analysis team and the architecture team, and wherein the design center creates the work packets; and

an assembly line that receives and executes the work packets to create the deliverable software.

9. The system of claim 8, wherein the design center further comprises:

a requirements analysis team, wherein the requirements analysis team is responsible for determining system requirements for executing the deliverable software on the customer'"'"'s system; and

an architectural team, wherein the architectural team models the project proposal in accordance with customer constraints, and wherein the architectural team bundles the customer constraints together with the work packets for execution in the assembly line.

10. The system of claim 9, wherein the work packets include governance procedures, standards, reused assets, work packet instructions, integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines.

11. The system of claim 8, wherein the assembly line includes software that automatically recognizes a project type for the project proposal, and wherein the assembly line assembles the work packets into the deliverable software in accordance with the project type that is recognized by the assembly line.

12. The system of claim 8, wherein the assembly line conducts an integration test, a system test, a system integration test and a performance test of the deliverable software, wherein the integration test tests the deliverable software for compatibility with the client'"'"'s system, the system test checks the client'"'"'s system to ensure that the client'"'"'s system is operating properly, the system integration test tests for bugs that may arise when the deliverable software is integrated into the client'"'"'s system, and the performance test tests the deliverable software for defects as it is executing in the client'"'"'s system.

13. A tangible computer-readable storage device encoded with a computer program, the computer program comprising computer executable instructions configured for:

receiving, at a software factory, a description of software needs from a customer;

creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs;

inducting the project proposal into the software factory, wherein inducting the project proposal initially evaluates the project proposal'"'"'s compatibility with a capacity of the software factory;

parsing the project proposal into major functional areas;

retrieving work packets that are appropriate for the project proposal, wherein the work packets include pre-stored, reusable, self-contained, discrete units of software code, governance, and operational instructions, wherein each of the work packets is associated with a functional area of the custom software and comprises software code and operating instructions;

assembling the work packets by;

calling a work packet specific template,

calling artifacts needed by the work packet specific template,

calling metrics needed by the work packet specific template, and

assembling the work packets using the called work packet specific template, artifacts, and metrics;

processing the work packets to obtain a deliverable software;

testing the deliverable software; and

delivering the deliverable software to the customer.

14. The tangible computer-readable storage device of claim 13, wherein the computer executable instructions further comprise executable instructions for supporting the software factory that comprises:

a software factory governance section that evaluates the project proposal for acceptance by the software factory;

a design center composed of a requirements analysis team and an architecture team, wherein the design center sections the project proposal into major functional areas that are to be handled by the requirements analysis team and the architecture team, and wherein the design center creates the work packets; and

an assembly line that receives and executes the work packets to create the deliverable software.

15. The tangible computer-readable storage device of claim 14, wherein the design center further comprises:

a requirements analysis team, wherein the requirements analysis team is responsible for determining system requirements for executing the deliverable software on the customer'"'"'s system; and

an architectural team, wherein the architectural team models the project proposal in accordance with customer constraints, and wherein the architectural team bundles the customer constraints together with the work packets for execution in the assembly line.

16. The tangible computer-readable storage device of claim 15, wherein the work packets include governance procedures, standards, reused assets, work packet instructions, integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines.

17. The tangible computer-readable storage device of claim 14, wherein the assembly line includes software that automatically recognizes a project type for the project proposal, and wherein the assembly line assembles the work packets into the deliverable software in accordance with the project type that is recognized by the assembly line.

18. The tangible computer-readable storage device of claim 14, wherein the assembly line conducts an integration test, a system test, a system integration test and a performance test of the deliverable software, wherein the integration test tests the deliverable software for compatibility with the client'"'"'s system, the system test checks the client'"'"'s system to ensure that the client'"'"'s system is operating properly, the system integration test tests for bugs that may arise when the deliverable software is integrated into the client'"'"'s system, and the performance test tests the deliverable software for defects as it is executing in the client'"'"'s system.

19. The tangible computer-readable storage device of claim 13, wherein the computer-usable medium is a component of a remote server, and wherein the computer executable instructions are deployable to a supervisory computer from the remote server.

20. The tangible computer-readable storage device of claim 13, wherein the computer executable instructions are capable of being provided by a service provider to a customer on an on-demand basis.