Software Factory Readiness Review

• US 20080255693A1
• Filed: 04/13/2007
• Published: 10/16/2008
• Est. Priority Date: 04/13/2007
• Status: Active Grant

• Current Assignee: GlobalFoundries, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Reddington, Francis X., Finlayson, Ronald D., Chaar, Jarir K., Mitsumori, Naomi M., Jobson, Thomas A.
• Granted Patent: US 8,296,719 B2
• Time in Patent Office: Days
• US Class Current: 700/97
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A computer-implemented method, system, and computer-readable medium for determining if a software factory is ready to take on a software project is presented. In a preferred embodiment, the computer-implemented method includes the steps of: determining if an infrastructure for a software factory has been procured; determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed; determining if a workflow event model for an assembly line in the software factory has been configured; determining if workload in the assembly line has been balanced; determining if communication channels between the software factory and a customer'"'"'s computer system have been defined and cleared for data transmission; and in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory.

Claims

1. A computer-implemented method for determining if a software factory is ready to take on a software project, the computer-implemented method comprising:

determining if an infrastructure for a software factory has been procured;

determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed;

determining if a workflow event model for an assembly line in the software factory has been configured;

determining if workload in the assembly line has been balanced;

determining if communication channels between the software factory and a customer'"'"'s computer system have been defined and cleared for data transmission; and

in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory.

2. The computer-implemented method of claim 1, 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 determining if a software factory is ready to take on a software project by performing the steps of;

determining if an infrastructure for a software factory has been procured;

determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed;

determining if a workflow event model for an assembly line in the software factory has been configured;

determining if workload in the assembly line has been balanced;

determining if communication channels between the software factory and a customer'"'"'s computer system have been defined and cleared for data transmission; and

in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory.

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 maj or 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 computer-readable medium encoded with a computer program, the computer program comprising computer executable instructions configured for:

determining if an infrastructure for a software factory has been procured;

determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed;

determining if a workflow event model for an assembly line in the software factory has been configured;

determining if workload in the assembly line has been balanced;

determining if communication channels between the software factory and a customer'"'"'s computer system have been defined and cleared for data transmission; and

in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory.

14. The computer-readable medium 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 computer-readable medium 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 computer-readable medium 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 computer-readable medium 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 computer-readable medium 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 computer-readable medium 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 computer-readable medium 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.