H.M.S.

INSTITUTE OF TECHNOLOGY,TUMKUR
NH-4 Kesaramadhu Post, Kyathsandra , Tumkur- 572104. Karnataka

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

Department Computer Science & Engineering Course Type Core
Course Title Software architectures Course code 10IS81
L-T-P 4-0-0 Duration of exam 3 hours
Internals 25 Marks External 100 Marks
Name of the Faculty Dr. A. Vijayaraghavan Contact hours 52
Designation Professor & HOD Semester VIII

Pre Requisites:

 Software engineering
 Object oriented concepts
 UML design concepts

Course Outcomes (COs)

Co’s Description
CO1 : Able to understand the basic concepts of software architecture and software architecture
Business cycle.
CO2: Understand the various architectural styles with case studies
CO3: Define various quality attributes of software architecture and explain the techniques to achieve
them.
CO4: Understand the concepts of various architectural patterns and some design patterns.
CO5: Acquire solid foundation in the field of designing and documenting Software architecture

Mapping of Course Outcomes to Program Outcomes

PO’s A B C D E F G H I J K L
CO’s
CO 1 H M
CO2 L H H M
CO3 M L M L L
CO4 M H H M
CO 5 M H H M M M M H L

Assessment Methods

A. Continues
1. 3 internal Assessment Tests->[Average of Best 2 tests] Evaluated for 25 Marks
2. Assignments ->Encouragements
3. Seminars & Presentations ->Encouragements
B. Semester end assessment
Semester end examinations -> Evaluated for 100 Marks
 Lesson plan for Academic Year Feb 2018- June 2018

Topics
Sl. Teaching
DATE Topics planned for the session Covered
No Aids
1 5/2/18 UNIT 1: Introduction: Revision of concepts of software BB
engineering. Introduction about Software architecture,
2 6/2/18 Where do architectures come from? Software processes and
the architecture business cycle.
3 7/2/18 Software processes and the architecture business cycle.
4 8/2/18 What makes a “good” architecture? What software
architecture is and what it is not;
5 12/2/18 Other points of view, Architectural patterns, reference
models and reference architectures;
6 14/2/18 Importance of software architecture. Architectural
structures and views,
7 15/2/18 Classification of views.
8 19/2/18 UNIT 2: Architectural Styles and Case Studies:
Architectural styles: Definition and classification. Structure
of styles.
9 20/2/18 Pipes and filters. Data abstraction and object- oriented
organization; Event-based, implicit invocation;
10 21/218 Layered systems. Repositories, Interpreters, Process control.
11 22/2/18 Other familiar architectures; Heterogeneous architectures.
12 26/2/18 Case Studies: Keyword in Context.
13 27/2/18 Case Studies: Instrumentation software,
14 28/2/18 Case Studies: Mobile robotics.
15 1/3/18 Case Studies: Cruise control, Three Vignettes in mixed style.
16 5/3/18 Revision of Unit 1 and 2 extra
17 5/3/18 UNIT 3: Quality: Functionality and architecture;
Architecture and quality attributes.
18 6/3/18 System quality attributes; Quality attribute scenarios in
practice; Other system quality attributes
19 7/3/18 Availability Scenario, Modifiability Scenario
20 8/3/18 Usability Scenario, Performance Scenario
21 12/3/18 Security Scenario, Testability Scenario
22 13/3/18 Business qualities, Architecture qualities. Achieving Quality:
Introducing tactics.
23 14/3/18 Availability tactics; Modifiability tactics; Usability tactics
24 19/3/18 Performance tactics; Security tactics; Testability tactics.
25 20/3/18 Relationship of tactics to architectural patterns;
Architectural patterns and styles.
26 21/3/18 Revision of Unit 3. extra
27 21/3/18 Unit 4: Architectural Patterns – 1: Introduction;
28 22/3/18 From mud to structure.
29 26/3/18 From mud to structure.
 30 27/3/18 Pipes and Filters
31 28/3/18 Pipes and Filters
32 2/4/18 Blackboard
33 3/4/18 Revision of Unit 4
34 4/4/18 UNIT 5: Architectural Patte rns – 2 : Distributed Systems:
35 4/4/18 Broker
36 5/4/18 Model View Controller
37 9/4/18 Model View Controller
38 10/4/18 Presentation-Abstraction-Control.
39 11/4/18 Revision of unit 5
40 12/4/18 UNIT 6: Architectural Patte rns – 3 : Adaptable Systems:
41 12/4/18 Microkernel
42 19/4/18 Microkernel
43 23/4/18 Reflection
44 24/4/18 Revision of Model View Controller
45 25/4/18 UNIT 7: Some Design Patterns : Structural
decomposition:
46 26/4/18 Whole – Part, Organization of work
47 26/4/18 Master – Slave
48 26/4/18 Access Control
49 30/4/18 Proxy.
50 2/5/18 Revision of Unit 7 extra
51 3/5/18 UNIT 8: Designing and documentingSoftware
Architecture: Architecture in the life cycle; Designing the
architecture.
52 7/5/18 Forming the team structure; Creating a skeletal system.

53 8/5/18 Uses of architectural documentation; Views; Choosing

the relevant views;
54 8/5/18 Documenting a view; Documentation across views.
55 9/5/18 Revision of unit 8

Text Books:
1. Len Bass, Paul Clements, Rick Kazman: Software Architecture in Practice, 2nd Edition, Pearson Education,
2003. (Chapters 1, 2, 4, 5, 7, 9)
2. Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal: Pattern-Oriented
Software Architecture, A System of Patterns, Volume 1, John Wiley and Sons, 2007. (Chapters 2, 3.1 to 3.4)
3. Mary Shaw and David Garlan: Software Architecture- Perspectives on an Emerging Discipline, PHI, 2007.
(Chapters 1.1, 2, 3)
Reference Books: 1. E. Gamma, R. Helm, R. Johnson, J. Vlissides: Design PatternsElements of Reusable
Object-Oriented Software, Pearson Education, 1995.
Web Reference: http://www.hillside.net/patterns/

Signature of Staff Signature of HOD Signature of Principal