Monitoring and maintaining balance of factory quality attributes within a software factory environment
First Claim
1. A computer-implemented method for monitoring and maintaining a balance of factory quality attributes when developing a deliverable software in a software factory, the computer-implemented method comprising:
- receiving, from a client computer associated with a client, a request for a deliverable software based on a project proposal, wherein the deliverable software is to enable execution of a project associated with the project proposal;
a balance evaluation engine in the software factory establishing a business baseline for the project proposal, the business baseline having a plurality of requirements associated with one or more business drivers of the project proposal, 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 work packets, which include pre-stored, reusable, self-contained, discrete units of software code; and
an assembly line that receives and executes the work packets to create the deliverable software;
optimizing the deliverable software based on the business baseline, wherein the optimizing the deliverable software further comprises;
evaluating, by the balance evaluation engine, one or more architectural qualities of the project proposal to determine a purpose and one or more content requirements of the project proposal;
determining how the purpose and the one or more content requirements are relevant to the one or more business drivers for implementing the deliverable software in order to select a plurality of hardware and software needed in the deliverable software to make the project work; and
in response to selecting the plurality of hardware and software, assembling one or more artifacts into the deliverable software;
wherein at least one of the one or more business drivers identified by the client is a goal to improve a return on equity, and the optimizing the deliverable software further comprises;
optimizing processing of one or more incoming transactions;
performing a root cause analysis to determine a context for the return on equity business driver;
evaluating a time taken to build the deliverable software;
evaluating an relevance of the deliverable software to meet the business baseline for the project proposal;
evaluating an efficiency of the software factory to build the deliverable software for optimization of return on equity; and
determining whether the software factory took too long to build the deliverable software for optimization of return on equity;
recursively performing the functions of (a) establishing a business baseline and (b) optimizing the deliverable software to modify the project proposal until an optimized design is created for the deliverable software that meets the plurality of requirements of the business baseline; and
delivering the deliverable software to the client computer.
2 Assignments
0 Petitions
Accused Products
Abstract
A System to Maintain Balance of Factory Quality Attributes with Software Factory Operating Environment provides the means to determine if a deliverable will meet the needs of a client'"'"'s project. The process includes the identification and measurement of different parameters of a software factory, including specified architectural features, and compares these parameters with the factory'"'"'s strategic artifacts and client'"'"'s critical project needs to qualify attributes within the software factory environment. This process provides a means to monitor and maintain an optimal balance of desirable quality attributes. Thus, quality attributes are analyzed before design time and before delivery of a software product, such that an analysis can be performed before any considerable amount of time and efforts have been spent on a project.
128 Citations
17 Claims
-
1. A computer-implemented method for monitoring and maintaining a balance of factory quality attributes when developing a deliverable software in a software factory, the computer-implemented method comprising:
-
receiving, from a client computer associated with a client, a request for a deliverable software based on a project proposal, wherein the deliverable software is to enable execution of a project associated with the project proposal; a balance evaluation engine in the software factory establishing a business baseline for the project proposal, the business baseline having a plurality of requirements associated with one or more business drivers of the project proposal, 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 work packets, which include pre-stored, reusable, self-contained, discrete units of software code; and
an assembly line that receives and executes the work packets to create the deliverable software;optimizing the deliverable software based on the business baseline, wherein the optimizing the deliverable software further comprises; evaluating, by the balance evaluation engine, one or more architectural qualities of the project proposal to determine a purpose and one or more content requirements of the project proposal; determining how the purpose and the one or more content requirements are relevant to the one or more business drivers for implementing the deliverable software in order to select a plurality of hardware and software needed in the deliverable software to make the project work; and
in response to selecting the plurality of hardware and software, assembling one or more artifacts into the deliverable software;wherein at least one of the one or more business drivers identified by the client is a goal to improve a return on equity, and the optimizing the deliverable software further comprises; optimizing processing of one or more incoming transactions; performing a root cause analysis to determine a context for the return on equity business driver; evaluating a time taken to build the deliverable software; evaluating an relevance of the deliverable software to meet the business baseline for the project proposal; evaluating an efficiency of the software factory to build the deliverable software for optimization of return on equity; and determining whether the software factory took too long to build the deliverable software for optimization of return on equity; recursively performing the functions of (a) establishing a business baseline and (b) optimizing the deliverable software to modify the project proposal until an optimized design is created for the deliverable software that meets the plurality of requirements of the business baseline; and delivering the deliverable software to the client computer. - View Dependent Claims (2, 3, 4, 13, 14, 15)
-
-
5. A system comprising:
-
a processor; a data bus coupled to the processor; a memory coupled to the data bus; and a computer-usable storage device embodying computer program code, the computer program code comprising instructions executable by the processor and configured to; receive, from a client computer associated with a client, a request for a deliverable software based on a project proposal, wherein the deliverable software is to enable execution of a project associated with the project proposal; establish, by a balance evaluation engine in a software factory, a business baseline for the project proposal, the business baseline having a plurality of requirements associated with one or more business drivers of the project proposal; optimize the deliverable software based on the business baseline, wherein the optimize the deliverable software further comprises additional processes that; evaluate, by the balance evaluation engine, one or more architectural qualities of the project proposal to determine a purpose and one or more content requirements of the project proposal, 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 work packets, which include pre-stored, reusable, self-contained, discrete units of software code; and
an assembly line that receives and executes the work packets to create the deliverable software;determine how the purpose and the one or more content requirements are relevant to the one or more business drivers for implementing the deliverable software in order to select a plurality of hardware and software needed in the deliverable software to make the project work; and
in response to selecting the plurality of hardware and software, assemble one or more artifacts into the deliverable software;wherein at least one of the one or more business drivers identified by the client is a goal to improve a return on equity, and the optimizing the deliverable software further comprises; optimizing processing of one or more incoming transactions; performing a root cause analysis to determine a context for the return on equity business driver; evaluating a time taken to build the deliverable software; evaluating an relevance of the deliverable software to meet the business baseline for the project proposal; evaluating an efficiency of the software factory to build the deliverable software for optimization of return on equity; and determining whether the software factory took too long to build the deliverable software for optimization of return on equity; recursively perform the functions of (a) establish a business baseline and (b) optimize the deliverable software to modify the project proposal until an optimized design is created for the deliverable software that meets the plurality of requirements of the business baseline; and deliver the deliverable software to the client computer. - View Dependent Claims (6, 7, 8, 16)
-
-
9. A computer-readable storage device encoded with a computer program, the computer program comprising computer executable instructions configured for:
-
receiving, from a client computer associated with a client, a request for a deliverable software based on a project proposal, wherein the deliverable software is to enable execution of a project associated with the project proposal; a balance evaluation engine in the software factory establishing a business baseline for the project proposal, the business baseline having a plurality of requirements associated with one or more business drivers of the project proposal, 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 work packets, which include pre-stored, reusable, self-contained, discrete units of software code; and
an assembly line that receives and executes the work packets to create the deliverable software;evaluating one or more business drivers identified by the client for the project, wherein the one or more quality objectives describe quality objectives for implementing the deliverable software and executing the project; evaluating activities needed to satisfy a goal of the project, wherein the business baseline is based on a balance of planned performance, efficiency and dependability of the deliverable software; and determining a relevance of the project proposal to the one or more business drivers; optimizing the deliverable software based on the business baseline, wherein the optimizing the deliverable software further comprises; evaluating, by the balance evaluation engine, one or more architectural qualities of the project proposal to determine a purpose and one or more content requirements of the project proposal; determining how the purpose and the one or more content requirements are relevant to the one or more business drivers for implementing the deliverable software in order to select a plurality of hardware and software needed in the deliverable software to make the project work; and in response to selecting the plurality of hardware and software, assembling one or more artifacts into the deliverable software; wherein at least one of the one or more business drivers identified by the client is a goal to improve a return on equity, and the optimizing the deliverable software further comprises; optimizing processing of one or more incoming transactions; performing a root cause analysis to determine a context for the return on equity business driver; evaluating a time taken to build the deliverable software; evaluating an relevance of the deliverable software to meet the business baseline for the project proposal; evaluating an efficiency of the software factory to build the deliverable software for optimization of return on equity; and determining whether the software factory took too long to build the deliverable software for optimization of return on equity; recursively performing the functions of (a) establishing a business baseline and (b) optimizing the deliverable software to modify the project proposal until an optimized design is created for the deliverable software that meets the plurality of requirements of the business baseline; and delivering the deliverable software to the client computer. - View Dependent Claims (10, 11, 12, 17)
-
Specification