System and method for extracting UML models from legacy applications

• US 20080163159A1
• Filed: 01/03/2007
• Published: 07/03/2008
• Est. Priority Date: 01/03/2007
• Status: Abandoned Application

• Current Assignee: Micro Focus Incorporated (Open Text Corporation)
• Original Assignee: Relativity Technologies, Inc. (Open Text Corporation)
• Inventors: Oara, Ioan Mihai, Aprelev, Alexander
• Application Number:
  US11/649,134
• Publication Number:
  US 20080163159A1
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques

Abstract

A method and computer program product are provided for extracting UML models from legacy applications. The system involves extraction of UML models and importing and exporting than to other commercial UML tools. In a more specific aspect, UML objects are associated with business rules which have been extracted from a legacy application. In particular, UML diagrams are extracted from a legacy application for Use Case diagrams, Activity diagrams from screen flows, and Activity diagrams from program logic.

Claims

1. A method of extracting a UML model and business rules from a legacy application comprising;

accessing a created repository of all objects and information about said objects which are contained in a legacy application;

creating a UML model of the legacy application by processing said repository;

linking UML objects in the UML model to business rules and identifying additional details about the UML objects; and

creating an enhanced UML model of the legacy application from said linking of UML objects and from said identified details thereof.

2. The method of claim 1, wherein said creating of an enhanced UML model comprises creating said UML model as UML diagrams comprised of at least one of Use Case diagrams, Activity diagrams.

3. The method of claim 2, wherein;

the Use Case diagrams are created from a hierarchy of screens of the legacy application;

the Activity diagrams are created based on a flow of screens and procedures of the legacy application;

4. The method of claim 3, wherein said hierarchy of screens comprises a tree format starting with a main menu screen and subsequent flows to other screens, and where said Use Cases are designated by pointing to selected screens and creating a Use Case for each selected screen in a manner in which, if a selected screen is subordinate to a selected screen, then its Use Case extends or is included in the Use Case derived from the screen to which it is subordinate.

5. The method of claim 2, wherein said UML diagrams are populated with UML objects derived from the legacy application and can be manually modified to describe additional information not automatically extracted with said UML mining tool and also populated with additional UML objects manually created.

6. The method of claim 2, wherein said UML diagrams and UML objects are created in a manner in which they can be exported to and imported from another UML tool through XMI.

7. The method of claim 1, further comprising attaching business rules extracted from the legacy program to the UML model created with a UML mining tool to result in said enhanced UML model.

13. The method of claim 2, wherein said UML diagrams and UML objects are created in a manner in which they can be exported to and imported from another UML tool through XMI.

8. A method of extracting a UML model from a repository describing a legacy application containing information about the artifacts and business rules which are contained in a legacy application, comprising:

creating a UML model of the legacy application by processing said repository;

linking UML objects in the UML model to business rules and identifying additional details about the UML objects; and

creating an enhanced UML model of the legacy application from said linking of UML objects and from said identified details thereof.

9. The method of claim 8, wherein said creating of an enhanced UML model comprises creating said UML model as UML diagrams comprised of at least of Use Case diagrams and Activity diagrams.

10. The method of claim 9, wherein;

the Use Case diagrams are created from a hierarchy of screens of the legacy application;

the Activity diagrams are created based on a flow of screens of the legacy application.

11. The method of claim 10, wherein said hierarchy of screens comprises a tree format starting with a main menu screen and subsequent flows to other screens, and where said Use Cases are designated by pointing to selected screens and creating a Use Case for each selected screen in a manner in which, if a selected screen is subordinate to a selected screen, then its derived Use Case extends or is included in the Use Case derived from the screen to which it is subordinate.

12. The method of claim 9, wherein said UML diagrams are populated with UML objects derived from the legacy application that can be manually modified to describe additional information not automatically extracted with said UML mining tool and by UML objects manually defined by the user.

14. The method of claim 8, further comprising attaching business rules extracted from the legacy application to the UML objects created with the UML mining tool to result in said enhanced UML model.

15. A computer program product for extracting a UML model from a legacy application, comprising:

storage media for having a computer program product encoded thereon;

means for accessing a repository of all objects and information about said objects which are contained in a legacy application being operated on by the computer program product;

means for creating a UML model of the legacy application by processing said repository; and

means for linking UML objects in the UML model to business rules and specifying additional details about the UML objects, comprising at least information about the legacy objects from which they were derived to hereby create an enhanced UML model.

16. The computer program product of claim 15, further configured for creating the UML model as UML diagrams comprised of at least one of Use Case diagrams and Activity diagrams.

17. The computer program product of claim 16, wherein the product is configured for;

the Use Case diagrams being created from a hierarchy of screens of the legacy application;

the Activity diagrams being created based on a flow of screens of the legacy application.

18. The computer program product of claim 17, wherein said product is configured for having the hierarchy of screens comprise a tree format starting with a main menu screen and subsequent flows to other screens, and where said Use Cases are designated by pointing to selected screens and creating a Use Case for each selected screen in a manner in which, if a selected screen is subordinate to a selected screen, then its Use Case extends or is included in the Use Case derived from the screen to which it is subordinate.

19. The computer program product of claim 16, wherein said product is configured for having UML diagrams populated with UML objects derived from the legacy application that can be manually modified to describe additional information not automatically extracted with said UML mining tool and also populated with other objects manually created by the user.

20. The computer program product of claim 15, wherein said product is configured for having the UML diagrams and UML objects created in a manner in which they can be exported to and imported from another UML tool through XMI.

21. The computer program product of claim 15, wherein said product is further configured for attaching business rules extracted from the legacy application to the created UML model to result in said enhanced UML model.