Architectural Synthesis Approach Sheldon X. Liang Ph. D. August 18, 2015 1 Software Engineering in CS at APU Architectural Synthesis Approach Azusa Pacific

Architectural Synthesis ApproachArchitectural Synthesis Approach

Sheldon X. Liang

Ph. D.

4/19/231

Software Engineering in CS at APUSoftware Engineering in CS at APUArchitectural Synthesis ApproachArchitectural Synthesis Approach

Azusa Pacific University, Azusa, CA 91702, Tel: (800) 825-5278 Department of Computer Science, http://www.apu.edu/clas/computerscience/

http://www.apu.edu/clas/computerscience/




2

Overview (objective problem solution)

Story of System Development

Architectural Synthesis Approach

Compatible Composition Model

CCM-Centric System Transition

What Achieved and Expected

Architectural Synthesis ApproachArchitectural Synthesis Approach

4/19/23







3

Overview Objectives

to develop an architectural model CCM1

to bridge gap between prototype & product

to establish a synthesis approach enabling

smooth evolution of prototype to product

consistently engineering HDSIS2

1 CCM: Compatible Composition Model2 HDSIS: Highly Dependable Software-Intensive Systems

4/19/23







4

Perspective confusion problem

Modeling difference problem

Constraint Attachment problem

CASE tool support problem

Overview Problems

4/19/23







5

Overview Solutions

Modeling HDSIS through perspective views

Architecting prototype via CCM

Formulating dependability as constraints

Evolving prototype into generic framework

4/19/23







Requirement and Decomposition Activity: Whole-Part issues

Collaboration via Communication Interaction: Roles and Responsibility

Interactive methods Architectural style

Architecture and Components Architectural elements

Story of System Development

64/19/23







7

Story Requirement & Decomposition

Family

Income1

Income2

Spending1

Spending2

Spending3

Husband

Wife

Child

Income1

Income2

Spending1

Spending2

Spending3

Conceptual Component

Monolithic:

No Decomposition

No Communication

No Interaction

No Collaboration

Decomposed:

Communication,

Coordination

Interaction

74/19/23







8

Story Prototyping for requirement acquisition

Husband

Wife

Child

Insurance Check

Rebate Check

Honey,I am home Almost ready,

just a second

Hi, How’s schooling It was great

When they are under the same roof, they do not need communication infrastructure

84/19/23







Story Prototyping for requirement acquisition

Rapid Prototyping will capture the conceptual interaction with Dataflow streams without involving concrete facilities for communication

Husband

Wife

Child

Insurance Check

Rebate Check

—Honey,I am home O Almost ready,

just a second

—Hi, How’s schooling O It was great

Husband

Wife

Child

Insurance Check

Rebate Check

—Honey,I am home O Almost ready,

just a second

—Hi, How’s schooling O It was great

94/19/23







Story Collaboration & Communication

Communication facilities forming an architecture that is embodied as components from which system is built, interactions among those components

Husband Wife

Child

Telcom

Caller Listener

Internet

Sender

Receiver

104/19/23







Story Interactive Method/Architectural Style

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

play roles

via styles (method)

comply with protocols

In architecture, components play roles and interact with each other via architectural styles, while complying with communication protocols.

114/19/23







Story Architecture & Components

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

SmithMartha

Lily

Real persons (components) are derived from roles

124/19/23







Story Summary

System Decomposition

Constructing Architecture

Derivational Implementation

Family

Husband

Wife

Child

Income1

Income2

Spending1

Spending2

Spending3

Income1

Income2

Spending3

Family

Husband

Wife

Child

Income1

Income2

Spending1

Spending2

Spending3

Income1

Income2

Spending3Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Sheldon Holly

Lily

Real persons are derived from roles

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Husband Wife

Child

Telcom

È Caller Listener'

Internet

: Sender

Ê Receiver

Sheldon Holly

Lily

Real persons are derived from roles

134/19/23







PSDL Model E Intended

System Compiler

Linker

Executer

Debugger

(1) COMI

Java

C++

Prototyping adjustment

Requirement adjustment

(2)

(3)

Legend: (1) Computational Activity (2’) Associated Constraints (2) Compositional Architecture (3) Derivational Implementation

Ada95

(2’)

CCM


Prototyping

144/19/23








Computational Activity

Derivational Implementation

CCM

O2 NH3 H2O

Water_Flow

Display_status

Drain Inlet Feeder

F_Time

Repository

Adjusting Listener Feeding Listener

Sampler

Source

Sensor

Adjusting Announcer

Feeding Announcer

Compositional Architecture

Dependability Translation Constraints Localization Patterns

Ÿ Availability Ÿ Reliability Ÿ Security Ÿ Integrity Ÿ Flexibility

Ÿ Consistency Ÿ Compatibility Ÿ Granularity Ÿ Heterogeneity Ÿ Real time Ÿ Synchronization

Ÿ Role Ÿ Style Ÿ Protocol

Quantifiable Constraints

PSDL Model E Intended

System Compiler

Linker

Executer

Debugger

(1) COMI

Java

C++

Prototyping adjustment

Requirement adjustment

(2)

(3)

Legend: (1) Computational Activity (2’) Associated Constraints (2) Compositional Architecture (3) Derivational Implementation

Ada95

(2’)

CCM

154/19/23







Conceptual Model Referring to the relationship among role, style, and protocol

Formal Representation Referring to formalism of syntax, semantics and constraints

Substantiated Interconnections Referring to the entity building interconnections

Constraint Attachment Referring to constraints associated with patterns

Compatible Composition Model

164/19/23







CCM-Centric System Transition Principle

Legend Heuristics and judgments Perspective model Automatic transition Descriptive representation Literal Documents E

Requirement Analysis

Constraint Attachment

Property Monitoring

Dependability Acquisition

Intended Product

Architectural Transition

Componential Transition

Mapping

Binding

Acquisition

Operational Concept

Compositional Model

Computational Model

E Architectural

Design

E Application

Implementation

Quantifiable Assessment

Componential Model

Figure 1 Conceptual Context for Quantifiable Architecture17

4/19/23







Computational Requirements Focusing on activities and information flows

Compositional Architecture Focusing on rules governing interactions

Componential Derivation Focusing on component and connectivity

Quantifiable Assessment Focusing on quantifying dependability

CCM-Centric System Transition perspectives

184/19/23







Explicitly define architecture for

faster, better, cheaper systems Clearly uncover perspective concerns for

customer, architect, implementer Incorporate requirements validation for

prototyping / requirement adjustment Quantify stable architecture for

heterogeneity, granularity, compatibility

What Achieved and Expected (progressive)

194/19/23







Thank you very much!

Questions?

That is all

204/19/23







Sometimes they are even contradictory

CustomerCustomer

Perspective Confusion Problem

ArchitectArchitect

ImplementerImplementer

Increased uncertainty about

requirements

Rapid Application

Development

FlexibleConfiguration in

Organization

214/19/23







Hint: a transitional process can be applied to change one into the other with a dependability-reserved transformation.

When modeling a system from various When modeling a system from various perspectives, we found it difficult to perspectives, we found it difficult to reflect various stakeholders’ concerns, reflect various stakeholders’ concerns, because compatibility is not easily assuredbecause compatibility is not easily assured

Modeling Difference Problem

224/19/23







Hint: dependability properties of HDSIS, such as Hint: dependability properties of HDSIS, such as availability, , reliability, integrity, security, maintainability, , are generally translated into quantitative constraintsare generally translated into quantitative constraints

How to attach dependability constraints on architectural artifacts, this becomes a key issue because it is not easy to find the crucial formal argument to which constraints are bound

Constraint Attachment Problem

234/19/23



Hint: a well-formulated description provides the mechanism for reasoning and manipulation

A real challenge is that intellectual models A real challenge is that intellectual models are not easily represented as semantic are not easily represented as semantic formulas that support efficient reasoning formulas that support efficient reasoning and manipulation by CASE toolsand manipulation by CASE tools

CASE Tool Support Problem

244/19/23



CCM provides a set of rules that govern the CCM provides a set of rules that govern the interactions among components with attached interactions among components with attached constraints constraints

Conceptual Model

CCM is characterized as the interactions between two interactive roles via an architectural style while complying with the communication protocol

COM1 COM2

P

S ro ri

glue glue Component1 Component2

254/19/23



composer Pipeline is generalized type Data is private; Size : Integer : = 100; style as <#pipe-filter#>; protocol as <#dataflow-stream#>; wrapper role Outflow is

port procedure Output(d: Data); procedure Produce(d: Data) is abstract; computation Produce (d); *[ Output (d) à Produce (d) ̧ met(100) à exception; ] end Outflow; role Inflow is port procedure Input(d: Data); procedure Consume(d: Data) is abstract; computation *[ Input (d)à Consume (d) ̧ mrt(100) à exception; ] end Inflow;

collaboration (P : Outflow; C : Inflow) P•Produce(d);

*[ P•Output(d)à P•Produce(d) � C•Input(d) à C•Consume (d)] end Pipeline;

COM1 COM2

P

S ro ri

glue glue Component1 Component2

Dependable composers to promote interactions

Heterogeneous forms to establish communication

Topological connectivity to guide configuration

Constraint attachment to quantify interconnections

Substantiated Interconnections

Substantiated interconnections among Substantiated interconnections among components embodied as following four aspects: components embodied as following four aspects:

274/19/23



Constraint Attachment

composer Pipeline is generalized … role Outflow is port procedure Output(d: Data); procedure Produce(d: Data) is abstract; computation Produce (d); *[ Output (d) latency(60) Produce (d) met(100) latency-signaled LAT-EXCEPTION met-signaled MET-EXCEPTION ] end Outflow; … … end Pipeline;

COM1 COM2

P

S ro ri

glue glue

LatencyMET

Latency: the upper bound of communication delay MET : Maximum Execution Time of computation

Dynamic design inspection to monitor

system execution

Component1 Component2

284/19/23



Topological Connectivity

Topological connectivity simplifies the Topological connectivity simplifies the interconnection among components as the following interconnection among components as the following four forms:four forms:

Fork (1~N): single producer to multiple consumers

Merge (N~1): multiple producers to single consumer

Unique (1~1): single producer to single consumer

Hierarchy: external producer to interact with the internal consumer, and vice versa

294/19/23



Topological Connectivity -- FORK

Component

Composer

Producer

Consumer

304/19/23



The viewpoint for the customer focuses on the activities The viewpoint for the customer focuses on the activities and information flows that accomplish the operational and information flows that accomplish the operational concept. The activities are also compartmentalized as concept. The activities are also compartmentalized as hierarchical components through information linkshierarchical components through information links

Computational Requirements

“Hole Component

High level in hierarchy

Low level in hierarchy

Sub-

314/19/23








PPcomputationcomputation = [ = [CCcc, , II, , CtCt ( (CCcc, , II)])]Cc: Conceptual component

I: Interconnections

Ct: Constraints on Cc and I

324/19/23








Fishier

334/19/23







The perspective from architect is concerned about The perspective from architect is concerned about the rules that govern the interactions between the rules that govern the interactions between components through compositional patternscomponents through compositional patterns


P

S r

o r

i

344/19/23








PPcompositioncomposition = [ = [CCcc R, RR, Roo──

SS//PP→→RRii, Ct, Ct ( (R, S, PR, S, P)])]

CCcc RR : component extracted as role

RRoo──SS//PP→→RRii

: interaction between roles

S: architectural style

P: communication protocol

COM1 COM2

P

S ro ri

glue glue

354/19/23







April 19, 2023

36


O2 NH3 H2O

Water_Flow

Display_status

Drain Inlet Feeder

F_Time

Repository

Adjusting Listener Feeding Listener

Sampler

Source

Sensor

Adjusting Announcer

Feeding Announcer



April 19, 2023

37

The perspective from implementer refers to The perspective from implementer refers to physical components, topological connectivity physical components, topological connectivity that will be instantiated to carry out the that will be instantiated to carry out the computational activitycomputational activity

Componential Derivation

PPderivationderivation= [= [R R CCpp, , ((CCppRRoo)─)─SS//PP→(→(RRii CCpp)), Ct, Ct ( (CCpp S, P S, P)])]

COM 1 COM 2

P

S ro ri

glue glue

R R CCpp : physical component derived

from roles

CCppRRoo: instance component glued to

role



38

Componential Derivation

38

PPderivationderivation= [= [R R CCpp, , ((CCppRRoo)─)─SS//PP→(→(RRii CCpp)), Ct, Ct ( (CCpp S, P S, P)])]

R R CCpp : physical component derived from roles

CCppRRoo: instance component glued to role



April 19, 2023

April 19, 2023

39

This refers to the abstraction of dependability, its This refers to the abstraction of dependability, its translation to quantitative constraints, and the handling translation to quantitative constraints, and the handling of these constraints applied in the design, construction, of these constraints applied in the design, construction, and evolution of a software-intensive system and evolution of a software-intensive system


Availability Reliability Security Integrity Flexibility

Consistency Compatibility Granularity Heterogeneity Real time Synchronization

Role Style Protocol



April 19, 2023

40


Availability Reliability Security Integrity Flexibility

Consistency Compatibility Granularity Heterogeneity Real time Synchronization

Role Style Protocol

Pquantification=[Dr Qc, Qc ─Attach CCM (R,S,P)]

Dr Qc represents translation of dependability to quantitative constraints

─attach : represents the localization of constraints

CCM(R, S, P): represents model parameterized as Role, Style, &

Protocol

Quantifiable Assessment



April 19, 2023

41

Quantifiable Assessment Design Inspection

Static Checking Check if the quantifiable attributes (constraints) meets the needs in specification at architectural level (artifacts)

Data analysis, reasoning, and static schedule

Dynamic MonitoringTest if the quantifiable attributes (properties) violates the predefined regulation at runtime



April 19, 2023

42

Quantifiable Assessment Dynamic Monitoring

composer Pipeline is generalized … role Outflow is port procedure Output(d: Data); procedure Produce(d: Data) is abstract; computation Produce (d); *[ Output (d) latency(60) Produce (d) met(100) latency-signaled LAT-EXCEPTION met-signaled MET-EXCEPTION ] end Outflow; … … end Pipeline;

COM1 COM2

P

S ro ri

glue glue

LatencyMET

Latency: the upper bound of communication delay MET : Maximum Execution Time of computation

Dynamic design inspection to monitor

system execution

Component1 Component2

