Componentization method for reengineering legacy system

• US 20050138603A1
• Filed: 11/15/2004
• Published: 06/23/2005
• Est. Priority Date: 12/22/2003
• Status: Abandoned Application

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: Kim, Hyeon Soo, Yang, Young Jong, Kim, Chul Hong, Cha, Jung Eun
• Application Number:
  US10/986,875
• Publication Number:
  US 20050138603A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/53 Decompilation; Disassembly
• CPC Class Codes: G06F 8/74 Reverse engineering; Extracting design information from source code

Abstract

The present invention proposes a Magic and Robust Methodology Integrated-Reengineering (MaRMI-RE), which is a reengineering methodology defining a process including procedures and techniques for a componentization of legacy systems and work products generated during the process. A continuous evolution model for the legacy systems proposed in the present invention enables the legacy systems to be systematically transformed into component systems capable of smoothly complying with new requirements, thus maximizing productivity and efficiency of the legacy systems with respect to potential business and system change requirements.

Claims

1. A componentization method for reengineering a legacy system, comprising:

a) a planning phase of establishing a componentization strategy and a process plan of the legacy system for the reengineering;

b) a reverse engineering phase of analyzing program information of the legacy system and recovering functional information and architecture information;

c) a componentization phase of extracting components from the legacy system, establishing target architecture, and designing and implementing components to comply with the target architecture; and

d) a delivery phase of delivering transformed components which a user has approved after a forward engineering method.

2. The componentization method of claim 1, wherein the planning phase a) includes a current situation grasping activity, an improvement business model derivation activity, an improvement strategy establishment activity, and a development plan establishment activity.

3. The componentization method of claim 2, wherein the current situation grasping activity includes a business environment analysis task, a legacy system analysis task, and a maintenance work analysis task.

4. The componentization method of claim 2, wherein the improvement business model derivation activity includes a business use case modeling task, a business object modeling task, a vision establishment task, and an improved architecture establishment task.

5. The componentization method of claim 2, wherein the improvement strategy establishment activity includes a reengineering scope setting task, and an improvement strategy derivation task.

6. The componentization method of claim 2, wherein the development plan establishment activity includes a development process establishment task, and a development plan drafting task.

7. The componentization method of claim 1, wherein the reverse engineering phase b) includes a program analysis activity, a design information understanding activity, and an architecture understanding activity.

8. The componentization method of claim 7, wherein the program analysis activity includes a code restructuring task, a program semantic information analysis task, and a system semantic information analysis task.

9. The componentization method of claim 7, wherein the design information understanding activity includes a data information understanding task, and a functional information understanding task.

10. The componentization method of claim 7, wherein the architecture understanding activity includes a structural architecture understanding task, a behavioral architecture understanding task, and a technical architecture understanding task.

11. The componentization method of claim 1, wherein the componentization phase c) includes a component mining activity, an architecture transformation activity, a component transformation activity, a component development activity, and a component integration test activity.

12. The componentization method of claim 11, wherein the component mining activity includes a component grasping task, a component extraction task, a component identification task, and a component evaluation task.

13. The componentization method of claim 11, wherein the architecture transformation activity includes a transformation strategy examination task, a software (S/W) architecture definition task, and a system architecture definition task.

14. The componentization method of claim 11, wherein the component transformation activity includes a scenario design task, an interaction design task, a component interior design task, a component interface design task, and a component detailed design task.

15. The componentization method of claim 11, wherein the component development activity includes a component implementation task, a User Interface (UI) implementation task, and a component unit test task.

16. The componentization method of claim 11, wherein the component integration test activity includes an integration test task and a system test task.