| PO1 | PO2 | PO3 | PO4 | PO5 | PO6 | PO7 | PO8 | PO9 | PO10 | PO11 | PO12 | PSO1 | PSO2 | PSO3 | ||
| K3 | K6 | K6 | K6 | K6 | K6 | K5 | K6 | |||||||||
| CO1 | K2 | 2 | 1 | 1 | 1 | |||||||||||
| CO2 | K4 | 3 | 2 | 2 | 2 | |||||||||||
| CO3 | K3 | 3 | 2 | 2 | 2 | |||||||||||
| CO4 | K4 | 3 | 2 | 2 | 2 | |||||||||||
| CO5 | K3 | 3 | 2 | 2 | ||||||||||||
| Score | 14 | 9 | 7 | 9 | ||||||||||||
| Course Mapping | 3 | 2 | 2 | 2 |
{{{credits}}}
| L | T | P | C |
| 3 | 0 | 0 | 3 |
- To understand and differentiate Unified Process from other approaches
- To understand object-oriented software design using UML’s static diagrams
- To understand software modeling using the UML’s dynamic diagrams
- To learn improving software design with design patterns
- To learn testing the software with its requirements specification.
{{{unit}}}
| UNIT I | DEVELOPMENT PROCESS & USE-CASE DIAGRAM (STATIC) | 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}}}
| UNIT II | UNIFIED PROCESS & CLASS DIAGRAM (STATIC) | 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}}}
| UNIT III | DYNAMIC & IMPLEMENTATION 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}}}
| UNIT IV | DESIGN PATTERNS | 9 |
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}}}
| UNIT V | TEST DRIVEN DEVELOPMENT AND REFACTORING | 9 |
Object oriented methodologies – Software quality assurance – Impact of object orientation on testing – Develop test cases and test plans.
\hfill Total Periods: 45
Upon completion of this course, the students should be able to:
- Express software design with UML diagrams (K2)
- Design and implement projects using OO concepts (K4)
- Identify and map basic software requirements in UML mapping (K3)
- Transform UML based software design into pattern based design using design patterns (K4)
- Test any object-oriented software against its requirements (K3).
- Larman, Craig, “Applying UML and Patterns”, Pearson Education Asia, 2008.
- Ali Bahrami, “Object Oriented Systems Development”, McGraw Hill International Edition, 1999.
- Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, “Design patterns: Elements of Reusable Object Oriented Software”, Addison Wesley, 1995.
- Martin Fowler, “UML Distilled: A Brief Guide to the Standard Object Modeling Language”, 3rd edition, Addison Wesley, 2003.
- Booch, G, Jacobson I, Rumbaugh J, “The Unified Modeling Language User Guide”, Addison Wesley, 2008.
- Roger S Pressman, “Software Engineering – A Practitioner’s Approach”, 7th edition, 2010.
- Aditya P Mathur, “Foundations of Software Testing – Fundamental Algorithms and Techniques”, Dorling Kindersley (India) Pvt. Ltd., Pearson Education, 2008.