OPEN APPLICATION LIFECYCLE MANAGEMENT FRAMEWORK

• US 20100017792A1
• Filed: 07/14/2009
• Published: 01/21/2010
• Est. Priority Date: 07/14/2008
• Status: Active Grant

• Current Assignee: Borland Software Corporation (Open Text Corporation)
• Original Assignee: Borland Software Corporation (Open Text Corporation)
• Inventors: Sauers, Ronald D., Velur, Shashi Kumar, Guck, Randal Lee, Gronback, Richard Charles, Chase, Raymond, Young, Charles C., Ambichl, Ernst
• Granted Patent: US 8,584,112 B2
• Time in Patent Office: Days
• US Class Current: 717/162
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

Techniques for open application lifecycle management frameworks are described, including using a framework hosted on one or more computers and having one or more services to integrate the one or more services with one or more applications using one or more providers, each of the one or more providers is adapted to at least one of the one or more applications, registering one or more repositories associated with the one or more applications using a location service module, receiving an input creating a project context associated with a project, data associated with the input being stored in a data structure associated with the project, the data structure being stored in a repository associated with the framework, generating a link, after registering the one or more repositories, between one or more element containers associated with the project, the link and the one or more element containers being stored in the repository, and configuring the framework to detect another input indicating interaction with an artifact, other data associated with the interaction being mapped between the one or more repositories and the repository using a domain model.

Claims

1. A method, comprising:

using a framework hosted on one or more computers and having one or more services to integrate the one or more services with one or more applications using one or more providers, wherein each of the one or more providers is adapted to at least one of the one or more applications;

registering one or more repositories associated with the one or more applications using a location service module;

receiving an input creating a project context associated with a project, data associated with the input being stored in a data structure associated with the project, the data structure being stored in a repository associated with the framework;

generating a link, after registering the one or more repositories, between one or more element containers associated with the project, the link and the one or more element containers being stored in the repository; and

configuring the framework to detect another input indicating interaction with an artifact, other data associated with the interaction being mapped between the one or more repositories and the repository using a domain model.

2. The method of claim 1, wherein each of the one or more providers is an application programming interface of the framework.

3. The method of claim 1, wherein the framework is an application.

4. The method of claim 1, wherein the framework is an open application lifecycle management application.

5. The method of claim 1, wherein the one or more applications are implemented on one or more other computers that are in data communication with the framework.

6. The method of claim 1, wherein at least one of the one or more services comprises an element service.

7. The method of claim 1, wherein at least one of the one or more services comprises a project service.

8. The method of claim 1, wherein at least one of the one or more services comprises a notification service.

9. The method of claim 1, wherein at least one of the one or more services comprises a security service.

10. The method of claim 1, wherein at least one of the one or more services comprises a user management service.

11. The method of claim 1, wherein at least one of the one or more services comprises a search service.

12. The method of claim 1, wherein at least one of the one or more services comprises a tray service.

13. The method of claim 1, wherein the framework further comprises a service implementation layer configured to provide run-time integration of data provided by a client.

14. The method of claim 13, wherein a change request associated with the artifact is normalized between the one or more repositories and the repository, the change request being configured to display using any of the one or more applications.

15. The method of claim 1, wherein the framework is configured to automatically manage a requirement associated with the artifact and the project using the link between the one or more element containers.

16. A system, comprising:

a database configured to store data associated with a framework; and

logic configured to use the framework hosted on one or more computers and having one or more services to integrate the one or more services with one or more applications using one or more providers, wherein each of the one or more providers is adapted to at least one of the one or more applications, to register one or more repositories associated with the one or more applications using a location service module, to receive an input creating a project context associated with a project, the data associated with the input being stored in a data structure associated with the project, the data structure being stored in a repository associated with the framework, to generate a link, after registering the one or more repositories, between one or more element containers associated with the project, the link and the one or more element containers being stored in the repository, and to configure the framework to detect another input indicating interaction with an artifact, other data associated with the interaction being mapped between the one or more repositories and the repository using a domain model.

17. A system, comprising:

a framework comprising an application lifecycle management client in data communication with a service, the service being integrated with the framework using a service implementation layer and a domain model, wherein the domain model is used to map data from one or more applications to the framework, the data being stored in a repository;

an application in data communication with the framework using one or more providers, wherein the providers adapt the data exchanged between the framework and the applications according to the domain model;

a data warehouse configured to store the data upon extraction from the application or the framework, wherein an extract, transform, and load engine is configured to extract the data; and

an analytical module configured to use the data stored in the data warehouse or the repository, wherein the analytical module is configured to generate a report or business intelligence associated with the data.

18. The system of claim 17, wherein the analytical module is configured to provide historical reports using the business intelligence application.

19. The system of claim 17, wherein the framework is configured to map generated data from the service to the data from the one or more applications using a common data representation generated according to the domain model.

20. A computer program product embodied in a computer readable medium and comprising computer instructions for:

using a framework hosted on one or more computers and having one or more services to integrate the one or more services with one or more applications using one or more providers, wherein each of the one or more providers is adapted to at least one of the one or more applications;

registering one or more repositories associated with the one or more applications using a location service module;

receiving an input creating a project context associated with a project, data associated with the input being stored in a data structure associated with the project, the data structure being stored in a repository associated with the framework;

generating a link, after registering the one or more repositories, between one or more element containers associated with the project, the link and the one or more element containers being stored in the repository; and

configuring the framework to detect another input indicating interaction with an artifact, other data associated with the interaction being mapped between the one or more repositories and the repository using a domain model.