Service-design in large-scale projects
                                                        Author: Steffen Rumpf
     ...
Agenda



        ✔ Intention
        ✔ Goals
        ✔ Basics of service design
        ✔ Approach of service design
    ...
IT under siege




                                 “If business is from Mars, then IT is from Venus.”
                   ...
Markets in state of flux



        About last decades:
        ✔ Almost stable market
        ✔ Established enterprises c...
Markets in state of flux



        What do enterprises need to succeed today?
        ✔ High business agility
           ...
IT/Business Alignment



      Business processes in the center of attraction



                                         ...
IT/Business Alignment



      Definition:
        ✔ State in which a business organization is able to use information
   ...
Why can SOA solve our problems?



                                                                                       ...
Project background



        ✔ Project enfolded 50 high-level-services (BPEL)
               ➢ Orchestrate several low-le...
Project goal



        ✔ Consolidation of:
               ➢ Different integration solutions (with redundant business logi...
The world that was!




                                                                       Frontend 2

               ...
The world that was!

                                      Frontend 1                  Frontend 2                 Frontend...
Goals of the service-design



        ✔ Separation between design(functional) and development(technical)
        ✔ Design...
Approach



       ✔ Definition of requirements
       ✔ Initial design
       ✔ Detailed design
       ✔ Test of the BPEL...
Distributed Knowledge




                                              operating departments (requestor)
                ...
Requirements & Changes



     Requirement's
       ✔ have to be send to the “requirement-input-channel“
       ✔ are defi...
Objectives of the service designer



        ✔ Creation of the technical design
               ➢ Analyze new requirements...
Service-design using Innovator

        ✔ Model driven Development (MDD)

                                Innovator       ...
Example: service object-model (SOM)




                                                                                  ...
Example: service activity diagram




                                                                                    ...
Example: Functional mapping




                                                                                          ...
Tools used



        ✔ MID Innovator – used to create activity and object diagram's
        ✔ Altova XML Spy – customizin...
Core questions for service design



        ✔ Which problem should be solved by this service?
        ✔ Which data is req...
Objectives of the developer



        ✔ Technical implementation of the functional design
        ✔ Needs technical know-...
Business Object Modell



      Definition from wikipedia:

      „Within Business Process Management all business objects...
BOM example (UML)


                                                                                      ✔ BOM definition...
Pro and contra BOM



        ✔ Pro
               ➢ Consistent naming conventions, attributes and
                 relati...
Service versioning



       ✔ Version changes
              ➢ Changes with consumer dependency => major version change
  ...
Governance Aspects



        ✔ Which services in which version are active which services have to be
          retired
   ...
Thank you for your attention!

                                                               Questions?




             ...
Upcoming SlideShare
Loading in...5
×

Servicedesign In Großprojekten

1,056

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
1,056
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Servicedesign In Großprojekten"

  1. 1. Service-design in large-scale projects Author: Steffen Rumpf Jan 19, 2010 1 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  2. 2. Agenda ✔ Intention ✔ Goals ✔ Basics of service design ✔ Approach of service design ✔ Objectives of the service designer ✔ Objectives of the service developer ✔ Versioning of services 2 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  3. 3. IT under siege “If business is from Mars, then IT is from Venus.” — Dave Welsh, Microsoft 3 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  4. 4. Markets in state of flux About last decades: ✔ Almost stable market ✔ Established enterprises can easily hold position In our days: ✔ Market has become unpredictable ➢ e.g. dot com bust ✔ Changing rate of "driving forces" has increased ➢ Caused by technological / public-policy alterations ✔ Enterprise extinction rate has increased significantly ➢ Worldwide major bankruptcies ➢ Market requirements rise 4 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  5. 5. Markets in state of flux What do enterprises need to succeed today? ✔ High business agility ➢ New markets evolve => Ability to take the opportunity FIRST ✔ Ability to adapt to new situations as fast as possible ➢ Internal flexibility, e.g. rearranging enterprise structures ➢ External flexibility, e.g. integrating new partner enterprises ✔ Well-regulated continous business transformation ✔ Maximum efficiency 5 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  6. 6. IT/Business Alignment Business processes in the center of attraction Changes very quickly Customer Market Has to be aligned to the changing market Competitors Business processes Has to be changed as fast as possible IT 6 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  7. 7. IT/Business Alignment Definition: ✔ State in which a business organization is able to use information technology (IT) effectively to achieve business objectives - typically improved financial performance or marketplace competitiveness. ✔ Alignment is the capacity to demonstrate a positive relationship between information technologies and the accepted financial measures of performance. ✔ Ask yourself: ➢ In the context of IT service delivery, do you feel that your IT organization is optimized in its alignment with business? ➢ As IT Leaders, do you ever get the feeling you aren’t seen as aligned with the Business Leaders that are your colleagues? 7 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  8. 8. Why can SOA solve our problems? Dynamic Service Orchestration High-level services Business Business Business (Composite services) Service Service Service Enterprise Service Bus Low-level services Standard Legacy Database (Basic services) Applications Applications Network Storage ... Complexity 8 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  9. 9. Project background ✔ Project enfolded 50 high-level-services (BPEL) ➢ Orchestrate several low-level-services to new functionalities ➢ Make use of a consistent data model ✔ Design-team consists of 20 designers ✔ Development-team consists of 30 developers ✔ ca. 20 back-ends involved ✔ Currently six front-ends which were connected via message bus 9 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  10. 10. Project goal ✔ Consolidation of: ➢ Different integration solutions (with redundant business logic) ➢ Front-ends/ portals ✔ Standardization of the IT-infrastructure due to consolidation of divisions ✔ Lower costs for operation, maintenance and development 10 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  11. 11. The world that was! Frontend 2 Frontend 1 Frontend 3 EAI EAI EAI Adapter Adapter Adapter SCM Adapter CRM ERP SFA Company 11 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  12. 12. The world that was! Frontend 1 Frontend 2 Frontend 3 XML EAI Adapter Adapter Adapter SCM Adapter CRM ERP SFA Unternehmen 12 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  13. 13. Goals of the service-design ✔ Separation between design(functional) and development(technical) ✔ Design of business object model (BOM)-aligned services ✔ Design of SOA-compliant services using BPEL ✔ Compliance with design and architecture guidelines ✔ Increase the degree of automation of business processes 13 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  14. 14. Approach ✔ Definition of requirements ✔ Initial design ✔ Detailed design ✔ Test of the BPEL process ✔ Integration test Analyze initial design Check that all Analyze requirements Check technicalCheck that coding Consolidate all ✔ Going live check feasibility systems And feasibility Is correct requirements work together definition of initial detailed BPEL integration development requirements design design test test 14 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  15. 15. Distributed Knowledge operating departments (requestor) functional requests (new actions, products etc.) process-team (initial design) Complete process flow (affected front-ends and back-ends) technical design (detailed design) Detailed service knowledge (service activities, functional specifics) development Implementation details (BPEL, XSLT, XQuery etc.) 15 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  16. 16. Requirements & Changes Requirement's ✔ have to be send to the “requirement-input-channel“ ✔ are defined in solution-documents or change-requests ✔ have to be evaluated and approved by the “requirement-input-channel” The process-team ✔ analyses the requirements and identifies services and frond-ends to be changed ✔ defines changes for each service and front-end on a coarse level. It is responsible that all changes are consistent. ✔ leads the coordination with the requestor ✔ During the tests all requirements have to be tested successful ✔ Changes can be driven by design i.e. if the designer identifies faults or bugs 16 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  17. 17. Objectives of the service designer ✔ Creation of the technical design ➢ Analyze new requirements ➢ Create service documentation ➢ Create UML activity diagrams ➢ Create UML object diagrams ➢ Create functional mappings ✔ Accountable for 2-3 services ✔ Detailed functional know-how needed ✔ Technical know-how (BPEL and XML-technique's) not necessary but beneficial ✔ Functional support for development ✔ Functional support for test and production ✔ Coordination with the back-ends 17 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  18. 18. Service-design using Innovator ✔ Model driven Development (MDD) Innovator Artifacts XSD / WSDL SOM Activity-diagram Service documentation 18 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  19. 19. Example: service object-model (SOM) 19 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  20. 20. Example: service activity diagram 20 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  21. 21. Example: Functional mapping 21 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  22. 22. Tools used ✔ MID Innovator – used to create activity and object diagram's ✔ Altova XML Spy – customizing XSD's, generation of sample XML's ✔ MS Excel – template and macro supported creation of functional mappings ✔ MS Word – documentation 22 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  23. 23. Core questions for service design ✔ Which problem should be solved by this service? ✔ Which data is required to solve this problem? ✔ What pre-conditions must be fulfilled? ✔ What post-conditions must be fulfilled? ✔ Which faults can happen in the activity flow? ✔ What restrictions should the back-end services have? ✔ Who should use this service? ✔ On changes: ➢ Are there dependencies to the customer? ➢ Which other services are affected by these changes? According to the design guidelines there should be more questions concerning communications patterns, service category, protocols etc. 23 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  24. 24. Objectives of the developer ✔ Technical implementation of the functional design ✔ Needs technical know-how ➢ BPEL ➢ XML (XQuery, XSLT, XPath etc.) ✔ Bug-fixing, technical ticket analysis 24 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  25. 25. Business Object Modell Definition from wikipedia: „Within Business Process Management all business objects, their attributes and their relations are defined in the business-object model (BOM).“ ✔ Described as object-model (UML), entity-relationship-diagrams (ER- diagrams) or XSD-Schema's ✔ Sometimes functional behavior is defined also (class-diagrams (UML)) 25 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  26. 26. BOM example (UML) ✔ BOM definition of a address type 26 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  27. 27. Pro and contra BOM ✔ Pro ➢ Consistent naming conventions, attributes and relation for used business objects ➢ Time advantages for analysis and specification due to a predefined „construction set“ ➢ Possibility for semi-automated specification of services ✔ Contra ➢ “Pad out” the interface due to unnecessary attributes ➢ Not all needed attributes are defined in the BOM ➢ Difficulty to map BOM-conform interfaces to BOM-non-compliant interfaces ➢ In case of tool-support: Possibility that the tool restricts the design 27 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  28. 28. Service versioning ✔ Version changes ➢ Changes with consumer dependency => major version change ➢ Changes with no consumer dependency => minor version change ✔ Different artifact subject to version ➢ Service documentation ➢ Schema's, WSDL ➢ BPEL Processes ✔ Name-space includes version ➢ http://checkCustomer_v01.brockhaus-gruppe.de 01.00 Major Minor 28 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  29. 29. Governance Aspects ✔ Which services in which version are active which services have to be retired ✔ Which back-end services are used in which version ✔ Which consumer uses which service and which version is used ✔ Define versioning concepts etc. ✔ Delivery of services (descriptions, WSDL and XSD files) ✔ Receiving/review of back-end services ✔ Define delivery processes ✔ SOA Governance only on a very low level and not in a big strategy 29 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt
  30. 30. Thank you for your attention! Questions? 30 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt

×