Computer method and system for integrating software development and deployment

• US 20070006122A1
• Filed: 12/28/2005
• Published: 01/04/2007
• Est. Priority Date: 05/31/2005
• Status: Active Grant

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Thomas, Malcolm, Hunt, Stephen, Bailey, Don, Kanakasabesan, Kartik, Seifert, Stephen
• Granted Patent: US 7,761,851 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/61 Installation

Abstract

A computer implemented method and system for software auditability and bidirectional traceability in a software development lifecycle is provided. The lifecycle having at least development and deployment phases is bridged with a configurable workflow engine, a configuration management engine, and a managed deployment engine, interconnected with one or more representations of work to be performed or of work performed. Additionally, auditability and bidirectional traceability is provided by linking a development asset in the development phase to a deployment asset in the deployment phase so that: the development asset can be determined from the deployment asset; a deploying entity deploying the deployment asset can be determined from the development asset; a development request for developing the development asset can be determined from the deployment asset deployed; and a deployment environment where the deployment asset is being deployed can be determined from the development asset.

Claims

1. A computer implemented method for providing a software development lifecycle with auditability and bidirectional traceability, the software development lifecycle having at least a development phase and a deployment phase, the method comprising:

bridging the development phase of the software development lifecycle and the deployment phase of the software development lifecycle with a configurable workflow engine, a configuration management engine, and a managed deployment engine; and

interconnecting the configurable workflow engine, the configuration management engine, and the managed deployment engine with one or more representations of work to be performed or of work performed, wherein the one or more representations of work to be performed or of work performed provide the software development lifecycle with auditability and bidirectional traceability.

2. The method of claim 1, wherein the configuration management engine further provides:

responding to a request for change from the configurable workflow engine;

providing one or more lists of versioned development assets needed to work on the request for change to the configurable workflow engine;

providing a configuration record representing the one or more lists of versioned development assets to the managed deployment engine; and

wherein the one or more representations of work to be performed or of work performed includes the request for change, and the one or more lists of versioned development assets.

3. The method of claim 1, wherein the configurable workflow management engine further provides:

responding to a request for change;

initiating one or more workflows in response to the request for change, each workflow having a workflow entity, one or more workflow states, and one or more workflow actions;

transitioning the workflow entity through the one or more workflow states in accordance with the one or more workflow actions;

representing the workflow entity as one or more lists of versioned development assets for the configuration management engine to manage;

providing the workflow entity to the managed deployment engine to be deployed; and

wherein the one or more representations of work to be performed or of work performed includes the request for change, and the workflow entity.

4. The method of claim 1, wherein the managed deployment workflow engine further provides:

responding to a transitioning of a workflow entity in a workflow of the configurable workflow engine;

creating a distribution using a configuration record from the configuration management engine, the configuration record corresponds to the transitioned workflow entity;

distributing the distribution to one or more host targets;

attaching a distribution log logging the distributing of the distribution to the one or more target hosts; and

wherein the one or more representations of work to be performed or of work performed includes the workflow entity, and the configuration record.

5. The method of claim 4, wherein the distributing is governed by a distribution policy, the distribution policy dictating any combination of:

who to distribute the distribution to, when to distribute the distribution, and who has access to the distribution policy.

6. The method of claim 5, wherein the distributing is limited to a collection of target hosts, each target host of the collection of target hosts share at least one distribution policy with the collection of target hosts.

7. The method of claim 1, wherein the interconnecting involves a configuration record, the configuration record further comprising;

one or more lists of versioned development assets representing work to be performed or of work performed; and

any combination of;

a target environment attribute identifying one or more target hosts to distribute a distribution to, a build administrator list attribute identifying who may build the distribution to be distributed, a release administrator list attribute identifying who may distribute the distribution, and a workflow entity identifier attribute identifying a workflow corresponding to the distribution.

8. The method of claim 7, wherein the configuration record and the distribution are accordingly labeled so as to provide auditability and bidirectional traceability.

9. A computer implemented method for providing auditability and bidirectional traceability of software in a software development lifecycle having at least a development phase and a deployment phase, the method comprising:

linking a development asset in the development phase to a deployment asset in the deployment phases so that any combination of;

i) the development asset developed in the development phase can be determined from the deployment asset deployed in the deployment phase,

ii) a deploying entity deploying the deployment asset in the deployment phase can be determined from the development asset developed in the development phase,

iii) a development request for developing the development asset in the development phase can be determined from the deployment asset deployed in the deployment phase, and

iv) a deployment environment where the deployment asset is being deployed in the deployment phase can be determined from the development asset in the development phase; and

as a function of the linking, providing auditability and bidirectional traceability of the software in the software development lifecycle.

10. The method of claim 9, wherein the linking comprising:

developing in the development phase the development request into the development asset through one or more development workflows;

creating the deployment asset from the development asset using a configuration record representing the developed development asset;

deploying in the deployment phase the deployment asset to the deployment environment using a deployment policy; and

logging the deploying in the deployment phase using a deployment log accessible to the development phase.

11. The method of claim 10, wherein each development workflow has one or more development workflow states and one or more development workflow actions for developing the development request into the development asset, each development workflow state transitions into another development workflow state in accordance with the one or more development workflow actions, whereby each transition represents any combination of:

assigning the development request or the development asset to one or more developers, working on the development asset by one or more developers, requiring the development asset in one workflow state meet a condition prior to transitioning to another workflow state, and deploying the development asset to one or more deployment environments.

12. The method of claim 10, wherein the configuration record describes a configuration of the development assets developed from the development request, and provides any combination of:

a deployment environment attribute identifying the deployment environment to deploy the deployment asset to, a build administrator list attribute identifying who may build the deployment asset to be deployed, a release administrator list attribute identifying who may deploy the deployment asset, and a development workflow identifier attribute identifying a development workflow corresponding to the development of the development asset from the development request.

13. The method of claim 10, wherein the distribution policy dictates any combination of:

who to distribute the deployment asset to, when to distribute the deployment asset, and who has access to the distribution policy.

14. The method of claim 10, wherein the development log logs any combination of:

what deployment asset was deployed, who deployed the deployment asset, where was the deployment asset deployed, and what configuration of development asset corresponds to the development asset.

15. The method of claim 9, wherein the linking comprising:

bridging the development phase of the software development lifecycle and the deployment phase of the software development lifecycle with a configurable workflow engine, a configuration management engine, and a managed deployment engine, wherein the configurable workflow engine, the configuration management engine, and the managed deployment engine are interconnected with one or more representations of work to be performed or of work performed.

16. The method of claim 15, wherein the one or more representation of work to be perform or of work performed includes a configuration record, a list of versioned development assets, and a workflow entity.

17. An system for providing a software development lifecycle with auditability and bidirectional traceability, the software development lifecycle having at least a development phase and a deployment phase, the apparatus comprising:

means for bridging the development phase of the software development lifecycle and the deployment phase of the software development lifecycle with a configurable workflow engine, a configuration management engine, and a managed deployment engine; and

means for interconnecting the configurable workflow engine, the configuration management engine, and the managed deployment engine with one or more representations of work to be performed or of work performed, wherein the one or more representations of work to be performed or of work performed provide the software development lifecycle with auditability and bidirectional traceability.

18. The system of claim 17, wherein the configuration management engine further provides:

means for responding to a request for change from the configurable workflow engine;

means for providing one or more lists of versioned development assets needed to work on the request for change to the configurable workflow engine;

means for providing a configuration record representing the one or more lists of versioned development assets to the managed deployment engine; and

wherein the one or more representations of work to be performed or of work performed includes the request for change, and the one or more lists of versioned development assets.

19. The system of claim 17, wherein the configurable workflow management engine further provides:

means for responding to a request for change;

means for initiating one or more workflows in response to the request for change, each workflow having a workflow entity, one or more workflow states, and one or more workflow actions;

means for transitioning the workflow entity through the one or more workflow states in accordance with the one or more workflow actions;

means for representing the workflow entity as one or more lists of versioned development assets for the configuration management engine to manage;

means for providing the workflow entity to the managed deployment engine to be deployed; and

wherein the one or more representations of work to be performed or of work performed includes the request for change, and the workflow entity.

20. The system of claim 17, wherein the managed deployment workflow engine further provides:

means for responding to a transitioning of a workflow entity in a workflow of the configurable workflow engine;

means for creating a distribution using a configuration record from the configuration management engine, the configuration record corresponds to the transitioned workflow entity;

means for distributing the distribution to one or more host targets;

means for attaching a distribution log logging the distributing of the distribution to the one or more target hosts; and

wherein the one or more representations of work to be performed or of work performed includes the workflow entity, and the configuration record.

21. The system of claim 20, wherein the means for distributing is governed by a distribution policy, the distribution policy dictating any combination of:

who to distribute the distribution to, when to distribute the distribution, and who has access to the distribution policy.

22. The system of claim 21, wherein the means for distributing is limited to a collection of target hosts, each target host of the collection of target hosts share at least one distribution policy with the collection of target hosts.

23. The system of claim 17, wherein the means for interconnecting involves a configuration record, the configuration record further comprising;

one or more lists of versioned development assets representing work to be performed or of work performed; and

any combination of;

a target environment attribute identifying one or more target hosts to distribute a distribution to, a build administrator list attribute identifying who may build the distribution to be distributed, a release administrator list attribute identifying who may distribute the distribution, and a workflow entity identifier attribute identifying a workflow corresponding to the distribution.

24. The system of claim 23, wherein the configuration record and the distribution are accordingly labeled so as to provide auditability and bidirectional traceability.

25. A computer program product comprising:

a computer usable medium having computer usable program code for providing auditability and bidirectional traceability of software in a software development lifecycle having at least a development phase and a deployment phase, the computer program product including;

computer usable program code for linking a development asset in the development phase to a deployment asset in the deployment phases so that any combination of;

i) the development asset developed in the development phase can be determined from the deployment asset deployed in the deployment phase;

ii) a deploying entity deploying the deployment asset in the deployment phase can be determined from the development asset developed in the development phase,

iii) a development request for developing the development asset in the development phase can be determined from the deployment asset deployed in the deployment phase, and

iv) a deployment environment where the deployment asset is being deployed in the deployment phase can be determined from the development asset in the development phase; and

as a function of the linking, providing auditability and bidirectional traceability of the software in the software development lifecycle.