Object-Oriented Reengineering Patterns
This reference details how to overturn legacy systems and comprehend difficulties, then reengineer the systems to comply with the new stipulations.
TABLE OF CONTENTS Object-Oriented Reengineering Patterns
Part I: Reverse Engineering
Chapter List
- Chapter 2: Setting Direction
- Chapter 3: First Contact
- Chapter 4: Initial Understanding
- Chapter 5: Detailed Model Capture
When you start a reengineering project, you will be pulled in many different directions, by management, by the users, by your own team. It is easy to be tempted to focus on the parts that are technically the most interesting, or the parts that seem like they will be easiest to fix. But what is the best strategy? How do you set the direction of the reengineering effort, and how do you maintain direction once you have started?
Forces
The following is a list of forces you should be aware of during the course of a reengineering project.
-
A typical reengineering project will be burdened with a lot of interests that pull in different directions. Technical, ergonomic, economic, and political considerations will make it difficult for you and your team to establish and maintain focus.
-
Communication in a reengineering project can be complicated by either the presence or absence of the original development team.
-
The legacy system will pull you toward a certain architecture that may not be the best for the future of the system.
-
You will detect many problems with the legacy software, and it will be hard to set priorities.
-
It is easy to get seduced by focusing on the technical problems that interest you the most, rather than what is best for the project.
-
It can be difficult to decide whether to wrap, refactor, or rewrite a...
Copyright Elsevier Science (USA) 2003 under license agreement with Books24x7
