BIRLA INSTITUTE OF TECHNOLOGY & SCIENCE, PILANI

WORK INTEGRATED LEARNING PROGRAMMES

COURSE HANDOUT

Part A: Content Design

Course Title Software Architectures
Course No(s) SE ZG651/ SS ZG653
Credit Units 5
Course Author Harvinder S Jabbal
Version No 1.4
Date

Course Objectives:
No Course Objective

CO1 To enable software engineers to architect software systems using industry best practices

CO2 To enable project managers to understand techniques of software architecture, and help them
take appropriate decisions

CO3 To enable software professionals to take up research activities in the domain of software
architecture

Learning Outcomes:

No Learning Outcome

LO1 Ability to identify architecturally significant requirements and apply appropriate tactics to
address them

LO2 Ability to determine appropriate architecture patterns for given requirements

LO3 Ability to document architecture that meets the needs of stakeholders

LO4 Ability to analyse architecture and determine its appropriateness given the requirement and
determine risks

LO5 Awareness of best practices in design of cloud based applications, distributed applications and
mobile applications

LO6 Awareness of new technologies and their architecture and understanding of situations when to
use these technologies

LO7 Ability evaluate the cost and benefit of different architecture options to aid in decision making

Text Books:
T1 Software Architecture in Practice, Third Edition, Len Bass, Paul Clements, Rick Kazman, Pearson
2013 ISBN:978-93-325-0230-7
 T2 Essential Software Architecture, Second Edition, Ian Gorton, Springer 2011
ISBN:9783642191756

Reference Material:
R1 Software Modelling and Design, Hassan Gomaa, Cambridge University Press 2011,
ISBN:9780521764148
R2 Microsoft Application Architecture Guide, Second Edition, Microsoft 2009, ISBN:
9780735627109 [Availability: Online Free]
R3 Enterprise Architecture at Work: Modelling, Communication and Analysis, Third Edition, Marc
Lankhorst et al., Springer 2013, ISBN:9783642296505
R4 Architecting for the cloud:

Developing Multi-tenant Applications for the Cloud on Microsoft Windows Azure, Third Edition,
Microsoft 2012, ISBN:978-1-62114-023-8 [Availability: Online Free]
R5 Architecting for the Cloud
Amazon Web Services – Architecting for the Cloud: Best Practices, January 2011, Jinesh
Varia [Availability: Online Free]
https://media.amazonwebservices.com/AWS_Cloud_Best_Practices.pdf

DZone’s Guide to Building and deploying applications on the cloud

https://dzone.com/guides/building-and-deploying-applications-on-the-cloud
R6 Architecting for mobile
 https://magora-systems.com/mobile-app-development-architecture/
 https://www.intellectsoft.net/blog/mobile-app-architecture/
 https://www.uxpin.com/studio/blog/successful-mobile-applications-ui-design-patterns/
 https://www.smashingmagazine.com/2018/02/comprehensive-guide-to-mobile-app-
design/
 Architecting Mobile Solutions for the Enterprise – Dino Esposito, 2012, Microsoft Press,
ISBN: 978-0-7356-6303-2
R7 Identifying Architecturally Significant Functional Requirement
Research paper by TCS –
https://www.researchgate.net/publication/278242211_What_You_Ask_is_What_You_Ge
t_Understanding_Architecturally_Significant_Functional_Requirements

R8 ATAM case study – Rockwell Collins – CAAS – Common Avionics Architecture System

Video: https://youtu.be/da9MHLeTwvY
Product description:
https://www.rockwellcollins.com/Products_and_Services/Defense/Avionics/Integrated_Cockpit_
Solutions/Common_Avionics_Architecture_System.aspx
Rockwell Collins case study:
https://resources.sei.cmu.edu/asset_files/TechnicalNote/2003_004_001_14150.pdf

R9 ATAM case study: Battlefield Control System:

https://resources.sei.cm u.edu/asset_files/TechnicalReport/2000_005_001_13706.pdf

R10 Serverless architecture:

 https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
 https://docs.microsoft.com/en-us/azure/architecture/reference-
architectures/serverless/web-app

Container technology: https://www.cio.com/article/2924995/what-are-containers-and-why-do-

you-need-them.html
 Caching: https://aws.amazon.com/caching/ , https://aws.amazon.com/caching/implementation-
considerations/

Failure management in distributed systems:

 https://docs.microsoft.com/en-us/azure/architecture/guide/design-principles/self-healing
 https://dzone.com/articles/microservices-in-practice-1

R11 Technology topics

Technologies: https://docs.microsoft.com/en-us/azure/architecture/

NoSQL databases
https://www.dataversity.net/a-brief-history-of-non-relational-databases/#
https://www.couchbase.com/resources/why-nosql
https://www.thoughtworks.com/insights/blog/nosql-databases-overview
Big data analytics
Data mining & analytics: https://www.educba.com/data-mining-vs-data-analysis/
Technologies: https://www.edureka.co/blog/top-big-data-technologies/
Tools: https://www.guru99.com/big-data-analytics-tools.html
Use cases: https://www.datamation.com/big-data/big-data-use-cases.html
Case studies: https://data-flair.training/blogs/big-data-case-studies/
https://businessesgrow.com/2016/12/06/big-data-case-studies/
Hadoop
https://www.mssqltips.com/sqlserverauthor/77/dattatrey-sindol/
https://en.wikipedia.org/wiki/Apache_Hadoop
https://mapr.com/products/apache-hadoop/
https://www.sas.com/en_in/insights/big-data/hadoop.html
Real time analytics
https://www.sisense.com/glossary/real-time-analytics/
https://searchcustomerexperience.techtarget.com/definition/real-time-analytics
https://www.scnsoft.com/blog/real-time-big-data-analytics-comprehensive-guide
Spark
https://spark.apache.org/streaming/
https://databricks.com/glossary/what-is-spark-streaming
Use cases: https://www.qubole.com/blog/apache-spark-use-cases/
Machine learning
https://docs.microsoft.com/en-us/azure/architecture/data-guide/big-data/machine-learning-
at-scale
Primer: https://www.sas.com/content/dam/SAS/en_us/doc/whitepaper1/machine-learning-
primer-108796.pdf

Steps: https://towardsdatascience.com/6-important-steps-to-build-a-machine-learning-
system-d75e3b83686
Blockchain
Introduction: https://www.pwc.co.uk/financial-services/fintech/assets/blockchain-an-
intro.pdf
Blockchain at Maersk: https://www.computerworld.com/article/3298522/ibm-maersk-
launch-blockchain-based-shipping-platform-with-94-early-adopters.html
Security
OpenId: https://en.wikipedia.org/wiki/OpenID
OAuth: https://tools.ietf.org/html/draft-ietf-oauth-use-cases-01#section-2.1
https://www.csoonline.com/article/3216404/what-is-oauth-how-the-open-
authorization-framework-works.html
De-militarized zone: https://searchsecurity.techtarget.com/definition/DMZ
Firewall:
https://www.cio.com.au/article/365101/top_seven_firewall_capabilities_effective_
application_control/
https://www.fortinet.com/products/next-generation-firewall.html#services
https://www.securedgenetworks.com/blog/11-Features-to-Look-for-in-Your-Next-
 Generation-Firewall
LDAP: https://stackoverflow.com/questions/239385/what-is-ldap-used-for
Integration strategies:
Book ‘Enterprise Integration Patterns’ - Gregor Hohpe and Bobby Woolf
IoT
https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/iot/

R12 Technology trends:

https://www.thoughtworks.com/radar
https://www.infoq.com/
https://www.developertoarchitect.com/
Micro-frontends: https://martinfowler.com/articles/micro-frontends.html
R13 Transitioning from Developer to Architect: https://www.youtube.com/watch?v=JV8HNsFWHD4

R14 Case studies

Architecture patterns – Case studies

 SoA at CIGNA
 SaleForce.com
 SoA at TripAdvisor
 Micro-Services at Danske Bank

Case studies.zip

Architecture evaluation and revision – Case study

Scaling hospital call

center
Scaling, caching, reliability case study: Netflix

http://highscalability.com/blog/2017/12/11/netflix-what-happens-when-you-press-
play.html

R15 Microservices in practice: https://dzone.com/articles/microservices-in-practice-1

R16 Tactics to address different quality attributes: https://docs.microsoft.com/en-

us/azure/architecture/patterns/category/availability
Content Structure

Module List of Topic Title Reference Recorded Lectures

No

M1 Introduction to Software Architecture T1 - 01, 02, RL 1.2 A Brief History of Software

 What is Software Architecture? 03, 24 Architecture
 Definitions of Software Architecture RL 1.3 Introduction to the Styles,
 Architecture Structure and Patterns Views and Three structures
 Good architecture
 Importance of Software architecture
 Contexts of Software architecture
 Architecture competence

M2 Software Quality Attributes T1 - 04, 05, RL 3.1 Quality classes, Quality

 Understanding Quality Attributes 06, 07, 08, attribute, quality attribute scenario
 Interoperability 09, 10, 11, and architectural tactics
 Testability 12 RL 4.1 Usability and its tactics
 Usability RL 4.2 Availability
 Performance R16 RL 5.1 Modifiability
 Scalability RL 5.2 Performance
RL 6.1 Security
 Modifiability
RL 6.2 Testability
 Security
RL 6.3 Interoperability
 Availability
 Integration
 Other Quality Attributes
 Design Trade-Offs

M3 Capturing Architecturally Significant Requirements T1 - 15, 16, RL 19.1 Architecture and

 Challenges in identifying ASRs 17 Requirements
 Quality attribute Workshop R7 RL 19.2 Designing the Architecture
o Understanding business goals from RL 8.2 Introducing Agile
Sponsors methodology
o Identifying architectural drivers
o Understanding Scenarios for each
architectural driver via brainstorming
with stakeholders
o Prioritizing scenarios
o Building a Utility tree

Architecture design
 Design strategy
 Steps of Attribute-Driven design
 Architecting in Agile projects

M4 Documenting Software Architecture T1 – 18 RL 7.1 Introduction to OO Design

 Importance of architecture documentation RL 7.2 Introduction to UML
 Architecture Views RL 8.1 Documenting Architecture
 Quality attribute views – Security view, using UML
Communication view, Reliability view RL 8.3 Rational Unified Process
 Combining Views RL 20.1 Designing and
 Philippe Kruchten’s 4+1 view Documenting the Architecture # 2
 Documentation Package
M5 Layered architecture: Guidelines for different layers R2 Recording not available
 Presentation
 Business
 Data Layer
 Service

Architecture evaluation (ATAM) T1 – 21

 Factors for evaluation R8
 Trade off analysis R9
 Evaluation method

Architecture Conformance techniques during

implementation T1 - 20

Architecture & Testing

T1 - 19
Architecture Reconstruction
 Raw view extraction
T1 – 20
 View fusion
 Finding violations

M6 Architectural patterns T1 RL 9.1 Pattern Definition,

 Layered Classification, Category and Intro
 MVC R14 to Layering
 Publish-subscribe RL 9.2 Layering Pattern
 Pipe & Filter RL 10.1 Pipe and Filter
 Service Oriented Architecture and Micro- RL 10.2 Blackboard
services RL 11.1 Distributed System
RL 12.1, 12.2 MVC Intro and detail
RL 13.1, 13.2 Microkernel
RL 13.3 Reflection

M7 Architectural patterns T1
 Broker
 Client server R14
 Peer-to-Peer
 Shared data
 Map-reduce
 Multi-tier
 M8 Integration strategies T1 RL 17.1 Introduction and
File transfer, Messaging, RPC, WebSockets, Virtualization basic
API Gateways RL 17.2 IAAS and Data storage
RL 18.1 Quality attribute revisited
Architecting for Cloud RL 18.2 Multi-Tenant Architecture,
 Benefits of Cloud based approach R4 Micro Services, CAP Theorem
 Developing Multi-tenant Applications for the R5
Cloud
 Amazon Web Services tools
 Trends in Cloud app development –
languages, DB, Micro-services, CI / CD

Technologies R10
 Distributed Cache
 Containers
 Serverless architecture
R10
Failure management
 CAP theorem
 Failure management in distributed systems

M9.1 Architecting for Mobile R6 Recording not available

 Types of mobile applications: native, cross
platform, web app
 Design considerations
 Android Application components
 Patterns in Mobile Application
o Store locally, sync later
o Responsive design
o UI design patterns

M9.2 New technologies & their architecture R11 Recording not available
R12
Use cases and architecture of:

 Big data
o NoSQL Databases
o Hadoop
o MapReduce
o Real-time analytics
 Artificial intelligence & Machine Learning
 Block Chain
 IoT
 Security: AuthID, OAuth

M10.1 Economic analysis of architectures T1

 Decision-making context
 Basis for economic analysis
 Cost Benefit Analysis Method

M10.2 Recent developments and Emerging trends R12

 WebAssembly
 Service mesh
 Edge computing
 Part B: Contact Session Plan
Academic Term Second Semester 2023-2024

Course Title Software Architectures

Course No SE ZG651/ SS ZG653

Lead Instructor Harvinder S Jabbal

Version 1.4.1

Contact Session-1, Module M1 Introduction (July 22)

Time Type Description References
Pre-CS-1 RL 1.2 A Brief History of Software Architecture

During CS-1 CS-1 Introduction

Post-CS-1 T1 - 01,

Contact Session-2, Module M1 Architectural Context (July 29)

Time Type Description References
Pre-CS-2 RL1.1 RL 1.3 Introduction to the Styles, Views and Three structures

During CS-2 CS-2 CS02A_Architectural Context

CS02B_What Is Software Architecture

Post-CS-2 T1 - 02, 03, 24

Contact Session-3, Module M2 Quality Attributes (Aug 5)

Time Type Description References
Pre-CS-3 RL 3.1 Quality classes, Quality attribute, quality attribute scenario
and architectural tactics
RL 4.1 Usability and its tactics
RL 4.2 Availability
During CS-3 CS-3 Quality classes, Quality attribute, quality attribute scenario
and architectural tactics
Usability and its tactics
Availability
Post-CS-3 R16 Tactics to address different quality attributes:
https://docs.microsoft.com/en-
us/azure/architecture/patterns/category/availability
T1 – 04, 11, 5

Contact Session-4, Module M2 Quality Attributes (Aug 12)

Time Type Description References
Pre-CS-4 RL 5.1 Modifiability
RL 5.2 Performance
RL 6.1 Security
During CS-4 CS-4 Modifiability
Performance
Security

Post-CS-4 T1 - 07, 08, 09

Contact Session-5, Module M2 Quality Attributes (Aug 19)e

Time Type Description References
Pre-CS-5 RL 6.2 Testability
RL 6.3 Interoperability

During CS-5 CS-5 Testability

Interoperability

Post-CS-5 T1 - 06, 10, 12

Contact Session-6, Module M3/M4 Architectural Requirement Design/ Documentation (Aug 26)
Time Type Description References
Pre-CS-6 RL 19.1 RL 19.1 Architecture and Requirements
RL 19.2 RL 19.2 Designing the Architecture
RL 8.2 RL 8.2 Introducing Agile methodology
RL 7.1 RL 7.1 Introduction to OO Design
RL 7.2 RL 7.2 Introduction to UML
RL 8.1 RL 8.1 Documenting Architecture using UML
RL 8.3 RL 8.3 Rational Unified Process
RL 20.1 RL 20.1 Designing and Documenting the Architecture # 2
During CS-6 CS-6 Capturing Architecturally Significant Requirements
Architecture design
Documenting Software Architecture
Post-CS-6 T1 - 15, 16, 17
R7 Identifying Architecturally Significant Functional
Requirement
T1 – 18
Contact Session-7, Module M5 ATAM (Sept 2)
Time Type Description References
Pre-CS-7

During CS-7 CS-7 Layered architecture: Guidelines for different layers

Architecture evaluation (ATAM)

Post-CS-7 T1 – 21
R2 Microsoft Application Architecture Guide, Second
Edition, Microsoft 2009, ISBN: 9780735627109 [Availability:
Online Free]
R8 ATAM case study – Rockwell Collins – CAAS –
Common Avionics Architecture System
R9 ATAM case study: Battlefield Control System:

Contact Session-8, Module M5 Conformance, Testing, Reconstruction (Sept 9)

Time Type Description References
Pre-CS-8

During CS-8 CS-8 Architecture Conformance techniques during implementation

Architecture & Testing
Architecture Reconstruction
Post-CS-8 T1: 19,20

MID – TERM EXAMINATION SYLLABUS END HERE

Contact Session-9, Module M6 Patterns (Sept 16)
Time Type Description References
Pre-CS-9 RL 9.1 Pattern Definition, Classification, Category and Intro to
Layering

During CS-9 CS-1 Nomenclature of Architectural Patterns

Post-CS-9 T1
R14 Architecture patterns – Case studies

Contact Session-10, Module M6 Patterns (Sept 30)

Time Type Description References
Pre-CS-10 RL 9.2 RL 9.2 Layering Pattern
RL 10.1 RL 10.1 Pipe and Filter
RL 10.2 RL 10.2 Blackboard

During CS- CS-1 Layered

10 MVC
SOA
Post-CS-10 T1
R14 Architecture patterns – Case studies

Contact Session-11, Module M7 Patterns (Oct 14)

Time Type Description References
Pre-CS-11 RL 11.1 RL 11.1 Distributed System
RL 12.1, 12.2 RL 12.1, 12.2 MVC Intro and detail
RL 13.1, 13.2 RL 13.1, 13.2 Microkernel
RL 13.3 RL 13.3 Reflection
During CS- CS-11 Adaptable
11 Sublisher Subscriber
Shared Data
Map Reduce
Multi Toer
Post-CS-11 T1
R14 Architecture patterns – Case studies
Contact Session-12, Module M8 Cloud (Oct 21)
Time Type Description References
Pre-CS-12 RL 17.1 RL 17.1 Introduction and Virtualization basic
RL 17.2 RL 17.2 IAAS and Data storage
RL 18.1 RL 18.1 Quality attribute revisited
RL 18.2
RL 18.2 Multi-Tenant Architecture, Micro Services, CAP
Theorem
During CS- CS-12 Integration strategies
12 Architecting for Cloud
Best Practices
The Road Ahead.
Post-CS-12 T1;
R4 Architecting for the cloud;
R5 Architecting for the Cloud;
R10 Serverless architecture

Contact Session-13, Module M9 Mobile Phone Architecture (Oct 28)

Time Type Description References
Pre-CS-13

During CS- CS-1 Architecting for Mobile

13
Post-CS-13 R6 Architecting for mobile

Contact Session-14, Module M9 Big data, Analytics, IoT, Machine Learning (Nov 4)
Time Type Description References
Pre-CS-14

During CS- CS-14 New technologies & their architecture; Big Data; NoSQL;
14 Security; Machine Learning.

Post-CS-14 R11 Technology topics.

R12 Technology trends

Contact Session-15, Module M10 Management & Governance (Nov 11)

Time Type Description References
Pre-CS-15 RL1.1

During CS- CS-15 Economic analysis of architectures; Management Practices;

15 Recent developments and Emerging trends

Post-CS-15 R12 Technology trends

Contact Session-16, Module M11 CBAM (Nov 18)
Time Type Description References
Pre-CS-16 RL1.1

During CS- CS-16 Economic analysis of architectures

16 Cost Benefit Analysis

Post-CS-16 T1

Course Contents

Mid sem exam syllabus: Modules 1 to 5

Compre exam syllabus: Modules 1 to 10

Contact sessions:

For each module there will be a contact session. The contact session is expected to cover:

 Key concepts in the module

 Examples / case studies
 Experience sharing from participants
 Exercises
Students are expected to go through the reference material and / or recorded lectures, before coming to the
class.

Students may be given home work at the end of each contact session.

Assignments:

Assignment #1 (5% weight). Each Student to submit individually.

Objective: To get familiar with the software architecture basics.

Activity:

1. Choose an existing system from your workplace

2. Understand the purpose (goal) of the system & its key requirements
3. Study the architecture and understand the tactics used

Document your work in the following format in PPT:

1. Purpose of the system (Goal)

2. Key requirements of the system – functional & non-functional
3. Utility tree of Architecturally Significant Requirements (ASR)
4. Tactics used to achieve the top 5 ASRs
5. Software Architecture diagram – Context diagram, Module decomposition, Component &
Connection diagram, Deployment diagram
6. Description of how the system works
7. Key learnings (one slide)
Assignment #2 (10% weight). Each Student to submit individually.

Objective: To gain experience in architecting real life applications in domains such as Retail, Transportation,
Healthcare, Hospitality, etc. Example systems: Swiggy, Uber, an IoT system to monitor health of industrial air
conditioners.

Activity

1. Identify top 3 Architecturally Significant Requirements (ASRs) and write them in the form of a Utility
tree. Why are these architecturally significant?
2. Describe in detail, the tactics you recommend for each ASR. For example, if caching is a tactic you
recommend, please mention what you will cache, what tool you would use, how it will work, etc.
3. Draw 2 software architecture diagrams – component & connection view and deployment view – to
understand how the system works.
4. Indicate important messages between components by labelling the connections in the C&C view. Also
indicate the communication method used.
5. Draw sequence diagram for one major scenario (use case). Mention the scenario.
6. State the architecture patterns used. Explain, where in the architecture, these patterns have been used.
7. What did you learn by doing this assignment? Mention 3 key learnings. One slide per person.

Evaluation criteria:

a) Easy-to-understand diagrams
b) Clarity of description
c) Correctness of work products

Evaluation Components

No Name Type Duration Weight Day, Date, Session, Time

EC-1 Quiz-I Online 5% February 19-28, 2024
Quiz-II Online 5% March 19-28, 2024
Quiz-III Online 5% April 19-28, 2024
Assignment I Online 5% TBA
Assignment-II Online 10% Individual Submission
TBA
Group Discussion
TBA
EC-2 Mid-Semester Exam Closed Book 2 Hours 30% Saturday, 16/03/2024 (FN)
EC-3 Comprehensive Exam Open Book 2½ 40%
Saturday, 18/05/2024 (FN)
Hours
Note - Evaluation components can be tailored depending on the proposed model.

Syllabus for exams:

 Syllabus for Mid-Semester exam (Closed Book): Modules 1-5
 Syllabus for Comprehensive exam (Open Book): Modules 1-10
Evaluation Guidelines:
1. For Closed Book tests: No books or reference material of any kind will be permitted. Laptops/Mobiles of any
kind are not allowed. Exchange of any material is not allowed.
2. For Open Book exams: Use of prescribed and reference text books, in original (not photocopies) is permitted.
Class notes/slides as reference material in filed or bound form is permitted. However, loose sheets of paper
will not be allowed. Use of calculators is permitted in all exams. Laptops/Mobiles of any kind are not allowed.
Exchange of any material is not allowed.
3. If a student is unable to appear for the Regular Test/Exam due to genuine exigencies, the student should
follow the procedure to apply for the Make-Up Test/Exam. The genuineness of the reason for absence in the
Regular Exam shall be assessed prior to giving permission to appear for the Make-up Exam. Make-Up
Test/Exam will be conducted only at selected exam centres on the dates to be announced later.
It shall be the responsibility of the individual student to be regular in maintaining the self-study schedule as given in
the course handout, attend the lectures, and take all the prescribed evaluation components such as Assignment/Quiz,
Mid-Semester Test and Comprehensive Exam according to the evaluation scheme provided in the handout.