Page 106 - Microsoft Word - B.Tech. Course Structure (R20) WITH 163 CREDITS

JNTUA College of Engineering (Autonomous), Ananthapuramu
Department of Computer Science & Engineering
Professional Elective-I
Object Oriented Analysis Design
Corse Code: Semester V (R20) L T P C : 3 0 0 3
Course Objectives:
● Understand the basic concepts of object-oriented techniques
● Build the Model of the software system using UML diagrams
● Elucidate design patterns as templates for good design
● Learn the object-oriented methodology in software design
● Demonstrate activity diagram and their modelling techniques.

Course Outcomes (CO):
CO1: Analyze the problem from object oriented perspective
CO2: Model complex systems using UML Diagrams
CO3: Determine the suitable design patterns in software design
CO4: Adapt Object-Oriented Design Principles
CO5: Apply basic structural modeling concepts for designing real-time applications

UNIT-I:Basic concepts
Basic concepts: objects, classes, abstract classes, data types, ADT, encapsulation and information
hiding, inheritance, association, aggregation, composition, polymorphism, dynamic binding, object-
oriented principles
UNIT-II:
Introduction to UML: Importance of modeling, principles of modeling, object oriented modeling,
conceptual model of the UML, Architecture, Software Development Life Cycle.
Basic Structural Modeling: Classes, Relationships, common Mechanisms, and diagrams. Advanced
Structural Modeling: Advanced classes, advanced relationships, Interfaces, Types and Roles,
Packages.

UNIT-III:
Class & Object Diagrams: Terms, concepts, modeling techniques for Class & Object Diagrams
Basic Behavioral Modeling-I: Interactions, Interaction diagrams.
Basic Behavioral Modeling-II: Use cases, Use case Diagrams, Activity Diagrams.

UNIT-IV:
Advanced Behavioral Modeling: Events and signals, state machines, processes and Threads, time
and space, state chart diagrams. Architectural Modeling: Component, Deployment, Component
diagrams and Deployment diagrams.

UNIT-V:
Patterns and Frameworks, Artifact Diagrams. Case Study: The Unified Library application

Mdv
Mdv