UCS2703 : Software Architecture

Unit-III
Architecture description, documentation and
evaluation

1
 Session Meta Data

Prepared By : Swarnalakshmi Ravi, Associate

Professor
Date : 25-Jul-2024

2
 Session Objectives
– The architectural description and documentation
– The architectural implementation and evaluation techniques
– The architectural rubrics and architectural trade off analysis
method ( ATAM )

3
 Session Outcomes
• At the end of this unit, participants will be able to
– Understand the architectural description and documentation
– Understand the architectural implementation and evaluation
techniques
– Understand the architectural rubrics and architectural trade off
analysis method ( ATAM )

4
  Architecture description

 We broadly saw earlier (unit-1) that an architecture

Unit-3 should contain Components, connectors and inter
relationships subject to some constraints.
Architecture
description,  This can be expanded to describe as follows:
documentati  -Specific elements or specifications

on and  -Components

Evaluation  -Connectors
 -Interactions
 - Constraints: Static vs Dynamic; Structural vs
Behavioral
  Architecture description

Unit-3  Static vs Dynamic aspects

Architecture  Functional Vs Non-functional aspects
description,  Structural Vs Behavioral aspects
documentati
on and  Take an example of architecture to find lifetime
predictivity of an asset in the factory
Evaluation  Let us list down the above facts (collective classroom
discussion)
  Architecture Evaluation
aspects

Unit-3  Ambiguity
Architecture  Accuracy

description,  Precision

documentati
 a –Neither accuracy nor
on and precision
Evaluation  b-Accuracy, No precision
 c-No accuracy, but precise
 d-Both accuracy, precision
  Architecture Evaluation aspects

Unit-3
Architecture
description,
documentati
on and
Evaluation
2 different architectural styles, 2 different systems

View- representation of the 2 systems

Viewpoint- a filter applied on the view ,that is the context applicable

to each system
  Architecture- Visualization & Evaluation
 Fidelity/Faithful to model
(adherence)
Unit-3
 Consistency
Architecture
description,  Comprehensibility
documentati
 Dynamism
on and
Evaluation  View Coordination

 Aesthetics

 Extensibility
  Architecture- Visualization & Evaluation
 Fidelity/Faithfulness to model (adherence)

Unit-3  Stick to the specifications

Architecture  Reuse architecture wherever possible
description,
documentati  Annotations and labelling
on and (meaningful)

Evaluation  Documentation about the model

 Innovate and enhance models

  Architecture- Visualization & Evaluation
 Consistency

Unit-3  Maintain consistency of the model

Architecture  Coordination expected throughout
description, (ideation to deployment)
documentati
 Peer to Peer consistency of model
on and
Evaluation  Master Slave consistency

 Push

 Pull
  Architecture- Analysis

Unit-3 8 Dimensions of Architecture

Analysis
Architecture
description,
documentati
on and
Evaluation
  Architecture- Analysis- Challenges

Unit-3
Architecture
description,
documentati
on and
Evaluation Ex: without typecast – data type mismatches in variables
can cause inconsistencies
  Architecture- Analysis- Scope

 Component level analysis

Unit-3  Connector level analysis
Architecture  System level analysis

description,  Sub system level analysis

documentati  Data exchange level

on and  Ex: Power plant various units and sub systems ( Coal handling
Evaluation unit, Boiler unit, Turbines subsystem and the digital info
exchange for operational management)
  Architecture- Analysis- Formalism
Unit-3
Architecture  Formal (notations) – high precision and expressivity (triplets in
a knowledge graph)
description,
documentati  Semi-Formal – moderate precision and expressivity
on and
Evaluation  Informal – very less precision and expressivity
  Architecture- Analysis- Techniques

 Static analysis techniques [syntax focused]

Unit-3
Architecture  Dynamic analysis techniques [ implementation focused]
description,
documentati  Scenario based analysis techniques [ impact focused]

on and
Evaluation  Ex: in Radiology department what if a machine is idle or shut
down for long? Impact to hospitals? Impact to patients?
 Solution; Preventive and periodic maintenance of assets
  Architecture- Analysis- Summary

Unit-3
Architecture
description,
documentati
on and
Evaluation
  ATAM- Architecture Trade off Analysis Method

 Business drivers and software architecture

Unit-3
Architecture
description,
documentati
on and
Evaluation
  ATAM- Architecture Trade off Analysis Method

 Business drivers and software architecture

Unit-3
Architecture
description,
documentati
on and
Evaluation
  Implementation
 Crucial phase in Software Architecture

Requirements thru Architecture design -> the final outcome will

be tested during implementation phase only
Unit-3 We have earlier discussed on software qualities, rubric and
Architecture evaluation criteria

description, Mapping -> Architecture implementation

documentati
Get everything in working mode -- Connectors, components, high
on and level programming languages, component interactions, facing and
Evaluation managing the constraints, reusable libraries, development
environment etc.

Architecture Framework to make implementation happen

  Implementation
 Crucial phase in Software Architecture

Requirements thru Architecture design -> Traceability or

Mapping
Unit-3
Architecture
description,
documentati
on and
Evaluation
  Implementation
 Crucial phase in Software Architecture

Requirements thru Architecture design -> Traceability or

Mapping
Unit-3
Architecture
description,
documentati
on and
Evaluation
  Implementation
 Crucial phase in Software Architecture

Requirements thru Architecture design -> Traceability or

Mapping
Unit-3
Architecture
description,
documentati
on and
Evaluation
Traceability or Mapping therefore has to take care of
requirements to implementation across components,
connectors, interactions, behaviours, stakeholders
communication and satisfaction
  Implementation
 Crucial phase in Software Architecture
Requirements thru Architecture design -> Traceability or
Mapping

Unit-3
Architecture
description,
documentati
on and
Evaluation
  Final phase - Deployment and Mobility –Evaluation
[Software]

Unit-3
Architecture
description,
documentati
on and
Evaluation
  6 Thinking hats

Learning
Zone
  6 Thinking hats

 Scenario:

Learning  Setting up an innovation lab facility at CSE department, SSN

 Let us discuss architecture blue-print
Zone  Stakeholders involved (incl.SSN facility chief, approvals from
HoD, Principal etc)