a modular reference structure for component-based architecture … · 2016-02-29 ·...

KIT – University of the State of Baden-Wuerttemberg and

National Research Center of the Helmholtz Association

SOFTWARE DESIGN AND QUALITY GROUP

INSTITUTE FOR PROGRAM STRUCTURES AND DATA ORGANIZATION, FACULTY OF INFORMATICS

www.kit.edu

A Modular Reference Structure forComponent-based Architecture Description Languages

ModComp, Ottawa, 28.09.2015

Misha Strittmatter, Kiana Rostami, Robert Heinrich, Ralf Reussner

Software Design and Quality Group

Institute for Program Structures and Data Organization2 27.09.2015

Palladio Component Model (PCM)

DSL for component-based software architectures

Initial focus design time performance prediction

Misha Strittmatter, Kiana Rostami, Robert Heinrich, Ralf Reussner – A Modular

Reference Structure for Component-based ADLs

Palladio

[Becker09]

DependenciesIntroduction ConclusionModularization Related WorkApplication

Performance

Palladio Component Model (PCM)

DSL for component-based software architectures

Initial focus design time performance prediction

Design did not consider extensibility

Research spectrum broadened

Initial extensions: intrusively

Later: external extensions

Palladio

[Becker09]

Performance

Motivation

Challenge: extension &

evolution

Motivation

evolution

Inconsistent structuring

Motivation

evolution

Improper separation of

concerns

Interface Relations

Resource Interfaces:

Relations & Roles

Events

Infrastructure

Variable Characterization

Parameter Class is in Repo

Events

Infrastructure

Events

Infrastructure (Only examples on class level)

Motivation

evolution

concerns

Dependency cycles

⇒ all or nothing reuse

Motivation

evolution

concerns

Dependency cycles

⇒ all or nothing reuse

⇒ Degradation of

understandability and

maintainability

• Metamodels not designed for extensibility or modularity, are hard to evolve and maintain

• Intrusive modification and extension degrades structure over time

• Variants/branches lead to duplication

Problem

• An approach, which categorizes and divides information into modules and layers

• Guidance and mechanisms for metamodel composition and extension

• Constrainment of dependencies

• Reduced complexity⇒ Improved understandability & maintainability

• Flexibility (pick which modules you really need)⇒ Extensibility, reuse

Benefit

Institute for Program Structures and Data Organization10 27.09.2015 Misha Strittmatter, Kiana Rostami, Robert Heinrich, Ralf Reussner – A Modular

Dependencies

Base Metamodel

Extension Metamodel

At least one element in Ext

does somehow depend on

an element in Base

(EMOF based or similar)

Dependencies

Reference Base Metamodel

Extension Metamodel

Inter-

Interface

Modification

Dependencies

Reference Base Metamodel

Extension Metamodel

Inter-

Interface

Modification

• Should be a “thing” for itself

• If not: see later

Dependencies

Reference

Contains

Base Metamodel

Extension Metamodel

DataTransfer

Object

Dependencies

Reference

Contains

InheritanceRepo

Base Metamodel

Extension Metamodel

BlackBox

CompExtend metamodel

by new subclass

Dependencies

Reference

Contains

Inheritance

Base Metamodel

Extension Metamodel

Extend existing class

by new information:

• Attribute

• Reference

• Containment

Security

Dependencies

Reference

Contains

Inheritance

Base Metamodel

Extension Metamodel

• Not a plain relation as the others

• Only needed when working with

multiple metamodels

Security

Dependencies

Reference

Contains

Inheritance

Extends

Base Metamodel

Extension Metamodel

Security

Dependencies

Reference

Contains

Inheritance

Extends

= Metamodel extension types

Beware: there are ways to use

inheritance to model the

extends relation.

One of them is really bad.

Dependencies

Reference

Contains

Inheritance

Extends

= Metamodel extension types

Beware: there are ways to use

inheritance to model the

extends relation.

One of them is really bad.

All these relations are allowed

between metamodels

if used correctly

Extends: Dependency Inversion

Base Metamodel

Extension Metamodel

Security

Extends: Dependency Inversion

Base Metamodel

Extension Metamodel

Security

Modularization

(Metamodel) modules

Set of classes

Explicit dependencies

No dependency cycles

Module

Module Module

Modularization

(Metamodel) modules

Set of classes

Modularization

Module contains set of concerns

Must be meaningful to use

module with or without extension

Module

Module Module

Modularization

(Metamodel) modules

Set of classes

Modularization

Module contains set of concerns

Must be meaningful to use

module with or without extension

If not: module has to be base for

multiple Extensions

Module

Module Module

Ext 1 Ext 2

Layering

Modules form cycle free,

directed graph

Layering

Modules form cycle free,

directed graph

Modules are

organized in layers

Specific types of

dependencies

between layers

Layers

Π: Paradigm

Δ: Domain

Ω: Quality

Σ: Analyses

Layers

Π: Paradigm

Abstract structure

E.g. composition, object orientation, behavioral formalism

Δ: Domain

Ω: Quality

Σ: Analyses

Layers

Π: Paradigm

Abstract structure

Δ: Domain

Assign domain semantics to paradigm

E.g. software, embedded systems, cyber-physical infrastructures

Ω: Quality

Σ: Analyses

Layers

Π: Paradigm

Abstract structure

Δ: Domain

Ω: Quality

Inherent quality properties assigned to domain entities

Σ: Analyses

Layers

Π: Paradigm

Abstract structure

Δ: Domain

Ω: Quality

Static during execution

Mainly second class entities

E.g. performance, security, resilience

Σ: Analyses

Layers

Π: Paradigm

Abstract structure

Δ: Domain

Ω: Quality

Static during execution

Mainly second class entities

E.g. performance, security, resilience

Σ: Analyses

In-/output, state

Analysis configuration

Application: Starting Point

Modifi-

cations

Artifacts

and Staff

Static

Dependencies

KAMP Maintainability

Prediction

Component Architecture,

Behavior, Performance,

Reliability, Infrastructure,

Events, Resources,

Deployment, Usage, ...

Performance

Results

(Proper elaboration of the PCM’s concerns in [Strittmatter14])

Application: Modularization

Entitiesπ Compo-

sition

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Modifi-

cations

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

Application: Benefit

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

Confi-

dentiality

EntitiesπΔ

Compo-

sition

Software

Components

Static

Dependencies

Development

ArtifactsBehavior

Specification

Perfor-

Performance

Results

Performance

Configuration

Result

Modifi-

cations

Relia-

bility

Failure

Performance

Metrics

Related Work

Structuring:

Orthographic Software Modeling [Atkinson10]

Deep modeling [Atkinson12]

UML archetypes [Coad99]

Software “blood types” [Siedersleben04]

Related Work

Structuring:

Extensibility:

JetBrains MPS [Voelter12]

Arch Studio [Dashofy05]

Related Work

Structuring:

Extensibility:

JetBrains MPS [Voelter12]

Arch Studio [Dashofy05]

Modularity:

Generators [Jung15]

Transformations [Rentschler14]

Future Work

Guidance/rules to assign information to layers

Specifics of layers concerning dependency types

and module types

Survey of extension mechanisms

Future Work

Guidance/rules to assign information to layers

Specifics of layers concerning dependency types

and module types

Survey of extension mechanisms

Further application (whole PCM, …)

Tool support

modularization

structure visualization

modular graphical editors

Conclusion

Design for extensibility and modularity

Guidance for structuring in modules

Classification of information into layers

Conclusion

Explicit dependencies between modules

Avoid dependency cycles between modules

Conclusion

Explicit dependencies between modules

Avoid dependency cycles between modules

Benefit

Reduced complexity

⇒ Understandability & maintainability

Flexibility (pick which modules you really need)

⇒ Extensibility, reuse

𝑓 Π, Δ, Ω, Σ = 𝑀𝑒𝑡𝑎𝑚𝑜𝑑𝑒𝑙

Paradigm

DomainQuality

Analysis

Module

Selection

Summary

Backup

Application: Paradigm

Com-ponent

Inter-face * Composed

Structure

CompositionCoreEntities

AssemblyContext

Connector

Application: Domain

∙ ∙ ∙

Com-ponent

Behavior

AbstractAction

Behavior

InternalAction

ExternalCall

StartAction

∙ ∙ ∙

Modification

ModInterface

ModComp

ModConnector

∙ ∙ ∙

Repository

SoftwareComponent

ComponentRepository

BusinessComponent

InfrastructureComponent

∙ ∙ ∙

OperationInterface

Inter-face

IntraCompPropagation

Propagation

∙ ∙ ∙

Application: Quality

InternalAction

ResourceDemand

Performance

FailureType

Reliability

FailureTypes

HardwareFailure

SoftwareFailure ∙ ∙ ∙

FailureOccurence

FailureProbability

Application: Analysis

Δ ΩEvolutionScenario

KAMP Input KAMP Result

ImpactPropagation

Modification

Propa-gation

DevelopmentArtifact

StaffSpecification

PerformanceResults

OperationResponseTime

OperationInterface

AssemblyContext

Dependencies within the Layering

ΔX X XY

X X XY

Y X YX

X X XY

Y X YX

Y Y XX

Design-oriented

(Quality-describing)

(Analysis-oriented)

(Component-based)

Architecture vs. Software

Description Language

Dependencies

Reference “… knows …”

Contains “… contains …”

Inheritance “… is a …”

Extends “… is a property of …”

“… is a part of …”

“… is a trait of …”

Extension Mechanisms

Implementation of extends relation

Simple reference

Simple inheritance

Abstract reference

Decorator

Stereotyping [Kramer12]

Aspect(-oriented) extension [Jung14]

Completions [Kapova13]

Model weaving

RepositoryComposition

Performance

ResourceTypes

RDSEFF

DataTypes

Component Type Hierarchy

ResourceEnvironment

Reliability

QoS Annotations

a modular reference structure for component-based architecture … · 2016-02-29 ·...

Documents

marbett component solutionsmarbett component...

the canterbury tales by nicholas strittmatter grade 12...

dr. med. beate strittmatter - assets.thalia.media ·...

ambulante kinderintensivpflege braucht zunehmend...

autoradiographic angiotensin-converting [3h]captopril...

circular 76 / 2013 date: 19 november 2013...

thieme clinical collections - titles · thieme clinical...

70th ncaa wrestling tournament 2000 3/16/2000 to 3/18/2000...

owner/operator agreement - strittmatter...

to: all independent truckers - strittmatter...

rougier marie bgstu strittmatter...

freedomofinformation privacyacts subject: … · memorandum...

modcomp ii computer reference manual

neurobiologyofdisease ... ·...

· 2013-10-21 · some aips history ii designed initially...

field guiding/game ranging online · component # 15 –...

jenny strittmatter digital und b2b expertin ·...

modcomp family - the 3c/honeywell legacy project · modcomp...

customer type complaint name component name component...

disussin pap sis - iza institute of labor...