Model Based Planning in Service Oriented Architecture

390 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
390
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • With Drivers we indicate the forces and situations that are causing us to take actions.
  • With Drivers we indicate the forces and situations that are causing us to take actions.
  • Model Based Planning in Service Oriented Architecture

    1. 1. Model Based Planning in Service Oriented Architecture (SOA) Dave McCoy Associate Technical Fellow The Boeing Company
    2. 2. Definitions <ul><li>Service Oriented Architecture </li></ul><ul><li>Service Oriented Architecture (SOA) is an architectural concept where software functionalities are exposed as services. </li></ul>Service Requestor Service Provider Service Registry Network Existing Systems Or Services Service A Service is a software component designed to be invoked by name across applications or across organizations via a well-defined interface Service characteristics: Network-enabled Self-contained Client-agnostic Service Interface Service Service Implementation
    3. 3. SOA Attributes Benefits Characteristics <ul><li>Smaller software components, and greater reuse of standard software through plug and play approach </li></ul><ul><li>Heavily dependent of use of industry standards and a robust network </li></ul><ul><li>Business flexibility provided by increased granularity of processes enabled through services </li></ul><ul><li>Ability to quickly create business processes and composite applications to respond to changes in the marketplace </li></ul><ul><li>Decrease development and deployment cycle times through the use of pre-built, reusable services building blocks </li></ul>
    4. 4. What is Really Different <ul><li>1970 - 1980’s </li></ul><ul><ul><li>Monolithic applications </li></ul></ul><ul><ul><li>Mainframe ~ dumb terminal </li></ul></ul><ul><ul><li>Little integration, Applications in functional domains </li></ul></ul><ul><li>1990’s </li></ul><ul><ul><li>Distributed applications </li></ul></ul><ul><ul><li>Client ~ server </li></ul></ul><ul><ul><li>Integration within functions domains / application suites ~ proprietary </li></ul></ul><ul><li>Early 2000’s </li></ul><ul><ul><li>Loosely Coupled Applications </li></ul></ul><ul><ul><li>Web enabled </li></ul></ul><ul><ul><li>Integration using proprietary middleware and some web services </li></ul></ul><ul><li>Late 2000’s </li></ul><ul><ul><li>Composite applications </li></ul></ul><ul><ul><li>Rich web clients / portals </li></ul></ul><ul><ul><li>Standards based integration and orchestration </li></ul></ul>By 2008, Gartner predicts that SOA will be a prevailing software-engineering practice, ending the 40-year domination of monolithic software architecture Rigid Silo’s Agile Collaboration
    5. 5. Industry Trends <ul><li>Gartner </li></ul><ul><ul><li>“ By 2006, more than 60 percent of enterprises will consider SOA a guiding principle in designing their new mission-critical business applications and business processes (0.7 probability)”. </li></ul></ul><ul><ul><li>“ By 2006, more than 75 percent of midsize and large enterprises will have deployed SOA-enabled development tools and middleware (0.8 probability)” </li></ul></ul><ul><ul><li>“ Services-oriented development will dramatically increase in near future.” </li></ul></ul>
    6. 6. SOA Maturity ~ Gartner
    7. 7. IT Architecture Overview Business Intelligence Services Process Orchestration Service Registry B2B Interactions Collaboration Tools Portal Service Applications & Data Application functions are built as components (or &quot; services &quot;) that are loosely-coupled and well-defined to support interoperability, and to improve flexibility and re-use IBM’s ESB Graphic
    8. 8. Evolution of Aerospace Assembly Planning <ul><li>1970’s </li></ul><ul><ul><li>Paper planning </li></ul></ul><ul><ul><li>Word of mouth </li></ul></ul><ul><li>1980’s </li></ul><ul><ul><li>Electronic textual instructions </li></ul></ul><ul><ul><li>Network </li></ul></ul><ul><li>1990’s </li></ul><ul><ul><li>More computer based textual instructions </li></ul></ul><ul><ul><li>2D graphical additions </li></ul></ul><ul><ul><li>Internet </li></ul></ul><ul><li>2000’s </li></ul><ul><ul><li>3D graphic additions </li></ul></ul><ul><ul><li>Network bandwidth increases </li></ul></ul><ul><ul><li>Web based textual/graphical instructions </li></ul></ul><ul><ul><li>Model based work instructions </li></ul></ul>By 2010, ….. Text based Model Based INFORMATION CONTENT
    9. 9. PDM 2D Work Instructions 3D Work Instructions Manufacturing Planning Process Orchestration Web Services Web Services Assembly Planning in SOA Automation Internet Suppliers
    10. 10. Web Based 3D Viewer Integrated XVL – eXtensible Virtual world description Language
    11. 11. XVL <ul><li>Develops standards-based XVL® 3D format </li></ul><ul><ul><li>Provides 1/50-1/200 compression of 3D images </li></ul></ul><ul><ul><ul><li>order of magnitude better than currently available </li></ul></ul></ul><ul><ul><li>XML-based format fuses visual and non-visual data </li></ul></ul><ul><ul><li>Works with major CAD/CAM systems </li></ul></ul><ul><ul><li>Highly accurate </li></ul></ul><ul><li>Leverages 3D data across the enterprise by XVL® </li></ul><ul><ul><li>Speeds development & design cycles </li></ul></ul><ul><ul><li>Allows departments and partners collaborate </li></ul></ul><ul><ul><li>Enables automation and reduces costs for improved Manufacturing, Customer Service, Marketing, etc. </li></ul></ul>
    12. 12. Web Based 3D Viewer Integrated http://www.lattice3d.com/3ddemo/SW/SW.html
    13. 13. Web Based 3D Viewer Integrated http://www.lattice3d.com/3ddemo/AssemblyInstructions/index.xml#
    14. 14. Major Challenges <ul><li>Maturity of SOA </li></ul><ul><li>Process Orchestration </li></ul><ul><li>Vendor Support </li></ul><ul><li>Interoperability Standards </li></ul><ul><ul><li>S95, OASIS, BPEL </li></ul></ul>This Is Where We Need To Work Together
    15. 15. Process Orchestration Application Process Logic Functions Today Could support different business model Services Process Execution/Engine Future Application / New Process
    16. 16. Future <ul><li>Agile systems that adapt quickly to changing markets and process requirements </li></ul><ul><li>Incorporation of new technologies: </li></ul><ul><ul><li>Web Services </li></ul></ul><ul><ul><ul><li>XML, HTTP, SOAP </li></ul></ul></ul><ul><li>Service Oriented Architecture </li></ul><ul><li>Model Driven Enterprise </li></ul><ul><li>Process Orchestration along Supply Chain </li></ul><ul><li>IT Skills to Support New Environment </li></ul>The Future Has Never Been More Exciting And Challenging
    17. 17. Thank You

    ×