Your SlideShare is downloading. ×
0
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
CompuwareCorporation Business Driven SOA Edwin Schumacher
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

CompuwareCorporation Business Driven SOA Edwin Schumacher

275

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
275
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • COPYRIGHT © 2005 Compuware Corporation March 17, 2005 IDC – Service Oriented Architecture Conference 2005
  • COPYRIGHT © 2005 Compuware Corporation March 17, 2005 IDC – Service Oriented Architecture Conference 2005
  • COPYRIGHT © 2005 Compuware Corporation March 17, 2005 IDC – Service Oriented Architecture Conference 2005 2 2 2
  • COPYRIGHT © 2005 Compuware Corporation March 17, 2005 IDC – Service Oriented Architecture Conference 2005
  • COPYRIGHT © 2005 Compuware Corporation March 17, 2005 IDC – Service Oriented Architecture Conference 2005
  • Transcript

    • 1. Business Driven SOA Edwin Schumacher Director of Product Management [email_address]
    • 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. Faster Development Through a Model-Driven Architecture based approach
    • 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. 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. 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. 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. 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. Ability to Change Through a Business Driven Service Oriented Architecture
    • 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. 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
    • 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 Technology Patterns
    • 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 Code Patterns
      • CICS
      • IMS/TM
      • Java, EJB
      • Web Services
      • SAP
      • DBMS
      • Corba
      • Monolithic
      • MQSeries, JMS
      Import Re-Design Patterns
    • 14. A Service Oriented Architecture Increases the ability to change - flexibility Data Data Storage
      • Create new database
      • Upload existing database
      Data Logic
      • Automatically generated
      • Distributed
      • Manage persistency
      Business Logic Application
      • Contains business logic
      • Integration layer
      • Exposable as Web Service
      Presentation Logic
      • Web-based
      • Java Server Pages
    • 15. Closing the Gap between Business and IT Business Process Automation leveraging SOA
    • 16. The Evolution of Enterprise Application Development Development paradigm Business – IT alignment
      • 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
    • 17. Business Process Automation The next step after SOA Data Databases
      • Create new database
      • Upload existing database
      Data Access Services
      • Generated
      • Distributed
      • Manage data integrity
      Business Logic Services Application
      • Contain business logic
      • Manage the transaction
      • Integration layer
      Presentation Services
      • Web-based
      • Client-Server
      • Wireless
      Enter Order Ship Order Business Process
      • Organisational model
      • Actors and Roles
      • Process model
      Check Customer Send Message Process
    • 18. Business Process Management Sales Production Shipping task customer customer
      • Process focus
      • Goals-driven
      • Customer orientation
      task task
      • Monitor performance
      • indicators
      • Tuning by workflow
      • & business rules
      Continuous Monitoring & Tuning Change
    • 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
    • 20.  

    ×