Managing software lifecycle

• US 8,225,308 B2
• Filed: 10/26/2007
• Issued: 07/17/2012
• Est. Priority Date: 10/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sedukhin, Igor, Eshner, Daniel, Christensen, Erik B., Kulkarni, Amol Sudhakar, Panditharadhya, Prasad Sripathi, Venkataramanappa, Girish Mittur, Pogrebinsky, Vladimir, Wu, Haoran Andy
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): ST LEGER, GEOFFREY R
• Application Number:
  US11/925,680
• Publication Number:
  US 20090113407A1
• Time in Patent Office: 1,726 Days
• Field of Search: None
• US Class Current: 717/174
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

The present invention extends to methods, systems, and computer program products for managing software lifecycle. Based on declarative models and knowledge of their interpretation, embodiments of the present invention facilitate lifecycle management for model-based software applications. Lifecycle models, such as, for example, lifecycle state machine models are stored in a shared repository such that executive services can determine how software application lifecycles are to be managed and transitioned. Software lifecycle activities can verify that a transition is possible and identify any errors preventing a lifecycle transition. Model-based error handling and error recovery mechanisms can be used to correct any identified errors.

Claims

1. At a computer system, the computer system including a repository storing models that describe intended application behavior, executive services for refining models so that drivers can implement model related commands on applications, and driver services for implementing model related commands for applications, a method for managing the lifecycle of a software application, the method comprising:

an act of storing application models in a repository, each application model comprising a declarative model that describes the structure and behavior of a distributed application;

an act of storing command/workflow models in the repository, each command/workflow model defining lifecycle commands for performing a transition between states of the lifecycle of a corresponding distributed application;

an act of storing lifecycle models in the repository, each lifecycle model defining states of a corresponding distributed application including transitions that can be made between the states, each transition including a reference to a command/workflow model that defines commands for implementing the transition;

an act of receiving an application model reference along with a software lifecycle command, the application model reference referring to a first application model that is stored in the repository, the software lifecycle command indicating a software lifecycle transition that is to be applied to a first distributed application;

an act of utilizing the application model reference to access the first application model, the first application model including a lifecycle model reference referring to a first lifecycle model in the repository and including a lifecycle state attribute configured to store a lifecycle state value indicating a current lifecycle state of the first distributed application;

an act of utilizing the lifecycle model reference to access the first lifecycle model, the first lifecycle model defining states of the first distributed application including transitions that can be made between the states, the states including an initial state, a valid state, a ready state, a deployed state and a running state, each defined transition referencing a command/workflow model in the repository that defines commands for implementing the transition;

an act of accessing the lifecycle state attribute in the first lifecycle model to determine the current lifecycle state of the first distributed application, the current lifecycle state comprising one of the initial state, the valid state, the ready state, the deployed state, or the running state;

an act of referring to the first lifecycle model to determine if the first distributed application can transition from the current lifecycle state to a new lifecycle state in accordance with the lifecycle transition indicated in the received software lifecycle command, the lifecycle command comprising one of

a create deployment transition command for transitioning the distributed application from the initial state to the valid state,

a verify transition command for transitioning the distributed application from the valid state to the ready state,

a deploy transition command for transitioning the distributed application from the ready state to the deployed state, and

a start transition command for transitioning the distributed application from the deployed state to the running state;

an act of determining that the first lifecycle model references a first command/workflow model for transitioning the first distributed application to the new lifecycle state in accordance with the lifecycle transition indicated in the received software lifecycle command;

an act of instantiating a first command/workflow instance from the first command/workflow model; and

an act of the first command/workflow instance performing commands to transition the distributed application to the new lifecycle state.

2. The method as recited in claim 1, wherein the declarative model is defined in an XML based language.

3. The method as recited in claim 1, wherein the transitions defined in the first lifecycle model that can be made between the states include verify, deploy, fix deployed, fix running, start, stop, check running, check deployed, undeploy, clean, and re-verify.

4. The method as recited in claim 1, wherein the lifecycle model is a lifecycle state machine.

5. The method as recited in claim 1, wherein the act of referring to the first lifecycle model to determine if the first distributed application can transition from the current lifecycle state to a new lifecycle state comprises an act of referring to software lifecycle activities to check for errors related to applying the lifecycle state transition to the distributed application.

6. The method as recited in claim 5, further comprising:

an act of identifying one or more errors related to applying the lifecycle state transition to the first distributed application;

an act of automatically implementing further software lifecycle commands to correct the one or more errors prior to applying the lifecycle state transition to the first distributed application; and

an act of sending the received lifecycle command and the first application model to drivers, the drivers configured to translate the software lifecycle command and the first application model into actions to implement the lifecycle state transition for the first distributed application.

7. The method as recited in claim 5, further comprising:

an act of determining that there are no errors related to applying the lifecycle state transition to the first distributed application; and

an act of sending the received lifecycle command and the first application model to drivers, the drivers configured to translate the software lifecycle command and the first application model into actions to implement the lifecycle state transition for the first distributed application.

8. The method of claim 1, further comprising:

an act of translating the first application model into the first distributed application, the first distributed application being configured to emit events defined in an event model stored in the repository;

an act of collecting emitted events, including events related to the software lifecycle transition;

an act of forwarding the collected events to a monitoring service that can compute operational data for the first distributed application, the operational data for determining if subsequent lifecycle state transitions are possible for the first distributed application.

9. The method as recited in claim 8, further comprising:

an act of referring to a lifecycle state machine model to identify what the resulting software lifecycle state is to be as a result of applying the software lifecycle transition, prior to translating the first application model.

10. The method as recited in claim 8, wherein the act of translating the first application model into the first distributed application comprises an act of executive services and driver services interoperating in accordance with a commands and models protocol to transfer relevant model related data to the driver services.

11. The method as recited in claim 8, wherein the act of translating the first application model into the first distributed application comprises an act of instrumenting application parts of the first distributed application to emit events in accordance with the event model.

12. The method as recited in claim 8, wherein the act of collecting emitted events, including events related to the software lifecycle transition comprises an event collector polling for accumulated events from the first distributed application.

13. The method as recited in claim 8, further comprising:

an act of the monitoring service detecting an error in implementation of the software lifecycle command.

14. The method as recited in claim 13, further comprising:

an act of automatically implementing a further software lifecycle command to correct the detected error; and

an act of re-applying the software lifecycle transition to the first distributed application.

15. A system for managing the lifecycle of software, the system comprising one or more processors and one or more computer storage media storing computer executable instructions which when executed by the one or more processors perform the following acts:

an act of storing application models in a repository, each application model comprising a declarative model that describes the structure and behavior of a distributed application;

an act of storing command/workflow models in the repository, each command/workflow model defining lifecycle commands for performing a transition between states of the lifecycle of a corresponding distributed application;

an act of storing lifecycle models in the repository, each lifecycle model defining states of a corresponding distributed application including transitions that can be made between the states, each transition including a reference to a command/workflow model that defines commands for implementing the transition;

an act of receiving an application model reference along with a software lifecycle command, the application model reference referring to a first application model that is stored in the repository, the software lifecycle command indicating a software lifecycle transition that is to be applied to a first distributed application;

an act of utilizing the application model reference to access the first application model, the first application model including a lifecycle model reference referring to a first lifecycle model in the repository and including a lifecycle state attribute configured to store a lifecycle state value indicating a current lifecycle state of the first distributed application;

an act of utilizing the lifecycle model reference to access the first lifecycle model, the first lifecycle model defining states of the first distributed application including transitions that can be made between the states, the states including an initial state, a valid state, a ready state, a deployed state and a running state, each defined transition referencing a command/workflow model in the repository that defines commands for implementing the transition;

an act of accessing the lifecycle state attribute in the first lifecycle model to determine the current lifecycle state of the first distributed application, the current lifecycle state comprising one of the initial state, the valid state, the ready state, the deployed state, or the running state;

an act of referring to the first lifecycle model to determine if the first distributed application can transition from the current lifecycle state to a new lifecycle state in accordance with the lifecycle transition indicated in the received software lifecycle command, the lifecycle command comprising one of

a create deployment transition command for transitioning the distributed application from the initial state to the valid state,

a verify transition command for transitioning the distributed application from the valid state to the ready state,

a deploy transition command for transitioning the distributed application from the ready state to the deployed state, and

a start transition command for transitioning the distributed application from the deployed state to the running state;

an act of determining that the first lifecycle model references a first command/workflow model for transitioning the first distributed application to the new lifecycle state in accordance with the lifecycle transition indicated in the received software lifecycle command;

an act of instantiating a first command/workflow instance from the first command/workflow model; and

an act of the first command/workflow instance performing commands to transition the distributed application to the new lifecycle state.