1. Application Transformation Building Competitive Applications

2. Simplify your business © 2004 Progress Software Corporation2 OpenEdge Reference Architecture Seminar Series Agenda n Current Challenges n OpenEdge Reference Architecture n Application Transformation –Challenges and Guidelines –The Zachman Framework –The Application Transformation Approach n Next Steps

3. Simplify your business © 2004 Progress Software Corporation3 OpenEdge Reference Architecture Seminar Series Transformation The Musée d'Orsay n From 17 th century gardens –To 18 th century hotel –To 19 th century railway station n To 21 st century art museum http://www.musee-orsay.fr

4. Simplify your business © 2004 Progress Software Corporation4 OpenEdge Reference Architecture Seminar Series Application Transformation “Describes the process of applying changes to the form, design, and/or function” of a legacy application William Ulrich (2002) Legacy Systems – Transformation Strategies

5. Simplify your business © 2004 Progress Software Corporation5 OpenEdge Reference Architecture Seminar Series OpenEdge Transformation Resources n Provide a fully documented methodology n Supplement the methodology with tools, templates, and samples n Assist partners with their application transformation efforts Method for transforming applications Providing assistance in evolving to modern methods, enabling you to deliver more competitive applications

6. Simplify your business © 2004 Progress Software Corporation6 OpenEdge Reference Architecture Seminar Series OpenEdge Transformation Resources n Standardized methodology for Progress n Collection of tools, papers, and information on moving applications forward n Reflection of experiences and efforts from the entire Progress community n Not a silver bullet, nor a red button!

7. Simplify your business © 2004 Progress Software Corporation7 OpenEdge Reference Architecture Seminar Series How do you Transform an Application? Legacy Application Modern Application Just start coding, right?

8. Simplify your business © 2004 Progress Software Corporation8 OpenEdge Reference Architecture Seminar Series Words of Wisdom Its a different world “You cannot solve the “You cannot solve the problems of the present with the solutions that problems of the present with the solutions that produced them.” produced them.” Einstein

9. Simplify your business © 2004 Progress Software Corporation9 OpenEdge Reference Architecture Seminar Series Transformation Challenges nMonolithic design nThousands of programs, and lines of code nInconsistent standards nComplex dependencies nFunctional fragmentation nElusive system semantics nRedundancy, little reuse nBrittle to enhancement or change nLack of documentation nLack of transformation tools

10. Simplify your business © 2004 Progress Software Corporation10 OpenEdge Reference Architecture Seminar Series Why Transformation Projects Fail nFlawed or incomplete transformation strategy nRelying on technical expertise alone nInadequately trained people tied to old technologies n“We know our application inside-out!” nLittle time spent gathering or validating requirements nArchitecture is not the primary consideration nNo recognition of a distinctive transformation process nInadequate planning and weak resolve to follow plans nLack of long-term commitment from management nManagement predetermines technical decisions Adapted from Bergey, Smith, Tilley, Weiderman, and Woods, Why Reengineering Projects Fail (CMU/SEI-99-TR-010). Carnegie-Mellon Software Engineering Institute

11. Simplify your business © 2004 Progress Software Corporation11 OpenEdge Reference Architecture Seminar Series Guidelines for Transformation Success nFormulate a complete and coherent strategy nTechnical expertise and disciplined management nInvest in training people on new technology nInvest in learning what you don’t know nGather and validate requirements with customers nArchitecture is the foundation nEstablish an appropriate transformation process nInvest in planning and discipline to execute plans nCommit to transformation as a long-term investment nTechnical decisions based on proper analysis Adapted from Bergey, Smith, Tilley, Weiderman, and Woods, Why Reengineering Projects Fail (CMU/SEI-99-TR-010). Carnegie-Mellon Software Engineering Institute

12. Simplify your business © 2004 Progress Software Corporation12 OpenEdge Reference Architecture Seminar Series A Model to Make Sense of Chaos… Logical Design Physical Design Implementation Deployment Conceptual Context Adapted from John Zachman, The Zachman Framework, Zachman Institute for Framework Advancment Data (what & where ?) Function (how?) Network (where?) People (who?) Time (when?) Motivation (why?) What, how, where, who, when & why?

13. Simplify your business © 2004 Progress Software Corporation13 OpenEdge Reference Architecture Seminar Series Zachman Framework Data (what?) Function (how?) Network (where?) People (who?) Time (when?) Motivation (why?) Contextual (Scope) List of important business entities List of core business processes List of business locations List of important users and user groups List of important business events List of business goals Conceptual (Business Model) Conceptual Data Model Business Process Model Business Logistics Business Workflow Model Master Schedule Business Plan Logical Design (System Model) Logical Data/Class Model Application Architecture Distributed Architecture Human Interface Architecture Processing Structure Business Rule Model Physical Design (Technology Model) Physical Data/Class Model Component Design Technology Architecture Presentation Architecture Control Structure Rule Designs Physical Implementation (Application) Data Definitions ProgramsNetwork Architecture Security Architecture Timing Definition Rule Specifications Deployment (Operation) DataFunctionNetworkOrganizationScheduleStrategy Adapted from John Zachman, The Zachman Framework, Zachman Institute for Framework Advancment

14. Simplify your business © 2004 Progress Software Corporation14 OpenEdge Reference Architecture Seminar Series Zachman Framework n Application Transformation projects carry a significant level of risk… …which must be managed and mitigated by gathering complete and accurate information through a methodical process of discovery and analysis n The Zachman Framework helps to identify and analyze areas that are relevant to a given application transformation scenario Simply a mental model

15. Simplify your business © 2004 Progress Software Corporation15 OpenEdge Reference Architecture Seminar Series Abstract Concrete Legacy Application Modern Application Logical Design Physical Design Implementation Deployment Conceptual Context Logical Design Physical Design Implementation Deployment Conceptual Context Analyze & Model Redesign & Harvest Build & Test You Need a Model for Transformation

16. Simplify your business © 2004 Progress Software Corporation16 OpenEdge Reference Architecture Seminar Series Application Transformation Approach Phase 1 Transformation Assessment Phase 1 Transformation Assessment Phase 2 Analysis & Modeling Phase 2 Analysis & Modeling Phase 3 Redesign & Harvesting Phase 3 Redesign & Harvesting Phase 4 Build & Test Phase 4 Build & Test

17. Simplify your business © 2004 Progress Software Corporation17 OpenEdge Reference Architecture Seminar Series In iterative process to transform your application Awareness Transformation Assessment Analysis & Modeling Redesign & Harvesting Build & Test Transformation Continues Engagement Capability Gap Fulfillment Project Planning & Management Commitment Application Transformation Approach

18. Simplify your business © 2004 Progress Software Corporation18 OpenEdge Reference Architecture Seminar Series Transformation is an Iterative Process Application Partner 2 nd Iteration N th Iteration … 1 st Iteration Technical Empowerment Monitoring Spot Mentoring Mentoring

19. Simplify your business © 2004 Progress Software Corporation19 OpenEdge Reference Architecture Seminar Series n Formulate an effective application transformation plan that aligns with business goals –Current business position, business goals, and business strategy –Overview of legacy application including new functional and non-functional requirements –Assessments of the current infrastructure n Technology, people and skills, processes, and organizational capability Phase 1 – Transformation Assessment

20. Simplify your business © 2004 Progress Software Corporation20 OpenEdge Reference Architecture Seminar Series n Capture and develop a set of models to represent the form and function of the legacy application n Compile an inventory of physical legacy artifacts which may feasibly be harvested for reuse Phase 2 – Analysis & Modeling

21. Simplify your business © 2004 Progress Software Corporation21 OpenEdge Reference Architecture Seminar Series Phase 3 – Redesign & Harvest n Transform the models captured from the legacy system into models for the target application n Extract and rework the physical legacy artifacts listed in the harvest inventory

22. Simplify your business © 2004 Progress Software Corporation22 OpenEdge Reference Architecture Seminar Series Phase 4 – Build & Test n Build and test a new, modern application using the redesigned models and the harvested legacy components

23. Simplify your business © 2004 Progress Software Corporation23 OpenEdge Reference Architecture Seminar Series “It is not the strongest of the species that survives, nor the most intelligent, but the one that responds to change.” Charles Darwin

24. Simplify your business © 2004 Progress Software Corporation24 OpenEdge Reference Architecture Seminar Series n Formalized approach n Industry standards n Architecture-centric n Combines management and technology n Reduced risk n Enhanced quality n Expanded capabilities n Organizational learning n Applications aligned with business goals Key benefits Application Transformation Approach

25. Simplify your business © 2004 Progress Software Corporation25 OpenEdge Reference Architecture Seminar Series Benefits of a Competitive Application n Greater marketability n Greater sales penetration n Higher revenue n Enhanced business agility n Enhanced organizational capability n Improved efficiencies / reduced overheads n Greater profitability

26. Simplify your business © 2004 Progress Software Corporation26 OpenEdge Reference Architecture Seminar Series Recommended Reading n Books –Software Architecture in Practice n ISBN 0-321-15495-9 –Documenting Software Architectures n ISBN 0-201-70372-6 –Legacy Systems n ISBN 0-13-044927-X –Modernizing Legacy Systems n ISBN 0-321-11884-7

27. Simplify your business © 2004 Progress Software Corporation27 OpenEdge Reference Architecture Seminar Series Review and Discussion Application transformation n Challenges and Guidelines n The Zachman Framework n The Application Transformation Approach

28. Simplify your business © 2004 Progress Software Corporation28 OpenEdge Reference Architecture Seminar Series Agenda n Current Challenges n OpenEdge Reference Architecture n Application Transformation n Next Steps

29. Simplify your business © 2004 Progress Software Corporation29 OpenEdge Reference Architecture Seminar Series Next Steps n Start NOW –Business plan –Application roadmap, using the Reference Architecture –Get to the current environment (Progress Version 9) –Training –Plan, Plan, Plan n Get comfortable with the OpenEdge Reference Architecture –Read presentation –Attend Seminars / Classes n Training –Skills Assessment – create education plan –Non-Progress training may be needed –Commit to training your people –Willing to ‘invest in themselves’ n Understand it’s not a short process, must stay committed

30. Simplify your business © 2004 Progress Software Corporation30 OpenEdge Reference Architecture Seminar Series Summary & Close “Enterprises will use SOBAs to gain a competitive advantage. They will be able to combine application functions at more-granular levels in more-innovative approaches than previously feasible” Charles Abrams Gartner Article Top View, 17 February 2004

31. Simplify your business © 2004 Progress Software Corporation31 OpenEdge Reference Architecture Seminar Series Whiteboard Discussion Customer implementations etc