Software factory readiness review
First Claim
1. A computer-implemented method for delivering custom software, comprising:
- receiving a software project proposal including a custom software description describing a specific project type of the software project;
determining, by a computer processor, that the software project proposal is qualified for acceptance by a software factory, utilizing a scorecard for the specific project type, wherein the scorecard provides a maturity assessment of resources required and identifies any potential choke-points for the specific project type; and
in response to a determination that the software project proposal is qualified for acceptance by the software factory, the software factory undertaking the software project proposal by;
obtaining a plurality of work packets for the software project, wherein each of the plurality of work packets is associated with a functional area of the custom software and comprises software code and operating instructions,assembling, by the computer processor, the plurality of work packets to obtain deliverable software, anddelivering the deliverable software to a customer,wherein the software project proposal is determined to be qualified for acceptance by the software factory in response to a determination that the resources required are available and a determination that no potential choke-points are found,wherein the software factory comprises;
a software factory governance section that evaluates the software 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 software 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, andan assembly line that receives and executes the work packets to create the deliverable software.
6 Assignments
0 Petitions
Accused Products
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: receiving a software project proposal including a custom software description describing a specific project type of the software project; determining, by a computer processor, that the software project proposal is qualified for acceptance by a software factory, utilizing a scorecard for the specific project type, wherein the scorecard provides a maturity assessment of resources required and identifies any potential choke-points for the specific project type; and in response to a determination that the software project proposal is qualified for acceptance by the software factory, the software factory undertaking the software project proposal.
-
Citations
17 Claims
-
1. A computer-implemented method for delivering custom software, comprising:
-
receiving a software project proposal including a custom software description describing a specific project type of the software project; determining, by a computer processor, that the software project proposal is qualified for acceptance by a software factory, utilizing a scorecard for the specific project type, wherein the scorecard provides a maturity assessment of resources required and identifies any potential choke-points for the specific project type; and in response to a determination that the software project proposal is qualified for acceptance by the software factory, the software factory undertaking the software project proposal by; obtaining a plurality of work packets for the software project, wherein each of the plurality of work packets is associated with a functional area of the custom software and comprises software code and operating instructions, assembling, by the computer processor, the plurality of work packets to obtain deliverable software, and delivering the deliverable software to a customer, wherein the software project proposal is determined to be qualified for acceptance by the software factory in response to a determination that the resources required are available and a determination that no potential choke-points are found, wherein the software factory comprises; a software factory governance section that evaluates the software 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 software 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. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A system, comprising:
-
a processor; a data bus coupled to the processor; a memory coupled to the data bus; and a tangible computer-readable medium embodying computer program code therein, comprising instructions executable by the processor and configured for delivering custom software by causing the processor to; receive a software project proposal including a custom software description describing a specific project type of the software project; determine that the software project proposal is qualified for acceptance by a software factory, utilizing a scorecard for the specific project type, wherein the scorecard provides a maturity assessment of resources required and identifies any potential choke-points for the specific project type; and in response to a determination that the software project proposal is qualified for acceptance by the software factory, undertake the software project proposal by; obtaining a plurality of work packets for the software project, wherein each of the plurality of work packets is associated with a functional area of the custom software and comprises software code and operating instructions, assembling the plurality of work packets to obtain deliverable software, and delivering the deliverable software to a customer, wherein the software project proposal is determined to be qualified for acceptance by the software factory in response to a determination that the resources required are available, and a determination that no potential choke-points are found, wherein the software factory comprises; a software factory governance section that evaluates the software 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 software 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. - View Dependent Claims (7, 8, 9, 10)
-
-
11. A tangible non-transitory computer-readable medium comprising computer readable code therein, comprising instructions executable by a processor and configured to:
-
receive a software project proposal including a custom software description describing a specific project type of the software project; determine that the software project proposal is qualified for acceptance by a software factory, utilizing a scorecard for the specific project type, wherein the scorecard provides a maturity assessment of resources required and identifies any potential choke-points for the specific project type; and in response to a determination that the software project proposal is qualified for acceptance by the software factory, the software factory undertaking the software project proposal by the instructions causing the processor to; obtain a plurality of work packets for the software project, wherein each of the plurality of work packets is associated with a functional area of the custom software and comprises software code and operating instructions, assemble, by the computer processor, the plurality of work packets to obtain deliverable software, and deliver the deliverable software to a customer, wherein the software project proposal is determined to be qualified for acceptance by the software factory in response to a determination that the resources required are available, and a determination that no potential choke-points are found, wherein the software factory comprises; a software factory governance section that evaluates the software 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 software 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. - View Dependent Claims (12, 13, 14, 15, 16, 17)
-
Specification