Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
Big Data in Production Environments
Next
Download to read offline and view in fullscreen.

1

Share

BRO 110: Reference Architecture

Download to read offline

Presentation related to Reference Architectures in Software Engineering; part of the lectures held at Duale Hochschule Mannheim

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

BRO 110: Reference Architecture

  1. 1. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 1 Session: Reference Architectures Reference Architectures Open Group Reference Architecture
  2. 2. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 2 Welcome in An investment in knowledge always pays the best interest --- Benjamin Franklin
  3. 3. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 3 Objectives ✔ Get a general idea about : ➢ What a Reference Architecture might be good for ➢ An example of a Reference Architecture
  4. 4. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 4 Module Reference Architecture(s)
  5. 5. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 5 It's getting harder In all domains one can identify two simultaneous trends: ✔ Increasing complexity, scope and size of the system of interest, its context and the organizations creating the system ✔ Increasing dynamics and integration: shorter time to market, more interoperability, rapid changes and adaptations in the field.
  6. 6. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 6 Reference Architecture Is there a consistent notion of what this actually is: ✔ What is a Reference Architecture? ✔ Why do we need Reference Architectures? ➢ what is their value, ➢ what is the benefit of creating and maintaining them? ✔ How do you capture a Reference architecture? ➢ how do you visualize it, ➢ what is the appropriate level of abstraction, ➢ how is it used?
  7. 7. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 7 Reference Architecture What is it about? ✔ captures the essence of the architecture of a collection of systems. ✔ provides guidance for the development of architectures for new versions of the system or extended systems and product families. ✔ is created by capturing the essentials of existing architectures and by taking into account future needs and opportunities, ranging from specific technologies, to patterns to business models and market segments. A resource containing a consistent set of architectural best practices for use by all the teams in your organization. --- IBM, developerWorks
  8. 8. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 8 Business Architecture More than a technical view Customer Context Technical Architecture Design PatternsEnterprise Users Business Models Design Patterns Requirements
  9. 9. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 9 How to ... Reference Architecture: ✔ Is based on proven concepts. ✔ Is more than just technologies and patterns ✔ Most often preceding architectures are mined for these proven concepts. ✔ For architecture renovation and innovation validation and proof can be based on reference implementations and prototyping. But: ✔ Reference Architectures are often associated with big and inflexible frameworks Gerrit Muller
  10. 10. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 10 How to ... Existing architectures Architecture Patterns Customer & Business needs Further requirements Reference Architecture mining proven concepts vision analysis evolution triggering
  11. 11. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 11 Who? ✔ The Chief Architect (Business + Technical) owns the Reference Architecture. Ownership is a critical success factor for a Reference Architecture. ✔ Sponsorship of business managers for Reference Architectures is a prerequisite. Such sponsorship works only if the Reference Architecture provides value for the business. ✔ Reference Architectures are often related to organization structures. This relationship between organization and architecture is already a heated subject of discussion for actual architectures: ➢ Should the architecture follow the organization structure, or vice versa? ➢ Should we compromise architectural integrity to align better with the organization? ➢ Or should we adapt the organization to serve the desired architecture?
  12. 12. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 12 Reference Architecture Criteria for good Reference Architecture ✔ understandable for broad set of stakeholders ✔ accessible and actually read / seen by majority of the organization ✔ addresses the key issues of the specific domain ✔ satisfactory quality ✔ acceptable ✔ up-to-date and maintainable ✔ adds value to the business
  13. 13. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 13 Module „It is not the strongest of the species that survive or the most intelligent, but the ones most responsive to change“ --- Carles Darwin Open Group Reference Architecture
  14. 14. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 14 The Open Group ✔ Vendor- and technology-neutral consortium ✔ Vision to enable access to integrated information within and between enterprises based on open standards and global interoperability. ✔ Members: Almost all majors including ➢ Capgemini (Netherlands) ➢ Hewlett-Packard (USA) ➢ IBM (USA) ➢ SAP (Germany) ➢ Sun Microsystems (USA) ➢ ...
  15. 15. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 15 Ups, so what is this?
  16. 16. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 16 So, what do we have here Nine layers representing nine key clusters of considerations and responsibilities that typically emerge in the process of designing an solution or defining an enterprise architecture standard. ✔ Three of the layers address the implementation and interface with a service (the Operational Systems Layer, the Service Component Layer, and the Services Layer). ✔ Three layers support the consumption of services (the Business Process Layer, the Consumer Layer, and the Integration Layer). ✔ Four layers support cross-cutting concerns of a more supporting (sometimes called non-functional or supplemental) nature (the Information Layer, the Quality of Service Layer, the Integration Layer, and the Governance Layer).
  17. 17. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 17 Typical interaction between the layers Consumer Consumer Layer Integration Layer Business Process Layer Services Layer Component Layer OS Layer
  18. 18. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 18 OS Layer Capabilities: ✔ Service Delivery: This category of capabilities is required for delivery of the functional elements including the finding of the components implementing the services, the wrapping and the composition/ decomposition of the underlying services, and the implementation of the services. ✔ Runtime Environment: This category of capabilities is required for providing a runtime environment representing runtime infrastructure ✔ Virtualization and Infrastructure Services: This category of capabilities provides underlying infrastructure such as computing power, network, storage, etc. in native or a virtualized manner.
  19. 19. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 19 Component layer ✔ This layer contains software components, each of which provides the implementation or ―realization for services and their operations ✔ The layer also contains the functional and technical components that facilitate a service component to realize one or more services. ✔ Each service component fulfils the following goals: ➢ Realizes one or more services ➢ Provides an enforcement point for service realization ➢ Enables IT flexibility by strengthening the decoupling in the system, by hiding volatile implementation details from service consumers
  20. 20. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 20 Component layer Package X Application Y Service Component A Application B XML via http Layer #1Layer #2
  21. 21. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 21 Services layer ✔ The Services Layer contains software components, each of which provides the implementation or ―realization for services and their operations. ✔ The layer also contains the functional and technical components that facilitate a service component to realize one or more services ✔ Services can be discovered and invoked, or possibly choreographed to create a composite service. ✔ Services are functions that are accessible across a network via well-defined interfaces of the Services Layer.
  22. 22. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 22 Business Process Layer Business processes are realized as compositions (orchestrations, choreographies) of elements on services layer ✔ process representation and composition ✔ building blocks for aggregating loosely-coupled services as a sequencing process aligned with business goals. ✔ enable interactions between services and business processes. ✔ within an enterprise or across multiple enterprises.
  23. 23. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 23 Consumer Layer Provides capabilities to deliver required functionality and data to service consumers ✔ Service consumers may be human users and applications ✔ Users may have preferences on how to interact with functionality provided ➢ Portals ➢ Rich Internet Applications, RIA ➢ Interactive Voice Response, IVR ➢ API
  24. 24. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 24 Integration Layer Realizes „communication infrastructure“ between service requester/consumer and service provider ✔ Between service requester and provider requests must be ➢ mediated ➢ transformed ➢ routed, and ➢ transported ✔ Business rules are made available consistently through all layers („cross-cutting architectural concern“) ✔ Centralization of management of business rules in this layer prevents divergence or loss of consistent rules
  25. 25. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 25 What we will focus on ... Consumer Consumer Layer Integration Layer Business Process Layer Services Layer Component Layer OS Layer
  26. 26. Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 26 Review Session Review: ✔ What is the purpose of a reference architecture? ✔ What is key to success for a reference architecture? ✔ Can you name some of the layers of the SOA reference architecture?
  27. 27. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 1 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 1 Session: Reference Architectures Reference Architectures Open Group Reference Architecture
  28. 28. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 2 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 2 Welcome in An investment in knowledge always pays the best interest --- Benjamin Franklin
  29. 29. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 3 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 3 Objectives ✔ Get a general idea about : ➢ What a Reference Architecture might be good for ➢ An example of a Reference Architecture
  30. 30. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 4 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 4 Module Reference Architecture(s)
  31. 31. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 5 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 5 It's getting harder In all domains one can identify two simultaneous trends: ✔ Increasing complexity, scope and size of the system of interest, its context and the organizations creating the system ✔ Increasing dynamics and integration: shorter time to market, more interoperability, rapid changes and adaptations in the field.
  32. 32. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 6 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 6 Reference Architecture Is there a consistent notion of what this actually is: ✔ What is a Reference Architecture? ✔ Why do we need Reference Architectures? ➢ what is their value, ➢ what is the benefit of creating and maintaining them? ✔ How do you capture a Reference architecture? ➢ how do you visualize it, ➢ what is the appropriate level of abstraction, ➢ how is it used?
  33. 33. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 7 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 7 Reference Architecture What is it about? ✔ captures the essence of the architecture of a collection of systems. ✔ provides guidance for the development of architectures for new versions of the system or extended systems and product families. ✔ is created by capturing the essentials of existing architectures and by taking into account future needs and opportunities, ranging from specific technologies, to patterns to business models and market segments. A resource containing a consistent set of architectural best practices for use by all the teams in your organization. --- IBM, developerWorks
  34. 34. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 8 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 8 Business Architecture More than a technical view Customer Context Technical Architecture Design PatternsEnterprise Users Business Models Design Patterns Requirements
  35. 35. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 9 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 9 How to ... Reference Architecture: ✔ Is based on proven concepts. ✔ Is more than just technologies and patterns ✔ Most often preceding architectures are mined for these proven concepts. ✔ For architecture renovation and innovation validation and proof can be based on reference implementations and prototyping. But: ✔ Reference Architectures are often associated with big and inflexible frameworks Gerrit Muller
  36. 36. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 10 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 10 How to ... Existing architectures Architecture Patterns Customer & Business needs Further requirements Reference Architecture mining proven concepts vision analysis evolution triggering
  37. 37. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 11 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 11 Who? ✔ The Chief Architect (Business + Technical) owns the Reference Architecture. Ownership is a critical success factor for a Reference Architecture. ✔ Sponsorship of business managers for Reference Architectures is a prerequisite. Such sponsorship works only if the Reference Architecture provides value for the business. ✔ Reference Architectures are often related to organization structures. This relationship between organization and architecture is already a heated subject of discussion for actual architectures: ➢ Should the architecture follow the organization structure, or vice versa? ➢ Should we compromise architectural integrity to align better with the organization? ➢ Or should we adapt the organization to serve the desired architecture?
  38. 38. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 12 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 12 Reference Architecture Criteria for good Reference Architecture ✔ understandable for broad set of stakeholders ✔ accessible and actually read / seen by majority of the organization ✔ addresses the key issues of the specific domain ✔ satisfactory quality ✔ acceptable ✔ up-to-date and maintainable ✔ adds value to the business
  39. 39. Java EE 5 Workshop - Brockhaus GmbH © 2009 - 13 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 13 Module „It is not the strongest of the species that survive or the most intelligent, but the ones most responsive to change“ --- Carles Darwin Open Group Reference Architecture
  40. 40. Java EE 5 Workshop - Brockhaus GmbH © 2009 - 14 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 14 The Open Group ✔ Vendor- and technology-neutral consortium ✔ Vision to enable access to integrated information within and between enterprises based on open standards and global interoperability. ✔ Members: Almost all majors including ➢ Capgemini (Netherlands) ➢ Hewlett-Packard (USA) ➢ IBM (USA) ➢ SAP (Germany) ➢ Sun Microsystems (USA) ➢ ...
  41. 41. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 15 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 15 Ups, so what is this?
  42. 42. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 16 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 16 So, what do we have here Nine layers representing nine key clusters of considerations and responsibilities that typically emerge in the process of designing an solution or defining an enterprise architecture standard. ✔ Three of the layers address the implementation and interface with a service (the Operational Systems Layer, the Service Component Layer, and the Services Layer). ✔ Three layers support the consumption of services (the Business Process Layer, the Consumer Layer, and the Integration Layer). ✔ Four layers support cross-cutting concerns of a more supporting (sometimes called non-functional or supplemental) nature (the Information Layer, the Quality of Service Layer, the Integration Layer, and the Governance Layer).
  43. 43. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 17 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 17 Typical interaction between the layers Consumer Consumer Layer Integration Layer Business Process Layer Services Layer Component Layer OS Layer
  44. 44. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 18 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 18 OS Layer Capabilities: ✔ Service Delivery: This category of capabilities is required for delivery of the functional elements including the finding of the components implementing the services, the wrapping and the composition/ decomposition of the underlying services, and the implementation of the services. ✔ Runtime Environment: This category of capabilities is required for providing a runtime environment representing runtime infrastructure ✔ Virtualization and Infrastructure Services: This category of capabilities provides underlying infrastructure such as computing power, network, storage, etc. in native or a virtualized manner.
  45. 45. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 19 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 19 Component layer ✔ This layer contains software components, each of which provides the implementation or ―realization for services and their operations ✔ The layer also contains the functional and technical components that facilitate a service component to realize one or more services. ✔ Each service component fulfils the following goals: ➢ Realizes one or more services ➢ Provides an enforcement point for service realization ➢ Enables IT flexibility by strengthening the decoupling in the system, by hiding volatile implementation details from service consumers
  46. 46. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 20 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 20 Component layer Package X Application Y Service Component A Application B XML via http Layer #1Layer #2
  47. 47. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 21 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 21 Services layer ✔ The Services Layer contains software components, each of which provides the implementation or ―realization for services and their operations. ✔ The layer also contains the functional and technical components that facilitate a service component to realize one or more services ✔ Services can be discovered and invoked, or possibly choreographed to create a composite service. ✔ Services are functions that are accessible across a network via well-defined interfaces of the Services Layer.
  48. 48. Java EE 5 Workshop - Brockhaus GmbH © 2009 - 22 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 22 Business Process Layer Business processes are realized as compositions (orchestrations, choreographies) of elements on services layer ✔ process representation and composition ✔ building blocks for aggregating loosely-coupled services as a sequencing process aligned with business goals. ✔ enable interactions between services and business processes. ✔ within an enterprise or across multiple enterprises.
  49. 49. Java EE 5 Workshop - Brockhaus GmbH © 2009 - 23 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 23 Consumer Layer Provides capabilities to deliver required functionality and data to service consumers ✔ Service consumers may be human users and applications ✔ Users may have preferences on how to interact with functionality provided ➢ Portals ➢ Rich Internet Applications, RIA ➢ Interactive Voice Response, IVR ➢ API
  50. 50. Java EE 5 Workshop - Brockhaus GmbH © 2009 - 24 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 24 Integration Layer Realizes „communication infrastructure“ between service requester/consumer and service provider ✔ Between service requester and provider requests must be ➢ mediated ➢ transformed ➢ routed, and ➢ transported ✔ Business rules are made available consistently through all layers („cross-cutting architectural concern“) ✔ Centralization of management of business rules in this layer prevents divergence or loss of consistent rules
  51. 51. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 25 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 25 What we will focus on ... Consumer Consumer Layer Integration Layer Business Process Layer Services Layer Component Layer OS Layer
  52. 52. Copyright by Brockhaus AG - Brockhaus GmbH © 2009 - 26 Copyright by Brockhaus GmbH, alle Rechte reserviert, unautorisierte Vervielfältigung untersagt 26 Review Session Review: ✔ What is the purpose of a reference architecture? ✔ What is key to success for a reference architecture? ✔ Can you name some of the layers of the SOA reference architecture?
  • Gudimetla

    Mar. 28, 2018

Presentation related to Reference Architectures in Software Engineering; part of the lectures held at Duale Hochschule Mannheim

Views

Total views

699

On Slideshare

0

From embeds

0

Number of embeds

71

Actions

Downloads

32

Shares

0

Comments

0

Likes

1

×