0% found this document useful (0 votes)
461 views

IT 301 Software Architecture and Design Patterns PDF

This document describes a course on software architecture and design patterns. The course is a 3 credit hour course introduced in 2016. It aims to teach students basic software concepts, the software design process, and different architectural styles and patterns. The syllabus covers topics like UML diagrams, architectural styles, and design patterns. Students will learn to design UML diagrams, identify appropriate architectural styles and patterns, and create flexible software architectures. The course is divided into 6 modules over 15 weeks and will be evaluated through internal exams, assignments, and an end semester exam.

Uploaded by

Ashwin Mohan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
461 views

IT 301 Software Architecture and Design Patterns PDF

This document describes a course on software architecture and design patterns. The course is a 3 credit hour course introduced in 2016. It aims to teach students basic software concepts, the software design process, and different architectural styles and patterns. The syllabus covers topics like UML diagrams, architectural styles, and design patterns. Students will learn to design UML diagrams, identify appropriate architectural styles and patterns, and create flexible software architectures. The course is divided into 6 modules over 15 weeks and will be evaluated through internal exams, assignments, and an end semester exam.

Uploaded by

Ashwin Mohan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Course Course Name L-T-P- Year of

code Credits Introduction


IT301 Software Architecture and Design Patterns 3-1-0 - 4 2016
Prerequisite : Nil
Course Objectives
 To introduce to the students the basic knowledge of software, software
development process and the concepts of software design principles.
 Gain knowledge on how to design UML diagrams.
 To impart knowledge on the different architectural styles and architectural patterns
for the software.
Syllabus
Introduction to the concepts of Software and the software design process, Process models,
Importance of software architecture, Software design principles, Introduction to UML diagrams,
UML diagram preparation for various case studies. Introduction to Software Architectural styles,
Software Architecture patterns, Evaluation of architectural design.
Expected outcome
The students will be able to
i. Design UML diagram for the software.
ii. Identify and apply appropriate architectural styles and architectural design pattern
for the software.
iii. Create flexible, reusable and efficient architecture for software.

Reference Books:
1. Eric J. Braude , Software Design, John Wiley and Sons.
2. Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides : Design Patterns:
Elements of Reusable Object-Oriented Software, Addison – Wesley, 1994
3. James Rumbaugh, Object Oriented Modeling and Design, Prentice Hall India
4. Len Bass, Paul Clements, Rick Kazman, Software Architecture in Practice (2nd Ed.),
Pearson
5. Mary Shaw & David Garlan, Software Architecture – Perspectives on an emerging
discipline, Pearson, 1996
6. Roger S.Pressman, Software Engineering – A Practitioner’s approach, 8th edition(2014),
McGraw Hill Education
Course Plan
Module Contents Hours Sem.
Exam
Marks
The Nature of Software – Defining software, Software
Application domains. Software Engineering. The Software
Process, Process Models: - Water fall model, Incremental
model, Prototyping model, RAD, Spiral model and Agile
I 8
Development. (Brief introduction of Agile Development).
What is Software Architecture? Why is software architecture 15%
important? Role of software architect.
Software Design principles – Correctness and Robustness –
II Flexibility, Reusability and Efficiency – Tradeoffs among 7 15%
robustness, flexibility, reusability and efficiency
FIRST INTERNAL EXAM
Introduction to UML diagrams – Use case diagrams, Class
diagrams, Sequence diagrams, Activity diagrams, State 8
III Transition diagram, Deployment diagram. 15%
Case study discussion on UML diagrams – Group
4
presentation by students on different case studies.
IV Software architectural styles - pipes & filters, layered, event-
based, data-centered, interpreter, MVC, message dispatcher, 9 15%
multi-tier distributed
SECOND INTERNAL EXAM
What is a design pattern? Creational patterns – Factory,
V Abstract Factory, Prototype and Singleton. Structural patterns 9 20%
– Composite, Decorator, Adapter, Façade and Flyweight.
Behavioral patterns- Chain of responsibility, Command,
VI Interpreter, Mediator, State, Template and Observer. 9 20%
Evaluation of architectural design - ATAM
END SEMESTER EXAM

QUESTION PAPER PATTERN

Maximum Marks: 100 Exam Duration: 3 hours

The question paper shall consist of Part A, Part B and Part C.

Part A shall consist of three questions of 15 marks each uniformly covering Modules I and II.
The student has to answer any two questions (15×2=30 marks).
Part B shall consist of three questions of 15 marks each uniformly covering Modules III and IV.
The student has to answer any two questions (15×2=30 marks).
Part C shall consist of three questions of 20 marks each uniformly covering Modules V and VI.
The student has to answer any two questions (20×2=40 marks).

Note : Each question can have a maximum of 4 subparts, if needed

You might also like