Software Architecture and Design Patterns Detailed Syllabus for Computer Science and Engineering M.Tech first year first sem is covered here. This gives the details about credits, number of hours and other details along with reference books for the course.
The detailed syllabus for Software Architecture and Design Patterns M.Tech 2017-2018 (R17) first year first sem is as follows.
M.Tech. I Year I Sem.
Course Objectives: After completing this course, the student should be able to:
- To understand the concept of patterns and the Catalog.
- To discuss the Presentation tier design patterns and their affect on: sessions, client access, validation, and consistency.
- To understand the variety of implemented bad practices related to the Business and Integration tiers.
- To highlight the evolution of patterns.
- To how to add functionality to designs while minimizing complexity
- To understand what design patterns really are, and are not
- To learn about specific design patterns.
- To learn how to use design patterns to keep code quality high without overdesign.
UNIT – I : Envisioning Architecture
The Architecture Business Cycle, What is Software Architecture, Architectural patterns, reference models, reference architectures, architectural structures and views. Creating an Architecture Quality Attributes, Achieving qualities, Architectural styles and patterns, designing the Architecture, Documenting software architectures, Reconstructing Software Architecture.
UNIT – II : Analyzing Architectures
Architecture Evaluation, Architecture design decision making, ATAM, CBAM. Moving from one system to many Software Product Lines, Building systems from off the shelf components, Software architecture in future.
UNIT – III : Patterns
Pattern Description, Organizing catalogs, role in solving design problems, Selection and usage. Creational and Structural patterns Abstract factory, builder, factory method, prototype, singleton, adapter, bridge, composite, façade, flyweight.
UNIT – IV : Behavioral patterns
Chain of responsibility, command, Interpreter, iterator, mediator, memento, observer, state, strategy template method, visitor.
UNIT – V : Case Studies
A-7E – A case study in utilizing architectural structures, The World Wide Web – a case study in interoperability, Air Traffic Control – a case study in designing for high availability, Celsius Tech – a case study in product line development,
TEXT BOOKS:
- Software Architecture in Practice, second edition, Len Bass, Paul Clements & Rick Kazman, Pearson Education, 2003.
- Design Patterns, Erich Gamma, Pearson Education, 1995.
REFERENCE BOOKS:
- Beyond Software architecture, Luke Hohmann, Addison wesley, 2003.
- Software architecture, David M. Dikel, David Kane and James R. Wilson, Prentice Hall PTR, 2001
- Software Design, David Budgen, second edition, Pearson education, 2003
- Head First Design patterns, Eric Freeman & Elisabeth Freeman, O’REILLY, 2007.
- Design Patterns in Java, Steven John Metsker & William C. Wake, Pearson education, 2006
- J2EE Patterns, Deepak Alur, John Crupi & Dan Malks, Pearson education, 2003.
- Design Patterns in C#, Steven John metsker, Pearson education, 2004.
- Pattern Oriented Software Architecture, F. Buschmann & others, John Wiley & Sons.
For all other M.Tech 1st Year 1st Sem syllabus go to JNTUH M.Tech Computer Science and Engineering 1st Year 1st Sem Course Structure for (R17) Batch.
All details and yearly new syllabus will be updated here time to time. Subscribe, like us on facebook and follow us on google plus for all updates.
Do share with friends and in case of questions please feel free drop a comment.