MaRMI-RE: Systematic Componentization Process for Reengineering Legacy System Jung-Eun Cha, Chul-Hong Kim, Computational Science and Its Applications – ICCSA 2005 Lecture Notes in Computer Science Volume 3482, 2005, pp Presentation by: Rick Kok, , Business Informatics, Universiteit Utrecht

MaRMI-RE  Name: Magic and Robust Methodology Integrated- ReEngineering  Authors:  Jung Eun Cha, from the Software Engineering Department of the Electronics and Telecommunications Research Institute in Daejeon, Korea  Chul-Hong Kim, also from the Software Engineering Department of the Electronics and Telecommunications Research Institute in Daejeon, Korea

Daejon, Korea? © Google Maps

What is MaRMI-RE?  Purpose: ”we provide a componentization process […] for reengineering legacy systems into component systems so that legacy systems can continue to be developed to comply with varying business and technical environments” (Cha & Kim, 2005)  Basically a step-by-step plan for reverse engineering, redesigning and rebuilding a legacy system

What is a legacy system?  “A legacy system is an operational system that has been designed, implemented and installed in a radically different environment than that imposed by the current IT strategy and no longer supports the current business strategy” (Mitleton-Kelly, E., 2004)

Main phases

2. Re-engineering phase 4. Transfer phase 1. Planning phase 3. Componentization phase

Main phases  1. Planning.  Gain understanding of current business and requirements  Make strategy for transformation  Plan transformation  2. Re-engineering.  Information recovery on code level, design level and architectural level  3. Componentization.  Create components based on system functions  Adapt and alter components to new system  Transform and adopt components  Test integration  4. Transfer.  Train users  Install system  Test acceptance  Transfer system

PDD

PDD – Phase 2: Re-engineering phase

PDD – Phase 3: Componentization phase

Related literature  Positioning between other methods  CORUM (Common Object-based Re-engineering Unified Model) is a method that is based on “creating a data model for interoperability between several re-engineering toolsets” (Kazman, Woods & Carriere, 1998)  CORUM II basically is an adaptation of CORUM, but more complete by adding the software architecture concept and some more tools (Kazman, Woods & Carriere, 1998)  MARMI-RE: a method and tools for legacy system modernization (Cho, Cha, & Yang, 2004)  MaRMI-RE: Systematic Componentization Process for Reengineering Legacy System (this paper)

Related literature  Citations  Not widely used in the academic world. According to Google Scholar, cited by three papers  Hwang, K. S., Cui, J. F., & Chae, H. S. (2009, October). An Automated Approach to Componentization of Java Source Code. In Computer and Information Technology, CIT'09. Ninth IEEE International Conference (Vol. 2, pp ). IEEE.  刘芳, 瞿有甜, 周波, & 胡顺扬. (2009). 遗产软件重构技术的研究. 计算机技术与发展 ISTIC, 19(3).  Kok, R. (2013). BUSINESS INFORMATICS UNIVERSITEIT UTRECHT. (me)  Evaluations  One book evaluates the method  Dosch, W., Lee, R. & Wu, C. (2005). MaRMI-RE: a Method and Tools for Legacy System Modernization. Software Engineering Research, Management and Applications. 1st ed. Berlin, Germany: Springer. pp  Applications  According to Cha, J. and Kim, C. (2005), the method has been used twice in case studies. I couldn’t find any evidence that is has been used in other applications.

Example of a Use Case Diagram  Imagine a fictitious webshop. The next actors can be found in this example.  A client. He can place, pay and delete orders.  A salesperson. He has to approve orders of the clients by checking if they are correctly placed.  The financial department. This department accepts the payments of the client.  A shipping clerk, to ships the clients' orders.  The uses cases are:  Delete order  Place order  Pay order  Approve order  Send order

Example of a Use Case Diagram

Questions?