CS8592 – OBJECT ORIENTED ANALYSIS AND DESIGN Syllabus 2017 Regulation

0
2760

CS8592 – OBJECT ORIENTED ANALYSIS AND DESIGN Syllabus 2017 Regulation

OBJECT ORIENTED ANALYSIS AND DESIGN CS8592 – OBJECT ORIENTED ANALYSIS AND DESIGN Syllabus 2017 Regulation

CS8592                         OBJECT ORIENTED ANALYSIS AND DESIGN               L T P C                                                                                                                             3 0 0 3

OBJECTIVES:

  • To understand the fundamentals of object modeling
  • To understand and differentiate Unified Process from other approaches.
  • To design with static UML diagrams.
  • To design with the UML dynamic and implementation diagrams.
  • To improve the software design with design patterns.
  • To test the software against its requirements specification

UNIT I UNIFIED PROCESS AND USE CASE DIAGRAMS                                                                       9

Introduction to OOAD with OO Basics – Unified Process – UML diagrams – Use Case –Case study – the Next Gen POS system, Inception -Use case Modelling – Relating Use cases – include, extend and generalization – When to use Use-cases

UNIT II STATIC UML DIAGRAMS                                    9

Class Diagram–– Elaboration – Domain Model – Finding conceptual classes and description classes – Associations – Attributes – Domain model refinement – Finding conceptual class Hierarchies – Aggregation and Composition – Relationship between sequence diagrams and use cases – When to use Class Diagrams

UNIT III DYNAMIC AND IMPLEMENTATION UML DIAGRAMS                                                                       9

Dynamic Diagrams – UML interaction diagrams – System sequence diagram – Collaboration diagram – When to use Communication Diagrams – State machine diagram and Modelling –When to use State Diagrams – Activity diagram – When to use activity diagrams Implementation Diagrams – UML package diagram – When to use package diagrams – Component and Deployment Diagrams – When to use Component and Deployment diagrams

UNIT IV DESIGN PATTERNS                                           9

GRASP: Designing objects with responsibilities – Creator – Information expert – Low Coupling – High Cohesion – Controller Design Patterns – creational – factory method – structural – Bridge – Adapter – behavioural – Strategy – observer –Applying GoF design patterns – Mapping design to code

UNIT V TESTING                                                              9

Object Oriented Methodologies – Software Quality Assurance – Impact of object orientation on Testing – Develop Test Cases and Test Plans

TOTAL: 45 PERIODS

OUTCOMES:

At the end of the course, the students will be able to:

  • Express software design with UML diagrams
  • Design software applications using OO concepts.
  • Identify various scenarios based on software requirements
  • Transform UML based software design into pattern based design using design patterns
  • Understand the various testing methodologies for OO software

TEXT BOOKS:

  1. Craig Larman, ―Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development‖, Third Edition, Pearson Education, 2005.
  2. Ali Bahrami – Object Oriented Systems Development – McGraw Hill International Edition – 1999

REFERENCES:

  1. Erich Gamma, a n d Richard Helm, Ralph Johnson, John Vlissides, ―Design patterns: Elements of Reusable Object-Oriented Software‖, Addison-Wesley, 1995.
  2. Martin Fowler, ―UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third edition, Addison Wesley, 2003.

LEAVE A REPLY

Please enter your comment!
Please enter your name here