1. Compuware Corporation Business Driven SOA Edwin Schumacher Director of Product Management edwin.schumacher@compuware.com

2. Compuware Corporation Page 2 Development strategies Building dynamic, business-driven applications faster Faster – increase productivity dramatically – Model-Driven Architecture (MDA) based Development Dynamic – ability to change, agility – Service Oriented Architecture (SOA) Business-driven applications – close the gap between business and IT – Business Process Automation (BPA)

3. Compuware Corporation Faster Development Through a Model-Driven Architecture based approach

4. Compuware Corporation Page 4 Productivity Analysis Comparing MDA-based to Code-Centric Development Conducted by The Middleware Company Compared two development paradigms – MDA environment against a traditional code-centric IDE Two teams – Each had 1 architect & 2 developers – Architected and produced the same J2EE application – one using MDA, the other using a code-centric, enterprise-caliber IDE Report available on: http://www.omg.org/mda/presentations.htm Title: ‘MDA Productivity Study, June 2003’

5. Compuware Corporation Page 5 Study Results The Middleware Company MDA team delivered an error-free application in 330 hours versus 507 hours with the IDE tool, which equates to 35% productivity increase One of the programmers expected that the MDA team would have been 10-20% faster were it not for the fact that this was their first project using the tool The quality of the code of an application built with an MDA tool is comparable if not better than applications that are built with traditional techniques

6. Compuware Corporation Page 6 EDS Study Driving Business Agility with MDA-based development Background – Conducted by a SUN Certified J2EE Architect/Developer from EDS Compared two development paradigms – MDA environment against a traditional code-centric IDE Approach taken – Pet Store specification used – Compared lines of handcrafted code – Migration from EJB 1.1 to 2.0 Report available on: http://www.eds.com/thought/thought_leadership_agility_model_arch.pdf

7. Compuware Corporation Page 7 Study Results EDS Lines of handcrafted code – J2EE Pet Store using MDA development tool – 610 – J2EE Pet Store – 14,273 On average the developer wrote only one to four lines of Java code manually for each 200 lines generated automatically Upgrading to EJB 2.0 – Took less than 30 minutes to upgrade. This would typically be a manual process, taking several months Bottom line – Significant productivity gains achieved with MDA tool during application development and maintenance – Clearly demonstrates how MDA protects existing investments

8. Compuware Corporation Page 8 Model-Driven Architecture based Development Translate to Architecture Translate to Code Automation through Transformation patterns Increase consistency Improve manageability Ensure alignment Business Model Business-centric No technology details Standards based (UML) Architecture Model Implementation technology Blueprint J2EE/.NET Code Model Complete executable results Protect generated code Enable customization Business changes by Business Analysts Architecture changes by Architects Code changes by developers Separation of concerns

9. Compuware Corporation Ability to Change Through a Business Driven Service Oriented Architecture

10. Compuware Corporation Page 10 Business Model Step One Expressed in UML – Structure and behaviour – Class Model and Service Model Develop at a high abstraction level – Business centric – Undistorted by technical details – Focus on application functionality Enrich with business rules – Constraints – Expressions Automated reuse of model definitions and business rules – Change applications rapidly in the model

11. Compuware Corporation Page 11 Architecture Model Step Two Automatic transformation from Business Model to Architecture Model – Consistency and quality Logically layered components – Presentation Model Data schemas, Web components etc. – Business Logic Model Data schemas, key classes, entity components, session components etc. – Data Model Relational data schema Tables, columns, keys etc. Business Model Code Model Architecture Model Design Patterns Design Patterns

12. Compuware Corporation Page 12 Code Model Step Three Automatic transformation from Architecture Model to Code – Productivity, quality and consistency – J2EE Core Patterns – Presentation Tier MVC framework (Struts) Java Server Pages, Servlets – Business Logic Tier Bean class, home/remote and primary key classes etc. According to EJB specification – Data Access Tier SQL scripts for target database – Application deployment descriptors For target application server Transformation Patterns Business Model Code Model Architecture Model Code Patterns Code Patterns Technology Patterns Technology Patterns

13. Compuware Corporation Page 13 Service Enablement Coherent Migration to a Service Oriented Architecture SOA is more than just Web services Integration Model – Import WSDL, IDL, COBOL Copybooks (CICS and IMS/TM), Java/EJB signatures, SAP business objects, DBMS, etc. – Automatic re-design to business model through re-design patterns enabling participation of legacy applications in a SOA – Reduce complexity through adapter approach Business Model Code Model Architecture Model Design Patterns Design Patterns Code Patterns Code Patterns CICS IMS/TM Java, EJB Web Services SAP DBMS Corba Monolithic MQSeries, JMS Import Re-Design Patterns Re-Design Patterns

14. Compuware Corporation Page 14 A Service Oriented Architecture Increases the ability to change - flexibility Data DataStorage Create new database Create new database Upload existing database Upload existing database DataLogic Automatically generated Automatically generated Distributed Distributed Manage persistency Manage persistency BusinessLogic Application Contains business logic Contains business logic Integration layer Integration layer Exposable as Web Service Exposable as Web Service PresentationLogic Web-based Web-based Java Server Pages Java Server Pages

15. Compuware Corporation Closing the Gap between Business and IT Business Process Automation leveraging SOA

16. Compuware Corporation Page 16 Business Process Automation Align application with business process Key Performance Indicators Service Level Agreements Service Oriented Architecture Ability to change – agility Accelerate integration Model-Driven Architecture based Development Improved productivity Services by design - architecture The Evolution of Enterprise Application Development Development paradigm Business – IT alignment

17. Compuware Corporation Page 17 Business Process Automation The next step after SOA Data Databases Create new database Create new database Upload existing database Upload existing database DataAccessServices Generated Generated Distributed Distributed Manage data integrity Manage data integrity BusinessLogicServices Application Contain business logic Contain business logic Manage the transaction Manage the transaction Integration layer Integration layer PresentationServices Web-based Web-based Client-Server Client-Server Wireless Wireless Enter Order Ship Order BusinessProcess Organisational model Organisational model Actors and Roles Actors and Roles Process model Process model Check Customer Send Message Process

18. Compuware Corporation Page 18 Business Process Management Sales Production Shipping task customer Process focus Goals-driven Customer orientation Monitor performance indicators Tuning by workflow & business rules Continuous Monitoring & Tuning Change

19. Compuware Corporation Page 19 Conclusion Model-Driven Architecture based development (MDA) – Focus on automating the translations from Business Model to Architecture to Code as they are the main source of errors – Model Driven Architecture Service Oriented Architecture (SOA) – Make sure Application Services relate to Business Operations – Web Services are just one implementation of a SOA – Take an evolutionary approach to SOA implementation Business Process Automation (BPA) – A Service Oriented Architecture is the foundation for Business Process Automation – Integrate BPA into your application development paradigm – process-oriented application development