Beyond eBusiness Chapter 7 Architecture Aspect Table of

Beyond e-Business Chapter 7: Architecture Aspect

Table of contents • • Introduction running case Types of architectures studies: Market-level architectures Party-level architectures POSH, TTU System-level architectures Tra. XP The service-oriented view Mapping O elements to A elements Conclusions Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 2

Architecture Aspect Introduction Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect -

Architecture aspect in BOAT Tech Bus Arch Org Beyond e-Business © 2015 Paul Grefen

Concept of architecture An architecture is the blueprint of the structure of a complex system. The architecture of an (networked e-business) information system specifies the structure of that system in terms of functional software components supporting specific functions and interfaces supporting the interactions among those components. Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 5

The need for architecture functionality quality Beyond e-Business © 2015 Paul Grefen demand pull

Architecture as a pivot between B&O and T aspects B&O A T Beyond e-Business

Architecture Aspect Types of architectures Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture

Aggregation levels of architectures (1) • To deal with complexity, we use multiple levels of architectures: – Market-level architecture: IS structure of an entire scenario, focusing on collaboration – Party-level architecture: overall IS structure of a single party in a senario – System-level architecture: structure of a single IS of a party in a scenario • Levels have an aggregation (part-of) relationship: one refines the other Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 9

Aggregation levels of architectures (2) Party-level Architecture System-level Architecture Beyond e-Business © 2015 Paul Grefen Party-level Architecture Aggregation Refinement Market-level Architecture System-level Architecture Chapter 7: Architecture Aspect - 10

Abstraction levels of architecture (1) • To deal with reuse, we use multiple levels of architectures: – Reference architecture: IS structure (blueprint) to be reused across multiple organizations – Standard architecture: IS structure (blueprint) to be reused within one organization – Instance architecture: IS structure for one IS of an organization • Levels have an abstraction relationship: one is a concretization of the other Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 11

Abstraction levels of architecture (2) Abstraction Reference Architecture Standard Architecture Instance Architecture Beyond e-Business © 2015 Paul Grefen valid across organizations valid within organizations Chapter 7: Architecture Aspect - 12

Aggregation and abstraction A 2 A 1 aggregation Beyond e-Business © 2015 Paul Grefen

Architecture Aspect Market-level architectures Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect

Market-level architecture • Market-level architecture describes – main IS modules of parties in scenario • Highly aggregated with each party as black box • More detailed with front-end modules of parties – connections between these modules • Focus on the inter-organizational connections • Labeled connections to indicate message sets – without reference to specific technology • Can exist as reference (e. g. in a business domain), standard or instance architecture Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 15

Highly aggregated abstract market-level architecture m 2 m 3 m 4 m 5 Beyond

Detailed abstract market-level architecture BES A FES A 1 m 1 FES B 1 FES A 2 m 2 FES B 2 FES A 3 m 3 FES B 3 m 4 FES A 5 BES B m 5 FES I 1 FES I 2 FES I 3 m 6 FES B 4 BES I Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 17

Multi-party abstract market-level architecture BES A FES A 1 m 1 FES B 5 m 7 FES C 1 FES A 2 m 2 FES B 6 m 8 FES C 2 FES A 3 m 3 FES B 3 BES B BES C FES A 4 FES B 4 FES A 5 m 5 FES I 1 m 4 FES I 2 BES I Beyond e-Business © 2015 Paul Grefen m 6 FES I 3 FES B 7 FES C 4 m 10 m 9 FES J 1 FES J 2 BES J Chapter 7: Architecture Aspect - 18

Broker System m 2 m 3 m 4 Payment Handling m 5 m 6 Goods Rcv. Advertising m 7 Order Mngt. Prov. Serv. Logistics Mngmnt m 9 Goods Dispatching m 8 Goods Handl. POSH Back End Systems Procurement Customer Back End Systems POSH scenario market-level architecture Beyond e-Business © 2015 Paul Grefen m 10 Order Entry Manufact. Back End Chapter 7: Architecture Aspect - 19

POSH scenario message sets Message Set m 1 m 2 m 3 m 4 m 5 m 6 m 7 m 8 m 9 m 10 Contents Exchanged Provider search request, Provider search result Provider profile, Provider offer Order, Order confirmation Payment order Payment notification Service request, Service information Delivery notification, Delivery confirmation Shipment request, Shipment confirmation Production order, Production confirmation Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 20

Broker System m 2 m 3 m 4 Advertising Order Entry Payment Handling m 5 Billing Mail Handl. m 6 TConf. Client m 7 TConf. Support m 8 TConf. Client VConf. Client m 9 VConf. Support m 10 VConf. Client Doc. Handl. TTU Back End Systems Procurement Customer Back End Systems TTU scenario market-level architecture Beyond e-Business © 2015 Paul Grefen m 1 Chapter 7: Architecture Aspect - 21

Architecture Aspect Party-level architectures Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect

Party-level architecture • Party-level architecture describes – main IS modules of one party in scenario • Front-end and back-end systems • Databases containing EB data – connections between modules – connections to other parties (context) – without reference to specific technology • Can exist as reference, standard (e. g. , standard within a distributed organization) or instance architecture Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 23

Abstract party-level architecture DB A 1 BES A 1 m. A 6 BES A 2 Beyond e-Business © 2015 Paul Grefen BES A 3 m 1 m. A 2 FES A 2 m. A 3 FES A 3 m. A 4 FES A 4 m. A 5 FES A 5 m 5 Party I DB A 3 DB MS A 2 FES A 1 Party B DB A 2 DB MS A 1 m. A 1 Chapter 7: Architecture Aspect - 24

Party-level vs. enterprise architecture Party-level Architecture 1 Party-level Architecture 3 Party-level Architecture 2 Enterprise Architecture Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 25

Broker Serv. Adm. DBMS A ERP System Advertising Logist. Beyond e-Business © 2015 Paul Grefen Goods Handl. Manuf. Advert. Data Order Mngt. Paym. ERP DB Prov. Serv. Cust. Serv. Data DBMS B POSH party-level architecture Chapter 7: Architecture Aspect - 26

Cloud-based ERP solution for POSH Broker Logist. Advertising Manuf. ERP Service Order Mngt. Goods Handl. Advert. Data Beyond e-Business © 2015 Paul Grefen Prov. Serv. Paym. Serv. Data Serv. Adm. Cust. DBMS Chapter 7: Architecture Aspect - 27

POSH enterprise architecture overview Party-level Architecture Procurement Party-level Architecture Finance Party-level Architecture Sales Party-level Architecture HRM Enterprise Architecture Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 28

Architecture Aspect System-level architectures Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect

System-level architecture • System-level architecture describes – modules of one front-end or back-end system of one party • Software system modules • Intra-system databases containing EB data – connections between modules – connections to other systems/parties (context) – without reference to specific technology • Can exist as reference, standard or instance architecture Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 30

m. A. BES_A 1. 3 BES A 1. 1 m. A 1 BES A 1. 2 m. A 2 FES A 2 BES A 1. 4 m. A. BES_A 1. 1 FES A 1 DBMS A 1 Abstract system-level architecture BES A 1. 3 m. A. BES_A 1. 2 m. A 6 BES A 2 Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 31

POSH system-level architecture Catalog Order Handling Shopping Cart Beyond e-Business © 2015 Paul Grefen

Architecture Aspect The service-oriented view Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture

Service-oriented party-level architecture Party I Party B m 1 FES A 1 m 2 FES A 2 m 3 FES A 3 m 4 FES A 4 m 5 FES A 5 Enterprise Service Bus BES A 1 Beyond e-Business © 2015 Paul Grefen BES A 2 BES A 3 DB MS A 1 DB MS A 2 Chapter 7: Architecture Aspect - 34

Service-oriented architecture and cloud computing Party I Party B m 1 FES A 1 m 2 FES A 2 m 3 FES A 3 m 4 FES A 4 m 5 FES A 5 Enterprise Service Bus BES A 1 BES A 2 Beyond e-Business © 2015 Paul Grefen BES A 3 DB MS A 1 DB MS A 2 Chapter 7: Architecture Aspect - 35

Partner Back End Systems Tra. XP market-level architecture Contract Mngmnt Registrat. Profiling Order Entry Ordering Order Entry Traveler Browser Event Handling Travel Commun. Traveler Commun. Contract Mngmnt Enterprise Service Bus Tra. XP Back End Systems Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 36

Network view of Tra. XP market-level arch. Travel Planner BES Travel Planner FES Hotel Booker BES Hotel Booker FES Airline Booker BES Airline Booker FES Rail & Bus Bkr BES Rail & Bus Bkr FES Rental Car Prv BES Rental Car Prv FES Insuran Prv BES Insuran Prv FES Social Med Prv BES Social Med Prv FES Beyond e-Business © 2015 Paul Grefen Tra. XP Front End Systems Traveler FES Enterprise Service Bus Tra. XP Back End Systems Chapter 7: Architecture Aspect - 37

Tra. XP party-level architecture Traveler Partner Contract Mngmnt Ordering Event Handling Registrat. Profiling Order Entry Travel Commun. Beyond e-Business © 2015 Paul Grefen Trip Mngmnt CRM Bus Process Mngmnt Data Mngmnt Business Intelligence Partner Mngmnt Enterprise Service Bus Chapter 7: Architecture Aspect - 38

Architecture Aspect Mapping O elements to A elements Beyond e-Business © 2015 Paul Grefen

Mapping O aspect elements to A aspect elements Tech Bus Arch Org Beyond e-Business

O-A mapping principles • Form is function principle: – structure of an architecture should follow the business functionality it is designed for • Well-chosen isomorphism between O-aspect and Aaspect structures • Modular design principle: – architecture should consist of well-designed modules • Facilitates extension and replacement • Facilitates use of common-of-the-shelve (COTS) components Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 41

O aspect vs. A aspect structure FES A 2 AF 3 AF 2 AF

O to A aspect mapping matrix O Aspect Modules AF 1 FES A 1

Architecture Aspect Conclusions Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect -

Conclusions • Architectures are pivots between businessoriented design and technology-oriented design of e-business scenarios. • Architectures can be positioned along aggregation dimension and abstraction dimensions – The position along aggregation dimension determines the ‘granularity’ of the architecture. – The position along the abstraction dimension determines the concreteness of the architecture. Beyond e-Business © 2015 Paul Grefen Chapter 7: Architecture Aspect - 45