PART2 B-WS13-14 V08 20131124 - TU Dresdenst.inf.tu-dresden.de/files/teaching/ws13/fps13/... ·...

transcript

Future-Proof Software-Systems(Zukunftsfähige Software-Systeme)

Frank J. FurrerFrank J. FurrerDr. sc. techn. ETH-Zürich

TU Dresden WS 2013/2014

Part 2 - BPart 2 - B

V0.81 / 26. 11.2013

Future-Proof Software-Systems:

A6: Reference Architectures,Frameworks and Patterns

Industrial Architecture

Copyright Frank J. Furrer 2013 2

EngineeringDiscipline

ArchitectureProcess

GovernanceInstrument

Structure

ArchitecturePrinciples

ArchitectureGuidelines &Best Practices

ArchitectureMetrics

ArchitectureStandards

BusinessArchitecture

ApplicationsArchitecture

Safety &Security

Architecture

IntegrationArchitecture

TechnicalArchitecture

StandardsEnforcement

TechnologyPortfolio

Management

ApplicationsPortfolio

Management

ServicePortfolio

Management

IT StandardsDevelopment

ComplexityManagement

Architect‘sTraining

Business-to-ITAlignment

ArchitectureCommunication

Future-Proof Software-Systems: Ref Archs & Patterns

Reference Architecture:

A reference architectureprovides a template solutionfor an architecture for aparticular application domain

- such as financial systems,automotive, aerospace etc.

Architecture Pattern:

An architectural pattern isa concept that solves anddelineates some essentialcohesive elements of asoftware architecture

http://en.wikipedia.org/wiki/Architectural_pattern

Reference Architectures, Architecture Frameworks, Architecture Patterns:

highly valuablesoftware/system architectureknowledge in proven & easilyaccessible form

automotive, aerospace etc.

Architecture Framework:

An architecture frameworkestablishes a common practicefor creating, interpreting,analyzing and usingarchitecture descriptions withina particular application domain

[ISO/IEC/IEEE 42010]

Architectural_pattern

Patterns

Architecture Pattern:

An architectural pattern is a concept that solves and delineates some essentialcohesive elements of a software architecturehttp://en.wikipedia.org/wiki/Architectural_pattern

Origin of Patterns:Christopher Alexander, 1977

Application to Software Architecture:Erich Gamma, Richard Helm,Ralph Johnson, John Vlissides, 1995(„Gang of Four“)

ihpatte

/desig

(„Gang of Four“)

Example: Security Pattern „RBAC“ [Role-Based Access Control](Fernandez: Security Patterns in Practice, 2013, ISBN 978-1-119-99894-5)

accessDataUser

idname

ProtectionObject

idname

memberOf

isAuthorizedFor

ROLE-BASED ACCESS CONTROL PATTERN:

The User and Role classes describe registered users and their predefined

roles. Users are assigned to roles, roles are given rights according to theirfunctions. The association class Right defines the access types that a

user within a role is authorized to apply to the ProtectionObject.

accessType

checkRights

Example: Broker Pattern(Buschmann et. al.: A System of Patterns, 1996, ISBN 0-471-95869-7)

Client-sideProxy

send_request

Server-sideProxy

call_servicesend_response

calls*

Broker

register_servicefind_serverfind_clientforward_requestforward_response

transfermessage

*usesAPI

usesAPI

Server(Service Provider)

call_serverstart_taskuse_Broker_API

Server

run_serviceuse_Broker_API

Bridge

pack/unpack dataforward_messagetransmit_message

usesAPI

BROKER PATTERN:

This pattern is used to structure distributed systems with decoupledcomponents that interact by remote service invocations.

Patterns are recorded architecture and design wisdomin „canonical“ form. Patterns help you build on thecollective experience of skilled architects and softwareengineers (Buschmann et. al. ISBN 0-471-95869-7)

Patterns

Patterns are not final, directly applicable solutions!Patterns are intellectual building blocks which mustbe intelligently integrated into your work

Patterns are excellent documentation and communicationsinstruments. They are formal, clear and focussed

www.123rf.com

There is a rich literature about patterns.The future-proof software-system engineerneeds to continuously familiarize himselfwith this trove of architecture knowledge!

Architecture Frameworks

Architecture Framework:

An architecture framework establishes a common practice for creating, interpreting,analyzing and using architecture descriptions within a particular application domain

[ISO/IEC/IEEE 42010]

Meta-Model

TemplatesTemplates

TemplatesPrinciples

Architecture Methodology/Process Information Architecture

Technical Architecture

Integration Architecture

Applications Architecture

Business Architecture

ModelingNotation

ReferenceArchitectures

Architecture Organization Blueprint

Example: TOGAF (1/2)[The Open Group Architecture Framework] http://www.togaf.org/

Process,Methodology

Deliverables,Artefacts

ReferenceModels

ArchitectureOrganization

Repositoryetc.

Principles

Example: TOGAF (2/2)[The Open Group Architecture Framework] http://www.togaf.org/

rg/arc

-doc/arc

ap22.h

TOGAFIII-RM

rg/arc

III-RMReferenceArchitecture(High level)

Reference Architecture:

A reference architecture provides a template solution for a generic architecture for aparticular application domain

- such as financial systems, automotive, aerospace etc.

Reference Architecture

A reference architecture may recommend: FundamentalStructure

ComponentModel

ServiceStandardizationTechnology

Choices

SafetyMechanisms

Component ContractModel

Example: AUTOSAR (1/2)[AUTomotive Open System ARchitecture] http://www.autosar.org

tosar.

ad/papers

tosar.

ad/papers

Example: AUTOSAR (2/2)http://www.autosar.org

AUTOSAR is well documented in a number ofinteresting documents (some only for members)

AUTOSAR:

„Cooperate on

Standards –

Compete on

Implementations“

Example: BIAN (1/2)Banking Industry Architecture Network: http://www.bian.org

BIAN standardizes the full functionallandscape of a financial institution

Example: A (2/2)http://www.bian.org

Financial Markets

InvestmentManagement

Investment PortfolioPlanning IT Service

Investment

FinancialMarkets

InvestmentManagement

Investment PortfolioPlanning

Internal IT SystemOutsourced or3rd party SW

Investment PortfolioAnalysis

Investment PortfolioManagement

eTrading

siness

IT Service

InvestmentPortfolioAnalysis

siness

eTrading

Investment PortfolioManagement

Industry-wide,exchangeable,standardizedservices

Architecture Principle A5:

Reference Architectures, Frameworks and Patterns

1. Always consider applicable reference architectures, frameworksand patterns. Whenever possible adhere to proven patterns asfoundations of architecture and design

2. Manage and cultivate a set of patterns (in a repository) in yourcompany for easy reference. Annotate these with your own

company for easy reference. Annotate these with your ownexperience

3. For 3rd party software insist (as much as possible) on industry-standardized interfaces, services and managed redundancy

Justification: Reference architectures, frameworks and patterns arehighly valuable architecture and design knowledge in condensedform. Using suitable, proven reference architectures, frameworks andpatterns leads to good, safe and often optimum solutions

Reference Architectures

Architecture Frameworks

Architecture Patterns

Future-Proof Software-Systems Engineer

Apply & enforce

ol.blo

gspot.

/2011/06/bis

Future-Proof Software-Systems: Lessons learned for FPSS

Lessons learned for future-proof software-systems:

Reference architectures, architecture frameworks and architecturepatterns are highly valuable containers of proven architecturalknowledge

The future-proof software-systems engineer needs a large knowledge

The future-proof software-systems engineer needs a large knowledgeof these architectural artefacts

Established, accepted and enforced reference architectures,architecture frameworks and architecture patterns are of great value toan organization and should be carefully managed

Future-Proof Software-Systems: Research Topics

Research Questions Master Thesis Level:• Apply the TOGAF architecture framework step by step to a ( simple) system ofyour choice

Research Questions Ph.D. Thesis Level:• Develop an architecture framework for the architecting of CPS (Cyber-PhysicalSystems)

• Develop an architecture framework for the architecting of Robotics Systems (seealso the program „MORSE“ of the University of Dresden)

Future-Proof Software-Systems: References

References:ReferencesFowler03 Martin Fowler:

Patterns of Enterprise Application Architecture

Addison Wesley, Boston, USA, 2003. ISBN 978-0-321-12742-0Vlissides98 John Vlissides:

Pattern Hatching – Design Patterns Applied

Addison Wesley Longman Inc., Reading MA, USA, 1998. ISBN 978-0-201-43293-5Buschmann96 Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal:

Pattern-Oriented Software Architecture - Volume 1

John Wiley & Sons, Chicester, UK, 1996. ISBN 978-0-471-95869-7Fernandez13 Eduardo B. Fernandez:

Security Patterns in Practice – Designing Secure Architectures using Software Patterns

John Wiley & Sons, Ltd., Chichester UK, 2013. ISBN 978-1-119-99894-5

John Wiley & Sons, Ltd., Chichester UK, 2013. ISBN 978-1-119-99894-5Hanmer07 Robert Hanmer:

Patterns for Fault-Tolerant Software

John Wiley & Sons, Chicester, UK, 2007. ISBN 978-0-470-31979-6Duffy04 Daniel J. Duffy:

Domain Architectures – Models and Architectures for UML Applications

John Wiley & Sons, Ltd., Chichester, UK, 2004. ISBN 978-0-470-84833-2Kindel09 Olaf Kindel, Mario Friedrich:

Softwareentwicklung mit AUTOSAR – Grundlagen, Engineering, Management in der Praxis

dpunkt.verlag GmvH, Heidelberg, 2009. ISBN 978-3-89864-563-8

See also: www.autosar.org [last accessed 29.8.2013]TOGAF11 The Open Group:

TOGAF Version 9.1 Enterprise Edition – An Introduction (White Paper)

The Open Group, San Francisco, USA, December 2011. Document Number W118. Downloadable from:

https://www2.opengroup.org/ogsys/jsp/publications/mainPage.jsp [last accessed 16.9.2013]BIAN12 BIAN (Banking Industry Architecture Network):

BIAN Metamodel Specification

Version 1.6, Iteration 13, May 30, 2012. Downloadable from: www.bian.org [last accessed 16.09.2013]

References:

ReferencesBIAN12 BIAN (Banking Industry Architecture Network):

BIAN Metamodel Specification

Version 1.6, Iteration 13, May 30, 2012. Downloadable from: www.bian.org [last accessed 16.09.2013]

Feiler13 Peter H. Feiler, David P. Gluch:

Model-Based Engineering with AADL – An Introduction to the SAE Architecture Analysis and Design Language

Addison-Wesley (SEI Series), N.J., USA, 2013. ISBN 978-0-321-88894-5

A7: Reuse and Parametrization

ArchitectureProcess

Structure

ArchitectureMetrics

Safety &Security

Architecture

TechnologyPortfolio

Management

ServicePortfolio

Management

Future-Proof Software-Systems: Reuse and Parametrization

Definition:Reuse occurs when someone avoidshaving to write software by obtaining andusing software from someplace else[Jeffrey S. Poulin, 1997, ISBN 0-201-64313-9]

Reuse is:

Software Reuse http

://arto

fsoftw

Reuse is:

• very powerful (strong contribution to agility)

• (very) difficult

• if not done correctly: dangerous for the architecture

Successful Reuse requires:

• a company-wide reuse strategy

• a strong reuse organization

• a dedicated, committed management

Types of Reuse

Black BoxReuseUnmodified (1:1) reuse

Grey BoxReuseLimited modified reuse(Specific changes 25 %)

White BoxReuseSignificantly modified(Specific changes 25 %)

Levels of Reuse

Contracts

Applications:Business Functions

Level 3: Services

Business Process

Workflow

Level 4:

BusinessRules

Functionality:Code

Data:DB-Schema

Level 1:

Encapsulated Functionality & Data:Components

Level 2: Interfaces

Business Functions

Value of Reuse

Contracts

Level 3: Services

Business Process

Workflow

Level 4:

BusinessRules

very high

medium

Functionality:Code

Data:DB-Schema

Level 1:

Encapsulated Functionality & Data:Components

Level 2: Interfaces

Business Functions

medium

local reuse

„global“reuse

Contracts

Services

Business Process

Workflow

BusinessRules

Services arecalled to buildapplications orsystems

Business rulesare reused toimplementbusinessprocess steps

Functionality:Code

Data:DB-Schema

Encapsulated Functionality & Data:ComponentsInterfaces

Business Functions

Codefragments

Fragments ofcode are reusedin programs

Componentsare composedto applications

systems

Business Case of Reuse€

ProjectDevelopmentCost

DevelopmentTime

one-timeuse Value

Development

Project

DevelopmentCost

DevelopmentTime

Reusable Software

Project

DevelopmentCost

Development

Reusable Software

DevelopmentTime

Who is paying?

gs.law

The project has additional costand longer time-to-market

Reuse penalty

Projectcreating reusable

software Tra

Same projectcreating one-time software

All projects reusing the software havelower cost and shorter time-to-market

Reuse benefit

software

One-Time SoftwareDevelopment Process

SpecPhase

BusinessRequirements

ArchitectureRequirements

One-TimeSoftware

Development Process for Reuse

Reusable SoftwareDevelopment Process

SpecPhase

BusinessRequirements

ArchitectureRequirements

ReusableSoftware

SpecPhase

BusinessSzenarios

Reuse ArchRequirements

Elements for successful Reuseh

A dedicated andcommitted management

ReuseStrategy

A company-widereuse strategy

A strongreuse organizationGood software

architects

http://artofsoftwarereuse.com/tag/schemas/

Why should we work with Reuse?

Because of:

• The benefits (in development cost and time-to-market) are considerable

• The quality of the software is higher (mature components, managedevolution and maintenance)

• Use of proven 3rd party components and services

• Optimization: reusable components on-time components

Which are the risks if we work with Reuse?

Risks:

• Quality of reusable software not sufficient

• Reuse-factor too low

• Reuse-strategy not complete or adequate

• Creation of unmanged redundancy (both functional and data)

• Development and maintenance process more complicated

• Management not sufficiently supportive of reuse-strategy

Types of Reuse

Black BoxReuse

Unmodified (1:1) reuse

Parametrization

Business Rules

True, value-generating Reuse

Grey BoxReuseLimited modified reuse(Specific changes 25 %)

White BoxReuseSignificantly modified(Specific changes 25 %)

Not reuse unmanaged redundancy

Grey Box

Grey Box Modification Divergence (Unmanaged Redundancy)

Grey Box

Modification A

GreyBox

Modifi-

Change

Grey Box

Modifi-cation C

GreyBox

Modifi-cation

Parametrization and Business Rules

Black BoxReuse

Unmodified (1:1) reuse

Parametrization

Business Rules

Parametrization: Selection of a predefined behaviour of the black boxby parameters stored outside of the black box (Not part of the black boxfunctionality or data). The parameters are loaded at run-time. Newversions of the black box interpret the parameters correctly.

Business Rules: Business rules are specified in BR-languages anddefine processing logic – instead of having the processing logicimplemented in code within the black box (Not part of the black boxfunctionality or data). The business rules are loaded at run-time. Newversions of the black box interpret the business rules correctly

Black Box Usage (Managed Redundancy)

Black Box

Parametrization

Business Rules

Change

Loaded/Initializedat Run-Time

Black Box

Parametrization

Business Rules

Parametrization

Business Rules

Distributed/Updatedby ConfigurationManagement System

Parametrization Example: Different Account Number Formats

Payment OrderAccount Number Format: Bank Leu

Payment OrderAccount Number Format: CREDIT SUISSE

PaymentApplication

Clearing

Payment OrderAccount Number Format: IBAN

Payment OrderAccount Number Format: Future Format

Application

Accounts DB

System

Business Rules Example

Business Process

Application Software

Verbal Expression:

“A car with accumulatedmileage greater than 5’000since its last service mustbe scheduled for service”

BusinessLogic

SpecificBusiness

RulesInterpreter

Formal Expression:

If Car.miles-current-period > 5000 then

invoke Schedule-service (Car.id)

End if

Measuring the Reuse-Factor:

Contracts

Applications:

Services

Business Process

Workflow

BusinessRules

# ofapplications

using theservice

% of reusedbusiness rulesin a different

context

Functionality:Code

Data:DB-Schema

Encapsulated Functionality & Data:ComponentsInterfaces

Codefragments

service

# of calls/hour

# ofapplications

using thecomponent

# of componentsimplementingthe code/DB

fragment

Future-Proof Software-Systems: Industry Standards

Reuse and Parametrization

1. Use only the black-box concept to build reusable software

2. Whenever possible, configure the reusable modules via parametersor business rules (loaded or initiated at run-time)

3. Install and consequently use a configuration management systemto control the distribution of reusable software modules

4. Provide the 4 elements of successful reuse: Committedmanagement, reuse-strategy, reuse-organization and competent

software architects

5. Adapt your software development process to produce reusablesoftware

Justification: If done correctly, reuseable components have asignificant effect on the agility of the IT-system.

If done correctly, reuseable components have a significant (positive)effect on the agility of the IT-system

Use only the black-box concept (= unmodified reuse) to buildreusable software

Parametrization and business-rules are powerful instruments toadapt reusable software to different contexts

Successful reuse is only possible if 4 prerequisites are met:Committed management, an adequate reuse-strategy, an effectivereuse-organization and competent software architects

The software development process for reusable software is morecomplex than for one-time software

Research Questions Master Thesis Level:• Study the different reuse-concepts in some application areas (banking,automotive, aerospace etc.) from literature and compare them. Describecommonalities and differences. Formulate recommendations for application-independent reuse

Research Questions Ph.D. Thesis Level:• Investigate the different software development processes focused on producing

• Investigate the different software development processes focused on producingreusable software artefacts (from literature). Distill the good points and elaborateon the weak points. Define a strong process for the whole life-cycle of reusablesoftware development, including both local (inside the company) and global (reuseof external services). Put special emphasis on mechanisms to detect, avoid andeliminate unmanaged redundancy

References:ReferencesMurer11 Stephan Murer, Bruno Bonati, Frank J. Furrer:

Managed Evolution – A Strategy for Very Large Information Systems

Springer-Verlag, Berlin Heidelberg, 2011, ISBN 978-3-642-01632-5Lim98 Wayne C. Lim:

Managing Software Re-Use

Prentice Hall, USA, 1998. ISBN-13: 978-0-13552-3735-9Coulange98 Bernard Coulange:

Software Reuse

Springer-Verlag, Heidelberg, Berlin, 1998. ISBN 978-3-540-76084-9Leach13 Ronald J. Leach:

Software Reuse – Methods, Models, Costs

Ronald J. Leach Publishing, 2nd edition, 2013. ISBN 978-1-9391-42-35-1

Ronald J. Leach Publishing, 2 edition, 2013. ISBN 978-1-9391-42-35-1Hamlet10 Dick Hamlet:

Composing Software Components – A Software-Testing Perspective

Springer-Verlag, New York, N.Y., USA, 2010. ISBN 978-1-44197147-0Poulin97 Jeffrey S. Poulin:

Measuring Software Reuse – Principles, Practices, and Economic Models

Addison Wesley Longman Inc., Reading MA, USA, 1997. ISBN 0-201-63413-9Grunske10 Lars Grunske, Ralf Reussner, Frantisek Plasil (Editors):

Component-Based Software Engineering

13th International Symposium CBSE 2010 (June 2010). Springer-Verlag, Berlin & Heidelberg, 2010 (LNCS6092). ISBN 978-3-642-13237-7

Arbab12 Farhad Arbab, Peter Csaba Ölveczky (Editors):

Formal Aspects of Component Software

8th International Symposium FACS 2011 (September 2011). Springer-Verlag, Berlin & Heidelberg, 2012 (LNCS7253). ISBN 978-3-642-35742-8

Vliet08 Hans Van Vliet:

Software Engineering – Principles and Practice

John Wiley & Sons, Chichester, UK, 3rd edition 2008. ISBN 978-0-470-03146-9

A8: Industry Standards

ArchitectureProcess

Structure

ArchitectureMetrics

Safety &Security

Architecture

TechnologyPortfolio

Management

ServicePortfolio

Management

A STANDARD is:

• a formal, established norm for (technical) systems

• a document which establishes uniform (engineering or technical) criteria,principles, methods, processes and practices

www.ietf.org www.omg.orgwww.iso.org

International Standards Organizations

BusinessObjectModelV1.1/2009

CompanyStandards

Example:Napoleonic Guns(1/3)

reads/la

rgest-

.79423

reads/la

In early pre-Napoleonic times (18xx) the artillery cannons were individuallydifferent and required matched cannon balls difficult logistics

Manufacturing tolerances greatly reduced the accuracy and firing power ofthe artillery cannons reduced military impact

Example: Napoleonic Guns(2/3)

de Gribeauval standard:

• reduced and standardized the calibers

complexity reduction

• introduced normalized parts for the cannons

component technology

• set manufacturing processes & tolerances

1776: The de Gribeauvalstandard revolutionizedartillery.

1715-1789

Results: Massively improved military impact Mass production of cannons

Example: Napoleonic Guns(3/3)

lli.com

NapoleonicEmpire

(ca. 1810)

What is the impact of standards ?

Why are standards important ?

Impact:

• Forcing uniform, interoperable solutions in the industry

• Providing proven, widely accepted and mature solutions

• Enabling exchangeable products (mostly)

• Facilitates reuse

• Foundation for validation & certification

Importance:

• Provides long term stability with managed change

• Forces vendors to comply to interoperable solutions

• Advances industries as a whole

• Provides confidence in technical solutions (e.g. safety or security)

Negative: Standards-setting process is quite slow (Wide consensus required)

Industry Standards

1. Strictly adhere to proven, accepted industry-standards in all 5architecture layers and for all phases of the system lifecycle

2. Never allow any use of vendor-specific standards extensions (evenif they look tempting and useful)

3. Keep the number of standards in use to a minimum

4. Introduce new standards only based on very good reasons

5. If for a certain field of your activity there is no industry standard,formulate and instantiate a company standard

6. Enforce strict adherence to (pure) standards via regular reviews

Justification: A heterogenous industry (such as software-production)requires clearly stated foundations for technologies, products andprocesses – otherwise no interoperability, certification, reuse andvendor-independence is possible

Example:WebStandards(1/3)

Domain-specificStandards

Trust: PKI

Reasoning & Proofs

BusinessRules:

Underlying Logic: DL

Semantics(Ontology):DB Query:

Business Applications

SOA-Infrastructure: Web-Services

How can weestablish trust onthe WWW?

WebStandards

TechnicalInfrastructureStandards

Technical Infrastructure

Addressing: URI Unicode

Rules:RIF

(Ontology):OWL

DB Query:SPARQL

Vocabulary: RDF-S

Data Model: RDF

Syntax: XML

Example:WebStandards(2/3)

_nobody_kn

're_a_dog

Example: Authentication:

How can we establish trust in theidentity of an electronic partner ?

Trust: PKI

Answer:

We use aPublic Key Infrastructure (PKI)

Answer:

Use a Public Key Infrastructure(PKI)

PKI assigns Digital Certificates

Answer:

_nobody_kn

're_a_dog

On the Internet, nobody knows you're a dog

PKI assigns Digital Certificatesto entities (Persons, organizations)PKI assigns Digital Certificatesto entities (Persons, organizations)

A digital certificate is anunforgeable electronic proof ofidentity

PKI assigns Digital Certificatesto entities (Persons, organizations)

A digital certificate is anunforgeable electronic proof ofidentity

Digital certificates arestandardized in X.509 and areglobally accepted and used

Example: Web Standards(3/3) CA

Certification Agency[Trusted Entity]

X.509Certificate

_issuer_validity_subject_publicKey

_CA-Signature

Server

_CA-Signature

presents

Standards are highly important instruments for a number of ITfunctions, such as interoperability, security, safety, certification, …

A sufficient (but not overlapping) set of standards should be used,managed and enforced in an organization

No vendor-specific standards extensions (even if they look temptingand useful) should be used

The set of standards established in an organization represents aconsiderable business value

As an architect, look at the standards as a help, not a nuisance

Research Questions Master Thesis Level:• Develop a process for a (fictive) organization to evaluate, select, introduce,enforce and manage an optimum set of standards (Industry-standards and –where not available – company standards)

• Select a specific application domain (e.g. automotive, aerospace, medical,industrial, railway, … and examine their standards in use. Demonstrate the valueof the application and enforcement of this set of standards and the risks if failingto do so

Research Questions Ph.D. Thesis Level:• none

References:

ReferencesAkerkar09 Rajendra Akerkar:

Foundations of the Semantic Web – XML, RDF & Ontology

ALPHA Science Intl. Inc., Oxford, UK, 2009. ISBN 978-1-84265-535-1Jakobs00 Kai Jakobs:

Information Technology Standards and Standardization – A Global Perspective

Idea Group Publishing, Hershey, PA, USA, 2000. ISBN 1-878289-70-5Nash01 Andrew Nash, William Duane, Celia Joseph, Derek Brink:

PKI – Implementing and Managing E-Security

Osborne/McGraw Hill, CA, USA, 2001. ISBN 0-07-213123-3Katz08 Jonathan Katz, Yehuda Lindell:

Introduction to Modern Cryptography

Chapman & Hall/CRC, FL, USA, 2008. ISBN 978-1-58488-551-1Hafner09 Michael Hafner, Ruth Breu:

Security Engineering for Service-Oriented Architectures

Springer Verlag, Heidelberg, Germany, 2009. ISBN 978-3-540-79538-4Al-Hakeem12 Mazin S. Al-Hakeem:

Fundamentals of Web Engineering – An Engineering Approach to Develop Web Services, Contents &Environment under Standards Specification of Web Design

LAP LAMBERT Academic Publishing, 2012. ISBN 978-3-65912-492-1Sahai05 Akhil Sahai, Sven Graupner:

Web Services in the Enterprise – Concepts, Standards, Solutions, and Management

Springer-Verlag, Heidelberg, Berlin, 2005. ISBN 978-0-387-23374-1Dawson07 Anthony L. Dawson, Paul L. Dawson, Stephen Summerfield:

Napoleonic Artillery

Crowood Press Ltd., Wiltshire, UK, 2007. ISBN 978-1-86126-923-2

A9: Information Architecture

ArchitectureProcess

Structure

ArchitectureMetrics

Safety &Security

Architecture

TechnologyPortfolio

Management

ServicePortfolio

Management

Future-Proof Software-Systems: Information Architecture

IT-System

Data,Information

FunctionalityDocumentation,

Models etc.

InformationFunctionality

Models etc.

Technical Infrastructure

Software Structure,Relationships

Repository

Data/InformationArchitecture

Business Model… how to earn money

Business Processes… how to execute the business

operations

Information Architecture Stack:

Enterprise Model

Business Logic Model

Legal&

Information Architecture

tities

Databases/Tables… persistent storage of business

entities & transactions

operations

Applications/Components… Implementation of business

operations

Domain ModelBusiness Object Model

Database/TableModels

Legal&

ecovery

Architecture Principle A?:

1. Strictly

Justification: A

Research Questions Master Thesis Level:•

Research Questions Ph.D. Thesis Level:•

References:References

Lehner13 Wolfgang Lehner, Kai-Uwe Sattler:

Web-Scale Data Management for the Cloud

Springer-Verlag, Heidelberg, 2013. ISBN 978-1-4614-6855-4

A10: Formal Modeling

ArchitectureProcess

Structure

ArchitectureMetrics

Safety &Security

Architecture

TechnologyPortfolio

Management

ServicePortfolio

Management

Future-Proof Software-Systems: Architecture

Business Architecture Layer

architecting

Application (Software) Architecture Layer

Business area:Financial institution

Example:„Customer“

DatabaseSchema

Attributes:Name: …Address: …Date of birth: …etc.

Concept: Account1…*1…*

association

Database Design

BusinessContinuity& DisasterRecoveryPlan

Servicedesign

Access

Concept: Customer

„A person or organizationbuying goods or servicesfrom our organization“

Technical Infrastructure Architecture Layer

Infrastructure Services

Deployment Architecture Layer

PART2 B-WS13-14 V08 20131124 - TU Dresdenst.inf.tu-dresden.de/files/teaching/ws13/fps13/... ·...

Documents