Using the Methodology
Project Guide
Ulrich-SRM is designed in a modular fashion so that organizations with in-house redevelopment techniques may incorporate these into the overall process. Where in-house methods are either in common use, addressed in more detail or environmentally dependent, organizations can insert these methods into Ulrich-SRM.
One point to emphasize is that the techniques defined under the Ulrich-SRM redevelopment framework apply to an infinite variety of project types. In order to frame tasks and steps within the scope of specific project initiatives, analysts simply refer to one or more of the redevelopment scenarios. Initial entry into Ulrich-SRM, especially for the inexperienced user, should be through Ulrich-SRM scenarios.
Ulrich-SRM has been developed as a reference manual and guide. When organizations undertake a redevelopment endeavor, the tasks defined within Ulrich-SRM provide a "what to do" guide for various redevelopment tasks. It also helps place existing or proposed redevelopment tools within a much larger perspective.
However, Ulrich-SRM is not a replacement for training on a particular vendor tool, good management practices or new development methodology. The last point is particularly essential when using Ulrich-SRM Transformation tasks to support replacement/migration efforts.
Training Users
For anyone just becoming familiar with Ulrich-SRM, it is suggested that they review certain pieces of material based on their role within the organization. Senior IS management should read the executive summary, this introduction, the Enterprise Redevelopment Planning overview and scenario sections of interest. Applications management should review this introduction, the overview of each stage, the Inventory/Analysis stage and scenario sections of interest.
Managers and analysts chartered with cost and quality quotas should review the Inventory/Analysis and Positioning stages along with the Application Stabilization scenario. Individuals responsible for actually planning and performing redevelopment projects should use Ulrich-SRM as a reference guide, focusing on particular areas of interest for the project at hand. Finally, anyone working in the new development arena should review the functional assessment tasks of Inventory/Analysis, all of the Transformation stage and the Application Replacement scenario.
Roll Out
It is important to profile the type of organization that can benefit from Ulrich-SRM and the internal target audience. Any organization with a large installed base of existing application systems undergoing projects related to one or more of the Ulrich-SRM redevelopment scenarios will find Ulrich-SRM of value. Furthermore, any individual within an IS organization that is responsible for legacy applications should be aware of Ulrich-SRM.
The Executive Summary should be distributed to management so that they may ascertain the value of the systems redevelopment approach. Beyond that, a central redevelopment coordinator should work with various IS applications managers to determine how Ulrich-SRM applies to their unique project requirements.
The Ulrich-SRM step-by-step approach to systems redevelopment should be carefully reviewed by every organization with a significant investment in legacy systems and attempting to implement strategic information change requirements. The remainder of this document offers additional information on the Ulrich Systems Redevelopment Methodology and how it provides breakthrough approaches to the legacy systems dilemma.