2. A reference architecture for business information systems Reference Architectures and Patterns

Größe: px

Ab Seite anzeigen:

Download "2. A reference architecture for business information systems Reference Architectures and Patterns"

Katharina Schenck
vor 8 Jahren
Abrufe

1 2. A reference architecture for business information systems Reference Architectures and Patterns Winter Semester 2008 / 2009 Prof. Dr. Bernhard Humm Darmstadt University of Applied Sciences Department of Computer Science 1 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Bernhard Humm Darmstadt University of Applied Sciences Department of Computer

2 The lecture in the context of the entire course 1. Introduction 2. A reference architecture for business information systems 3. Application kernel facade 4. Persistence and transaction 5. Authorization 6. Client architecture 7. Other reference architectures: SOA, BI, systems integration, 2 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Persistence and transaction 5. Authorization 6. Client architecture 7.

3 Agenda Architectural Viewpoints Software Categories Components and Interfaces Reference Architecture for Business Information Systems Literature

4 Architectural viewpoints Architecture viewpoints separate concerns of different stakeholders A Architecture (Application Logic Architecture) Structure of an application from the business point of view Independent of techical issues Different for every application Application entitites like Customer, Account, etc. T Architecture (Technical Architecture) Glue between A an TI architecture Specifies the virtual machine on which the A archictecture will be executed TI Architecture (Technical Infrastructure) Hardware (computers, networks, etc.) and systems software (operating systems, application servers, database servers, etc.) and programming languages used 4 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

T Architecture (Technical Architecture) Glue between A an TI architecture Specifies the virtual machine on which the A archictecture will be executed TI Architecture (Technical

5 Architectural viewpoints Example project in the domain of logistics Customer: large international logistics provider Project: order management Volume Release 1: > 30 person years Time: April, 2003 January, 2004 Release 2 already implemented: similar volume and time span 5 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

years Time: April, 2003 January, 2004 Release 2 already implemented: similar volume and

6 Architectural viewpoints Example A Architecture (business application architecture) Master Applikation Informationsanforderung Benutzerverwaltung Frontend Internes Informationsservice und Clearing Portal Informationsservice und Clearing Benutzerverwaltung Stammdatenverwaltung Clients ESI-Frontend Benutzerverwaltung Stammdatenverwaltung SA- Frontend SA- Batch- Scanner SA- Online- Scanner NVE- Drucker NVE- Drucker NVE- Drucker Backend Auftragsverwaltung Produktionsauftragsverwaltung Annahme/Importer Auftragsüberwachung ESi-Backend SA-Backend Konvertierung Auftragsverwalter Disposition Auftragsabrechnung Auftragsüberwachung Disposition T&T-Verwaltung Nummerverwaltung Inform.service u. Clearing Auftragsverwalter Stammdatenverwaltung Informationsservice und Clearing Nummernverwaltung Stammdatenverwaltung Auftragsverwaltung Produktion Entgeltsicherung Tracking & Tracing Querschnitt Benutzerverwaltung 6 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Drucker NVE- Drucker NVE- Drucker Backend Auftragsverwaltung Produktionsauftragsverwaltung Annahme/Importer Auftragsüberwachung ESi-Backend SA-Backend Konvertierung Auftragsverwalter Disposition

7 Architectural viewpoints Example TI architecture (technical infrastructure) Aktive Netzkomponente (redundant) Serverfarm Cluster (Load-Balancing über BEA) Cluster Load-Balancer HTTPS-Umsetzer Annahmeserver (Apache Webserver) Annahmeserver (Apache Webserver) Anwendungsserver (BEA WebLogic) Anwendungsserver (BEA WebLogic) Anwendungsserver (BEA WebLogic) Datenbankserver (ORACLE) Datenbankserver (ORACLE) Protokolle HTTP Intranetserver (Apache Webserver) (Web-)Services SQL / JDBC SQL*Net Intranetserver (Apache Webserver) Produktion Archiv 7 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

WebLogic) Anwendungsserver (BEA WebLogic) Datenbankserver (ORACLE) Datenbankserver (ORACLE) Protokolle HTTP Intranetserver (Apache Webserver) (Web-)Services

8 Architectural viewpoints Example T Architecture Rich-Client Browser Browser Browser Web-Server (Client) Applikation in Fremd-Domäne Service-Infrastruktur / Middleware Service 1 Service 2 Service 3 WebLogic AWK A-Komponente 1 A-Komponente 2 A-Fall 1 (Use-Case) A-Fall 2 (Use-Case) A-Fall 3 (UseCase) A-Fall 4 (UseCase) A-Verwalter A-Entitätstyp A-Verwalter A-Entitätstyp Attribute und Beziehungen Attribute und Beziehungen Legende benutzt, ruft Adapter Datenbankserver Proxy 8 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

(Use-Case) A-Fall 3 (UseCase) A-Fall 4 (UseCase) A-Verwalter A-Entitätstyp A-Verwalter A-Entitätstyp Attribute und Beziehungen Attribute und

9 Separating the architectural viewpoints eases parallelizing project tasks Architectural viewpoints Time A Architecture T Architecture TI Architecture Reference architectures A Architecture overview Requirements, Subsystems, neigbouring systems Analysis and selection of technologies and tools Implementation of hardware Specification use cases entity model dialog specification etc. Types of layers components classes etc. Implementation of systems software and tools Subsystems, components interfaces, classes, etc. Programming base components (0/T software) Programming the application (A software) 9 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

entity model dialog specification etc. Types of layers components classes etc. Implementation of systems software and tools Subsystems, components interfaces, classes, etc.

10 Agenda Architectural Viewpoints Software Categories Components and Interfaces Reference Architecture for Business Information Systems Literature

11 Software categories Idea behind software categories Software that changes at a different pace should be separated into different modules Parnas, Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

different modules Parnas, 1972 11 Prof. Dr.

12 Software categories Example: Software for salary payment (human resources) IBM AS/400 Business changes Technical changes New legal requirements (taxes) New company payment policies New application server version New database version 12 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

company payment policies New application server version New database version 12

13 Software categories Software categories Categories 0 Software A Software T Software R Software AT Software Which means Independent of application and technology, ideally re-usable. Edamples: strings, containers, Determined by application logic, independent of technology. Lion s share of the application. Examples: customer, account, invoice, Dependent on a technical API. independent of the application logic Examples: persistence layer for specific DBMS Simple transformation logic E.g., to and from XML Dependent on application logic and technology difficult to maintain not re-usable To be avoided! 13 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Examples: customer, account, invoice, Dependent on a technical API.

14 Software categories Software categories as a measure for software quality Percentage of AT-Software Re-usability Maintainability Stability 14 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

15 Agenda Architectural Viewpoints Software Categories Components and and Interfaces Interfaces Reference Architecture for Business Information Systems Literature

16 Components and interfaces Component-oriented design of an automobile External view (interface) of the driver: as simple as possible Internal view: complex External view (interface) of workshop: as simple as possible 16 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

External view (interface) of workshop: as simple as possible 16 Prof. Dr.

17 Components and interfaces Component-oriented software design Example: Authorization component External view: operational interface of application programmer (as simple as possible) operative operative Schnittstelle B Berechtigungskomponente Berechtigungskern Admin- Schnittstelle A Berechtigung GUI External view: administrative interface (as simple as possible) R S RACF- Adapter DB-Zugriff R JDBC RACF Oracle Internal view: complex 17 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Admin- Schnittstelle A Berechtigung GUI External view: administrative interface (as simple as possible) R S RACF- Adapter DB-Zugriff

18 Components and interfaces Interfaces present abilites of a component to different user groups Patient Cat Pet class Cat implements Patient, Pet { } Source: Roger King 18 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

implements Patient, Pet { } Source: Roger King 18 Prof. Dr.

19 Agenda Architectural Viewpoints Software Categories Components and Interfaces Reference Architecture for Business for Business Information Information Systems Systems Literature

20 Reference architecture Reference architecture for business information systems Quasar (Quality Software Architecture) cd Quasar Architecture «Abstract T Component» Client Management «A Component» Dialog Separation of A Software and T Software on the component level «Abstract T Component» Application Kernel Facade «A Component» Application Component Alternatives «Abstract T Component» Authorization Identification of the main technical components Identification of dependencies Alternatives «Abstract T Component» Transaction «Abstract T Component» Persistence 20 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Application Component Alternatives «Abstract T Component» Authorization Identification of the main technical components Identification of dependencies Alternatives

21 Agenda Architectural Viewpoints Software Categories Components and Interfaces Reference Architecture for Business Information Systems Literature

22 Literature References for this lecture Sections of Teil 1 dealing with today s lecture: 1.2 Kategorien (Blutgruppen) 1.3 Schnittstellen und Komponenten 2. Architekturbegriffe 22 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciencse, WS 2008 /

Ähnliche Dokumente

2. A reference architecture for business information systems Reference Architectures and Patterns

2. A reference architecture for business information systems Reference Architectures and Patterns Winter Semester 2007 / 2008 Prof. Dr. Bernhard Humm Darmstadt University of Applied Sciences Department