34. Platform Independent Model BPE Gateway BRE Usage Business Services (ESB) Process Store Rule Base Auth System Application Workers, Business Managers, Business Architects Templates Templates Development Tools Admin BRE
35.
36. Interoperability Maturity Components Services Business Processes Business Rules Simplify business process flows Dynamic business processes Flow oriented around operating business processes Degree of freedom between function and coordination flow achieved Flow, rule, and function intertwined and not exposed
37. SOA Development Process Capture Business Process Analyze Business Process Interaction Development Design, Assemble Process Identify Necessary Services Deploy Process Implement Custom Services Design Services Deploy Services Execute Business Process Continuous Verification Change & Configuration Mgt Expose Legacy Services Identify Legacy System Acquire Services ~~~~~~~~~~~~~~WBM~~ ~~~~~~~~~~~~~~WID~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~RSA(RAD)~~ Business Activity Management (BAM) Business Process Definition
38. Integration Developer Business Modeler Software Architect Process Server Application Server Business Monitor Functional Tester Performance Tester Requisite Pro Publishing Server Method Composer Services Development Services Orchestration Services Definition SOA Guidance
57. Envisioned CBP BPC Cumulative Plan 2005 S1 2 2006 2007 2008 S1 S2 R4 M1 =2 =4 =9 =25 40 S1 S2 R4 M1 =2 =4 =9 =25 55 M2 # of Business Process Flows =15 All
58.
59.
60.
61.
62.
Notes de l'éditeur
This presentation provides a high-level overview of the motivations and technology behind service-oriented architecture.
What I would like you to know about SOA and why it is so very important.
Most companies of any size outsource portions of their business functions to qualified suppliers. Overall product and service quality depends on the aggregated qualities of all parties involved. The elimination of gaps, errors and omissions and just plain old inefficiencies in performing the operations of the business is becoming a vital success factor in the midst of increased competitiveness. Technologies exist today to monitor and measure business process performance, so that it can become improved and ultimately optimized. Many businesses are obliged to demonstrate regulatory compliance and business activity monitoring (BAM) can help greatly in this regard.
The operations and offerings of the business keep constantly changing, but IT systems can barely catch up. Many organizations keep on re-implementing the same old systems using new programming languages and technologies. This usually does not result in any degree of operational improvement, however. Developing new systems and capabilities takes time and can be risky to undertake. The competitive edge that any market opportunity may present may be lost while waiting for IT systems to be put in-place. Many have caught on to the fact that there is a rich vendor market for commercial, off-the-shelf software (COTS), that can solve some of the known challenges. How can we integrate COTS and still have control over our IT applications?
We need to blend lines of business with IT to get the value of both over time.
A service-oriented architecture defines interfaces as gateways to business IT capabilities. Services are abstractions of interfaces that unite service consumers with service providers. We have seen this before with other technologies, such as CORBA. CORBA was platform and language-neutral and continues to have great industry support. Many implementations of CORBA failed to realize its promised benefits. There have been lessons learned. As we will see, there are enabling technologies for SOA that when used properly, can be leveraged to produce successful outcomes.
Courtesy IBM
Courtesy IBM
Courtesy of BEA Systems Service-oriented Architecture government systems event held in May 2005.
Could be internal as well as external systems and sometimes both are selected as worthy projects to be implemented in parallel.
Key Tenets of Service-oriented Development of Applications (SODA) - Gartner
A graphical model depicting the layers and partitions of a platform-independent end-state architecture that makes SOA all happen.
This would be a great state for any enterprise to be in right now.
This topic is not only structural regarding technology, but also in terms of SOA maturity. We are presently at the component development level as an industry.
This is a very high-level and simple process that nicely ties everything together: services development and deployment, business process development and deployment, and business process execution. There are several IBM tools that constitute and integrated approach towards making this all happen. They are: WebSphere Business Modeler (WBM), WebSphere Integration Developer (WID), and Rational Software Modeler/Architect/Application Developer (RSA(RAD)). It is important to understand the role of each tool and how they all work as an ensemble to make services-oriented architectures realizable.
This ties together the use of many other IBM tools and also includes a high-level abstraction of the run-time processing elements that make services-oriented architecture happen. Most importantly, the Business Modeler and Integration Developer are very model-driven. All or most of the code is generated, and it has been hardened and tested over the years. Any custom application or component can also become model-driven using Software Architect. There are visual debuggers available that let you set breakpoints, inspect variables, and step-through your application. It is an opportunity to get out of the character and line-based practice of coding that has existed for a very long time. IBM has already provided knowledge that can be used on first SOA projects via the Rational Method Composer. This tool can be used to add more informative, enterprise, and project-specific knowledge needed to implement SOA across the enterprise. It is great since this knowledge is accessible from everyone’s desktop
A graphical model depicting the relevance and significance of modeling and designing services and business processes visually, then deploying, running, debugging, and measuring them. At some point, composite applications are assembled visually from suite of available services. The resulting application is deployed and tested, comes into operation, and business process results become analyzed. This really emphasizes the benefits of visual modeling.
A visual representation of a business process (WebSphere Business Modeler). I would like to emphasize that while we are looking at a very simple business process. Business process modeling consists of many pieces that come together to completely and succinctly provide its definition. 1. Business processes: business events, business results 2. Resources needed for activities: bulk resources, human resources, computing resources, etc. 3. Organizations: organization structure, roles for given human resources, resource availabilities/schedules, etc. 4. Physical locations 5. Business data When defined at sufficient levels, such business processes can be simulated and the results used to refine this model. There are many statistical functions that are available to define wait-times, durations, etc.
Capturing key performance indicators and situation events for a business process (WebSphere Business Modeler). Not only can key performance indicators be defined, but WBM enables the definition of business events that when placed in the run-time environment will become collected as business process actually execute.
A visual model of a designed business process (WebSphere Integration Developer). Business processes defined using the WPC can be directly imported into the WID. The WID generates the receive and send “framework” necessary to set-up the process for its implementation.
A visual model (Assembly Diagram) of services connected to business process (WebSphere Integration Developer). The assembly diagram is a great visualization, since it provides an abstraction between what needs to be done during the execution of a business process and the implementation resources that realize it. This screen capture shows the key abstractions that hold: the business process itself, some human-related tasks, an invocation of a web service to perform an activity, the evaluation of a business rule set, and some Java snippets. All of these resources are used to implement the business process.
The WID support the definition of rule templates that are subsequently used to define actual business rules. It is important to note that the rules can be defined by the business once templates are available.
The Rational Application Developer (RAD) product does in fact, support the definition, development, deployment, test, and documentation of web services.
This depicts one of the many dialogs that enable the fast development of web services (RAD).
It is important to note that there are visual editors to define web services. These will generate the WSDL XML for you. This allows service developers to focus on the service itself instead of low-level XML WSDL syntax.
A visual model of services interface [in WSDL] (Rational Software Architect).
Requirements traceability is achieved through the use of Requisite Pro integration with RSM/RSA. Access to any Requisite Pro project is available by opening the Requirements perspective in RSM/RSA.
This screen shot depicts the Requirements Browser, a UML deployment diagram, and the traceability between a UML element and requirements.
Implementation for service [in Java] (Rational Software Architect).
The Rational Method composer delivers SOA knowledge directly to everyone’s desktop. IBM has already encoded its lessons learned from implementing their own SOA initiatives into this product. Use RMC to create your own, relevant knowledge.