|
|
SOA and SOAD Case Studies
Features knowledge management strategy and reusable assets, architecture design work products in reference architetcure, reusable architetcural decision model, integration with other artifacts, user feedback, knowledge harvesting process, best practices.
The chapter presents an industrial case study for the creation and usage of architectural knowledge. To establish the context of our usage of architectural knowledge, the chapter introduces business domain, service portfolio, and knowledge management approach of the company involved in the case in a first section. This first section briefly reviews general architectural concepts such as viewpoints, methods, and reference architectures.
Next, the chapter introducs a Service-Oriented Architecture (SOA) infrastructure reference architecture as a primary carrier of architectural knowledge in this company. Moreover, the harvesting of architectural knowledge from industry projects is presented, as well as feedback from early reference architecture users.
 Find the book chapter online.
On January 23, 2008, Ildefons Magrans de Abril, the Technical Coordinator of the CMS Trigger Software project at CERN, Geneva, presented a SOA and Web services case study at the IBM Zurich Research Lab:
The experiments CMS (Compact Muon Solenoid) and ATLAS (A Toroidal LHC Apparatus) at the Large Hadron Collider (LHC) are the greatest
exponents of the rising complexity in High Energy Physics (HEP) data handling instrumentation. In this context, the design and
development of control systems is a major endeavor: Tens of millions of readout channels, tens of thousands of hardware boards
and the same order of connections are figures of merit. However the hardware volume is not the only complexity dimension,
the unprecedented large number of research institutes and scientists that form the international collaborations,
and the long design, development, commissioning and operational phases are additional factors that must be taken into account.
This talk discusses how web services based solutions helped to manage the unprecedented complexity to design and develop the
CMS online software infrastructure: The CMS distributed programming frameworks and a concrete control system are discussed in detail.
Download Ildefons' presentation here.
On this project, challenging requirements such as complexity of business process models and multi-channel accessibility turned out to be true proof points for the applied SOA concepts, tools, and runtime environments. To implement an automated and secured business-to-business Web services channel and to introduce a process choreography layer into a large existing application were two of the key requirements that had to be addressed. The solution complies with the Web Services Interoperability Basic Profile 1.0 and makes use of executable business process models defined in the Business Process Execution Language (BPEL).
This paper discusses the rationale behind the decision for SOA, process choreography, and Web services, and gives an overview of the BPEL-centric process choreography architecture. Furthermore, it features lessons learned and best practices identified during design, implementation, and rollout of the solution.
Download the OOPSLA 2005 practitioner report Service-Oriented Architecture and Business Process Choreography in an Order Management Scenario and find a BPM/SOA design lecture which features a generalized version of the solution here.
This report discusses the rationale behind the decision for Web services, and gives an architectural overview of the integration approach. Furthermore, it features the lessons learned and best practices identified during the design, implementation and rollout of the solution.
Download the OOPSLA 2004 practitioner report here.
A white paper co-authored by Olaf Zimmermann discussing a case study from the finance industry.
Download the paper here.
Research Papers on Software Service Engineering (SSE), Service-Oriented Analysis and Design, and Service Modeling
Abstract (PESOS): Service-Oriented Architecture (SOA) constitutes a modern, standards-based and technology-independent paradigm and architectural style for distributed enterprise computing. The SOA style promotes the publishing, discovery, and binding of loosely-coupled, network-accessible software services. With SOA systems operating in distributed and heterogeneous execution environments, the engineers of such systems are confined by the limits of traditional software engineering. In this position paper, we scrutinize the fundamental tenets underpinning the development and maintenance of SOA systems. In particular, we introduce software service engineering as an emerging discipline that entails a departure from traditional software engineering disciplines, embracing the open world assumption. We characterize software service engineering via seven defining tenets. Lastly, we survey related research challenges.
Click here for the PESOS paper on SSE and here for the Dagstuhl seminar summary.
We presented results from the SOA Decision Modeling (SOAD) project at conferences and workshops such as WICSA 2008, WWW 2008, ECOWS 2007, ICSOC 2007, QOSA 2007, and SEMSOA 2007. The ICSOC conference paper defines conceptual decisions and patterns for transactional workflows in SOA. The QOSA conference paper describes a decision capturing meta model, decision making steps, and the structure of the SOA design space (MDA layering).
The SEMSOA workshop paper, describes the active, guiding role of the decision model and the required model transformations.
Click here for more information on these papers.
On Service-Oriented Architecture (SOA) delivery projects, practitioners concern themselves with the characteristics of good services and how such services can be designed. For instance, they look for advice regarding interface granularity and criteria to assess whether existing software assets are fit for reuse in SOA environments. In this paper, we position architectural decision modeling as a prescriptive service realization technique. We propose a multidimensional SOA decision catalog, separating platform-independent from platform-specific concerns and supporting dependency management. The catalog is positioned in a three-stage model transformation chain for SOA.
SOAD-PositioningPaperv10.pdf
Reference as: Zimmermann O., Koehler J., Leymann F., The Role of Architectural Decisions in Model-Driven Service-Oriented Architecture Construction. In: Skar, L.A., Bjerkestrand A.A. (eds.), Best Practices and Methodologies in Service-Oriented Architectures (OOPSLA 2006 Workshop), Unipub (2006)
Service-Oriented Architectures (SOAs) have been established as an IT strategy to support the on demand goal of business agility. Web services standards and their implementations are key enablement technologies for SOA which are maturing rapidly. There is a growing body of successful implementations of these technologies. However, experience of solving the wider business and architectural issues involved in designing a high-quality SOA for a particular enterprise still stands at an early stage. In this paper, we motivate the need for service modeling methodologies as means of tackling the external design of a business-focused SOA, identify some of the available candidate assets, and discuss how existing artefacts such as UML analysis diagrams can be leveraged for service modeling.
INF05-ServiceModelingv11.pdf
Published in Lecture Notes für Informatik 2005,
INFORMATIK 2005 - Informatik LIVE! Band 2, Beitraege der 35. Jahrestagung der Gesellschaft für Informatik e.V. (GI), Bonn, 19. bis 22. September 2005 (ISBN: 3-88579-396-2),
© Gesellschaft für Informatik, 2005
Original SOAD Article on IBM developerWorks
http://www-128.ibm.com/developerworks/webservices/library/ws-soad1/
Other Articles
http://www-128.ibm.com/developerworks/webservices/library/ws-roles/
|
|
|
