Model-driven assignment of work to a software factory
First Claim
Patent Images
1. A computer implemented method of assigning work to a software factory for executing a project, the computer implemented method comprising:
- generating via a processor a project model from a process, wherein the project model is of a current project state that describes executable deliverables and states of the executable deliverables of a current project, wherein the project model is comprised of a set of model elements, wherein each model element is characterized by an element type, wherein each element type defines a set of element states, wherein each element state from the set of element states describes lifecycle states for a particular model element of the project model, and wherein each element state from the set of elements states describes a set of relationships that exist between the particular model element and other model elements in the project model;
mapping via the processor project model subcomponents of the project model to work packets that are available in a software factory, wherein each of said work packets comprises a header, wherein the header comprises a unique identification number, a description of said each of said work packets, a type description of said each of said work packets, an identifier of a parent object from which said each of said work packets has inheritance, and a checklist for returning said each of said work packets to the software factory after a customized deliverable unit of software has been delivered by the software factory;
determining via the processor which available work packets in the software factory are necessary work packets for executing the current project, wherein the determining is based on which work assignments are necessary for executing the current project;
generating via the processor an initial work plan for executing the project via an execution of the available work packets; and
in response to detecting changes to the project model, the processor displaying impacted work packets, wherein the changes to the project model comprise a new feature being added, an old feature being removed, and a new constraint being removed from the project model, and wherein the impacted work packets comprise work packets that are newly called, newly divorced, and newly modified for use by the software factory.
7 Assignments
0 Petitions
Accused Products
Abstract
A computer implemented method, system, and/or computer program product assigns work to a software factory for implementing a project. A project model of a project is generated. Project model subcomponents are mapped to work packets that are available to a software factory, thus leading to the generation of a work plan for performing the project via an execution of the available work packets.
205 Citations
17 Claims
-
1. A computer implemented method of assigning work to a software factory for executing a project, the computer implemented method comprising:
-
generating via a processor a project model from a process, wherein the project model is of a current project state that describes executable deliverables and states of the executable deliverables of a current project, wherein the project model is comprised of a set of model elements, wherein each model element is characterized by an element type, wherein each element type defines a set of element states, wherein each element state from the set of element states describes lifecycle states for a particular model element of the project model, and wherein each element state from the set of elements states describes a set of relationships that exist between the particular model element and other model elements in the project model; mapping via the processor project model subcomponents of the project model to work packets that are available in a software factory, wherein each of said work packets comprises a header, wherein the header comprises a unique identification number, a description of said each of said work packets, a type description of said each of said work packets, an identifier of a parent object from which said each of said work packets has inheritance, and a checklist for returning said each of said work packets to the software factory after a customized deliverable unit of software has been delivered by the software factory; determining via the processor which available work packets in the software factory are necessary work packets for executing the current project, wherein the determining is based on which work assignments are necessary for executing the current project; generating via the processor an initial work plan for executing the project via an execution of the available work packets; and in response to detecting changes to the project model, the processor displaying impacted work packets, wherein the changes to the project model comprise a new feature being added, an old feature being removed, and a new constraint being removed from the project model, and wherein the impacted work packets comprise work packets that are newly called, newly divorced, and newly modified for use by the software factory. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer program product for assigning work to a software factory for executing a project, the computer program product comprising:
- a non-transitory computer readable storage media;
first program instructions to generate a project model from a process, wherein the project model is of a current project state that describes executable deliverables and states of the executable deliverables of a current project;second program instructions to map project model subcomponents of the project model to work packets that are available in a software factory, wherein each of said work packets comprises a header, wherein the header comprises a unique identification number, a description of said each of said work packets, a type description of said each of said work packets, an identifier of a parent object from which said each of said work packets has inheritance, and a checklist for returning said each of said work packets to the software factory after a customized deliverable unit of software has been delivered by the software factory; third program instructions to determine which available work packets in the software factory are necessary work packets for executing the current project, wherein the determining is based on which work assignments are necessary for executing the current project; fourth program instructions to generate an initial work plan for executing the project via an execution of the available work packets; and fifth program instructions to, in response to detecting changes to the project model, display impacted work packets, wherein the changes to the project model comprise a new feature being added to the project model, an old feature being removed from the project model, and a new constraint being removed from the project model, and wherein the impacted work packets comprise work packets that are newly called, newly divorced, and newly modified for use by the software factory; and
whereinthe first, second, third, fourth, and fifth program instructions are stored on the non-transitory computer readable storage media and executed by the processor via the computer readable memory. - View Dependent Claims (11, 12, 13)
- a non-transitory computer readable storage media;
-
14. A computer system comprising:
-
a processor, a computer readable memory, and a computer readable storage media;
first program instructions to generate a project model from a process, wherein the project model is of a current project state that describes executable deliverables and states of the executable deliverables of a current project;second program instructions to map project model subcomponents of the project model to work packets that are available in a software factory, wherein each of said work packets comprises a header, wherein the header comprises a unique identification number, a description of said each of said work packets, a type description of said each of said work packets, an identifier of a parent object from which said each of said work packets has inheritance, and a checklist for returning said each of said work packets to the software factory after a customized deliverable unit of software has been delivered by the software factory; third program instructions to determine which available work packets in the software factory are necessary work packets for executing the current project, wherein the determining is based on which work assignments are necessary for executing the current project; fourth program instructions to generate an initial work plan for executing the project via an execution of the available work packets; and fifth program instructions to, in response to detecting changes to the project model, display impacted work packets, wherein the changes to the project model comprise a new feature being added to the project model, an old feature being removed from the project model, and a new constraint being removed from the project model, and wherein the impacted work packets comprise work packets that are newly called, newly divorced, and newly modified for use by the software factory; and
whereinthe first, second, third, fourth, and fifth program instructions are stored on the non-transitory computer readable storage media and executed by the processor via the computer readable memory. - View Dependent Claims (15, 16, 17)
-
Specification