SE7301 SOFTWARE DESIGN PATTERNS SYLLABUS FOR ME SOFFWARE ENGINEERING 3RD SEMESTER

 ANNA UNIVERSITY, CHENNAI

REGULATIONS - 2013
SE7301 SOFTWARE DESIGN PATTERNS SYLLABUS

ME 3RD SEM SOFFWARE ENGINEERING SYLLABUS

SE7301 SOFTWARE DESIGN PATTERNS SYLLABUS

OBJECTIVES: 

• How to add functionality to designs while minimizing complexity. 
• What code qualities they need to maintain to keep code flexible. 
• Understanding the common design patterns. 
• Identifying the appropriate patterns for design problems. 
• Refactoring the badly designed program properly using patterns. 

UNIT I INTRODUCTION

Introduction – Design Patterns in Smalltalk MVC – Describing Design patterns –Catalog of Design Patterns- Organizing the Catalog –How Design Patterns Solve Design Problems – How to select a Design Pattern – How to use a Design Pattern – What makes a pattern? – Pattern Categories – Relationship between Patterns – Patterns and Software Architecture 

UNIT II DESIGN PATTERNS FROM POSA1

Whole Part – Master Slave –Command Processor – View Handler – Forward Receiver – Client Dispatcher Server 

UNIT III CREATIONAL AND STRUCTURAL DESIGN PATTERNS

Abstract Factory - Factory Method – Prototype - Singleton – Builder Adapter Pattern – Decorator – Façade – Proxy - Bridge 

UNIT IV BEHAVIORAL DESIGN PATTERNS AND IDIOMS

Chain of Responsibility – Mediator – Observer – Strategy– Memento Idioms – Pattern Systems 

UNIT V CASE STUDY

Case Study Designing a Document Editor - What to expect from Design Patterns – A brief History of Design Patterns – The Pattern Community – Where will Patterns Go? – The Past, Present and the Future of Patterns - Anti Patterns 

TOTAL: 45 PERIODS 

OUTCOMES: 

• Be able to Design and implement codes with higher performance and lower complexity 
• Be aware of code qualities needed to keep code flexible 
• Understand core design principles and be able to assess the quality of a design with respect to these principles. 
• Be capable of applying these principles in the design of object oriented systems. 
• Demonstrate an understanding of a range of design patterns. Be capable of comprehending adesign presented using this vocabulary. 
• Be able to select and apply suitable patterns in specific contexts. 
• Understand and apply refactoring techniques in the context of design patterns. 

REFERENCES: 

1. Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, “Design patterns: Elements of Reusable object-oriented software”, Addison-Wesley, 1995. 

2.Frank Bachmann, Regine Meunier, Hans Rohnert “Pattern Oriented Software Architecture” – Volume 1, 1996. William J Brown et al., "Anti-Patterns: Refactoring Software, Architectures and Projects in Crisis", John Wiley, 1998