Software Engineering Automation Center Software Engineering - - PowerPoint PPT Presentation

software engineering automation center software
SMART_READER_LITE
LIVE PREVIEW

Software Engineering Automation Center Software Engineering - - PowerPoint PPT Presentation

Software Engineering Automation Center Software Engineering Automation Center ICSE 2003 Workshop on Software Architecture for Dependable Systems ms ICSE 2003 Workshop on Software Architecture for Dependable Syste Perspective- -based


slide-1
SLIDE 1

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225 May 19, 2003 1

Perspective Perspective-

  • based Architectural Approach

based Architectural Approach for Dependable Systems for Dependable Systems

Naval Postgraduate School May 2003 Sheldon X. Liang, J. Puett, Luqi

slide-2
SLIDE 2

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

May 19, 2003 2

Overview Perspective-based Architecting Dependable Compositional Patterns Conclusion

Perspective Perspective-

  • based Architectural Approach

based Architectural Approach for Dependable Systems for Dependable Systems

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-3
SLIDE 3

May 19, 2003 3

Objectives

to develop a method known as PBA1 to incorporate rapid system prototyping (RSP) to build a synthesizing approach that enables explicitly architecting HDSIS2 consistently engineering HDSIS

1 PBA: Perspective-Based Architectural Approach 2 HDSIS: Highly Dependable Software-Intensive Systems

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-4
SLIDE 4

May 19, 2003 4

Perspective confusion problem Model construction problem Constraint localization problem Software tool support problem

Barriers

Barriers

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-5
SLIDE 5

May 19, 2003 5

They are not always coincident concerns for all stakeholders, sometimes they are even contradictory for customer, architect and implementer, respectively.

Customer Customer

Perspective Confusion

Architect Architect Implementer Implementer

Increased uncertainty about requirements Rapid Application Development Flexible Configuration in Organization

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-6
SLIDE 6

May 19, 2003 6

A transitional process can be applied to change one into the

  • ther with a dependability-conserved transformation.

Modeling a system against different Modeling a system against different perspectives should reflect different perspectives should reflect different stakeholder stakeholder’ ’ s concerns, and it is required s concerns, and it is required that these models are compatible that these models are compatible

Model Construction

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-7
SLIDE 7

May 19, 2003 7

How to localize these constraints becomes key issue because it is not easy to find the crucial formal argument

  • n which constraints are localized

Dependable properties of HDSIS, such as Dependable properties of HDSIS, such as availability, , reliability, integrity, security, maintainability, are generally translated , are generally translated into quantitative constraints into quantitative constraints

Constraints Localization

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-8
SLIDE 8

May 19, 2003 8

A well-formulated description provides the mechanism for reasoning and manipulation

Intellectual models are to be represented Intellectual models are to be represented as semantic formulas that is suitable for as semantic formulas that is suitable for reasoning and manipulation by CASE reasoning and manipulation by CASE tools and this will be the main challenge. tools and this will be the main challenge.

Software Tool Support

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-9
SLIDE 9

May 19, 2003 9

Solutions

Modeling HDSIS via multiple perspectives Explicit architecture via compositional patterns Property formulation via localized constraints System evolution via generic framework

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-10
SLIDE 10

May 19, 2003 10

PBA: Perspective-Based Architectural Approach

  • Computational Activity

Operational Concept

  • Compositional

Architecture

Rules / patterns for Interconnections

  • Derivational

Transformation

Components and Connectivity

Behavioral Activities Real-time Constraints Architectural Properties

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Prototyping (Model) Refining (Coding) System Architecting Component Evolving Constructing (Prototype)

User’s Informal Needs Highly Dependable Systems Design Inspection

Generating (Framework)

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-11
SLIDE 11

May 19, 2003 11

Computational Activity Compositional Architecture Derivational Implementation Transitional Procedure

Perspective-Based Architectures

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-12
SLIDE 12

May 19, 2003 12

Computational activity accounts for the Computational activity accounts for the customer perspective concerns of computation customer perspective concerns of computation and interconnection and interconnection Computational Activity

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

P Pcomputation

computation = [

= [C Cc

c,

, I I, , Ct Ct ( (C Cc

c,

, I I)] )]

Computational activity is used to capture the activities and information flows that will accomplish the operational concept

“Hole Component

High level in hierarchy Low level in hierarchy Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-13
SLIDE 13

May 19, 2003 13

Compositional architecture accounts for the Compositional architecture accounts for the architect's perspectives of explicit treatment of architect's perspectives of explicit treatment of system composition and architecture with system composition and architecture with constraints localized on compositional patterns constraints localized on compositional patterns Compositional Architecture

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

P Pcomposition

composition = [

= [C Cc

c ⇒

⇒ R, R R, Ro

─S

S/

/P

P→

→R Ri

i, Ct

, Ct ( (R, S, P R, S, P)] )]

Compositional architecture provides a set of rules (patterns) that governs the interactions among components

P S

ro ri

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-14
SLIDE 14

May 19, 2003 14

Derivational implementation accounts for the Derivational implementation accounts for the implementer's perspectives of component implementer's perspectives of component derivation and connectivity derivation and connectivity Derivational Implementation

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

P Pderivation

derivation= [

= [R R ⊃ ⊃C Cp

p,

, ( (C Cp

p

R Ro

  • )

)─ ─S

S/

/P

P→

→( (R Ri

i

C Cp

p)

), Ct , Ct ( (C Cp

p S, P

S, P)] )]

Derivational implementation identifies physical components and connectivity that will be instantiated to carry out the computational activity

COM 1 COM 2 P S ro ri glue glue

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-15
SLIDE 15

May 19, 2003 15

Transitional Procedure

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

P computation P composition P derivation

Cc Cc ⇒ R R ⊃Cp I Ro?S/P? Ri (CpR)?S/P? (R C Ct(COM, INT)

Explicit Architecting via Compositional patterns

Ct (R, S, P)

Physical Derivation via PBA composers

Ct (Cp, S, P)

O2 NH3 H2O Water_Flow Display_status Drain Inlet Feeder F_Time Repository

Adjusting Listener Feeding Listener

Sampler Source Sensor

Adjusting Announcer Feeding Announcer

COM1 COM2

P S

ro ri

glue glue COM1 COM2

P S

ro ri

glue glue

COM1 COM2

P S

ro ri

glue glue

Prototyping A nalyzer Pattern Selector Fram ew

  • rk G

enerator Com ponent Evolver

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

Framework Generator

slide-16
SLIDE 16

May 19, 2003 16

Conceptual Model Formal Representation Substantiated Interconnections Dependability vs Constraints

Dependable Compositional Patterns

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-17
SLIDE 17

May 19, 2003 17

Compositional patterns provide a set of rules Compositional patterns provide a set of rules that govern the interactions among components that govern the interactions among components with localized constraints with localized constraints Conceptual Model

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Characterized as the interactions between two interactive roles via the architectural styles while complying with the communicatory protocols

COM1 COM2

P S

ro ri

glue glue

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

Component1 Component2

slide-18
SLIDE 18

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;

May 19, 2003 18

Formal Representation

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

COM1 COM2

P S

ro ri

glue glue

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225 Component1 Component2

slide-19
SLIDE 19

May 19, 2003 19

Substantiated Interconnections

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Substantiating the interconnections among Substantiating the interconnections among components deals with following four aspects: components deals with following four aspects:

Dependable composers to promote interactions Heterogeneous forms to establish communication Topological connectivity to guide configuration Constraint localization to govern interconnections

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-20
SLIDE 20

May 19, 2003 20

Topological Connectivity

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Topological connectivity simplifies the Topological connectivity simplifies the interconnection among components and comes in interconnection among components and comes in the following forms: the following 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

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-21
SLIDE 21

May 19, 2003 21

Topological Connectivity -- FORK

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Component Composer

Producer Consumer

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-22
SLIDE 22

May 19, 2003 22

Dependability vs Constraints

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

This deals with the abstraction of dependability, its This deals with the abstraction of dependability, its translation to quantitative constraints, and the handling translation to quantitative constraints, and the handling

  • f these constraints applied in the design, construction,
  • f these constraints applied in the design, construction,

and evolution of a software and evolution of a software-

  • intensive system.

intensive system.

Dependability

Translation Constraints Localization Patterns

  • Availability
  • Reliability
  • Security
  • Integrity
  • Flexibility
  • Consistency
  • Compatibility
  • Granularity
  • Heterogeneity
  • Real time
  • Synchronization
  • Role
  • Style
  • Protocol

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-23
SLIDE 23

May 19, 2003 23

Example of Localized Constraints

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms 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

Latency MET

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

Dynamical design inspection to monitor system execution

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225 Component1 Component2

slide-24
SLIDE 24

May 19, 2003 24

Explicitly defined architectures promise:

faster, better, cheaper systems PBA uncovers perspective concerns customer, architect, implementer PBA incorporates requirements validation prototyping / requirement adjustment PBA quantifies invariant architecture heterogeneity, granularity, compatibility

Conclusion

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225

slide-25
SLIDE 25

May 19, 2003 25

Thank you very much!

Questions?

That is all

Software Engineering Automation Center Software Engineering Automation Center

ICSE 2003 Workshop on Software Architecture for Dependable Syste ICSE 2003 Workshop on Software Architecture for Dependable Systems ms

Naval Postgraduate School, 833 Dyer Road, Monterey, CA 93943-5118 Tel: (831) 656-3195 Email: seac@nps.navy.mil http://seac.nps.navy.mil/ Fax: (831) 656-3225