VASIREDDY VENKATADRI INSTITUTE OF TECHNOLOGY NAMBUR-

522508 ANDHRA PRADESH, INDIA

YEAR: III B.Tech SEMESTER: II

COURSE NAME: OBJECT ORIENTED ANALYSIS AND DESIGN
COURSE CODE: XXXXXXXX
BRANCH: CSE
PREREQUISITE: OOPs Concepts
COURSE OBJECTIVE:

 To understand how to solve complex problems

 Analyze and design solutions to problems using object-oriented approach
 Study the notations of Unified Modeling Language

COURSE OUTCOMES: Students will be able to:

Cognitive
Levels as Weightage
SN OUTCOME
per Bloom’s (%)
Taxonomy
Analyse solutions to the complex problems
CO1 L1, L2 20
using object-oriented approach
Design structural model using classes,
CO2 L1, L2, L3 20
responsibilities and states using UML notation
Design behavioural model using basic
CO3 L1, L2,L3,L4 20
Interactions, Use cases of the problem domain
Design advanced behavioural models using
CO4 L3, L4 20
UML notation
Design and develop various components and
CO5 nodes from the problem domain using L3, L4 20
architectural modelling

WEIGHTAGE OF BLOOM’S LEGENDS & PERCENTAGE OF QUESTIONS IN

EXAMINATIONS:
L1 (Remembering) = 20 - 30%, L2 (Understanding) = 20 - 30%,
L3 (Applying) = 30 - 40 %, L4 (Analysing) = 30 - 40%,
Easy (%) = 10%-30%, Average (%) = 10% - 30%, Difficult (%) = 10% - 40%
TOTAL = L1 + L2 + L3 + L4 = 100% (on an average about 2 minutes per mark)
Note: This specification weightage in above shall be treated as a general guideline
for students, teachers and paper setters. The actual distribution of marks in the
question paper may vary slightly.
DETAILED SYLLABUS:
UNIT-1: Introduction to OOAD, The Structure of Complex systems, The Inherent
Complexity of Software, Attributes of Complex System, Introduction- Why we
model, Conceptual model of UML Architecture.
UNIT-II: Classes, Relationships, Common Mechanisms, Class diagrams, Object
diagrams

UNIT-III: Introduction- Interactions, Interaction diagrams, use cases, Use case

Diagrams, Activity Diagrams

UNIT-IV: Events and signals, State machines, Processes and Threads, Time and
space, State chart diagrams

UNIT-V: Introduction- Component, Deployment, Component diagrams,

Deployment diagrams

Case Study: The Unified Library application

TEXT BOOKS:
1. “Object- Oriented Analysis and Design with Applications”, Grady BOOCH,
Robert A. Maksimchuk, Michael W. ENGLE, Bobbi J. Young, Jim Conallen,
Kellia, Houston, 3rd edition, 2013, PEARSON.
2. “The Unified Modeling Language User Guide”, Grady Booch, James
Rumbaugh, Ivar Jacobson, 12th Impression, 2012, PEARSON.
REFERENCE BOOKS:
1. “Object-oriented analysis and design using UML”, Mahesh P. Matha, PHI
2. “Head first object-oriented analysis and design”, Brett D. McLaughlin, Gary
Pollice, Dave West, O‟Reilly
3. “Object-oriented analysis and design with the Unified process”, John W.
Satzinger, Robert B. Jackson, Stephen D. Burd, Cengage Learning

Online References
http://nptel.ac.in/courses/
 
Micro Syllabus of Object-Oriented Analysis and Design 
UNIT-1:
Introduction to OOAD, The Structure of Complex systems, The Inherent
Complexity of Software, Attributes of Complex Systems, Introduction- Why
we model, Conceptual model of UML, UML Architecture.
Unit No. Topic Sub Topic
Structure of Complex Systems
Complex Systems Inherent of Complex Systems
Attributes of Complex Systems
Introduction to UML
UNIT I Why do we Model?
Conceptual Model of UML-
UML Building Blocks (Things,
Diagrams, Relationships),
Rules, Common Mechanisms
UML Architecture
UNIT-2:
Classes, Relationships, Common Mechanisms, Class diagrams, Object
diagrams.
Unit No. Topic Sub Topic
Class definition, Terms and
Introduction to Classes Concepts (Name, Attributes,
Operations, Organizing Attributes
and Operations, Responsibilities)
Dependency, Generalization,
Association (Name, Role,
Relationships
Multiplicity), Aggregation and
Composition
Name, Stereotype, Tagged Values
UNIT II Common Mechanisms
and Constraints.
Class Diagram:- class definition,
visibility of attributes and
operations (private, public,
protected) with example diagram,
Class and Object Diagrams
class diagram construction.
Object Diagram:- object definition,
representation, an example
diagram.
Unit-3:
Introduction- Interactions, Interaction diagrams, use cases, Use case
Diagrams, Activity Diagrams.
Unit No. Topic Sub Topic
What is interaction, definition,
Terms and Concepts (Links,
Messages, Sequencing and
Interaction Diagrams Representation)
Interaction Diagrams:- Sequence
Diagram, Collaboration Diagram,
and various common modelling
techniques.
Definition, Elements (Use case,
Actor, Subsystems and
UNIT III
Use case Diagrams Relationships in use case
diagrams), Use case diagram
construction.
Definition, Elements (Activities,
Associations, Conditions,
Constraints), Notations (Initial
Activity Diagrams State, Final State, Condition,
Activity), Activity Diagram
Construction and various
common modelling techniques.
Unit-4:
Events and signals, State machines, Processes and Threads, Time and
space, State chart diagrams.
Unit No. Topic Sub Topic
 What is Event, Types of Events
(Internal and External Events),
Events and Signals
Signals, Call Events, Time and
Change Events, Sending and
Receiving Events.
Process Definition, Thread
UNIT IV
Definition, Synchronization,
Process and Threads
Communication, Time and
Location.
State Diagram Definition,
State Diagrams Example and various common
modelling techniques.
Unit-5:
Introduction- Component, Deployment, Component diagrams, Deployment
diagrams. Case Study: The Unified Library application.
Unit No. Topic Sub Topic
Component Diagram Definition,
Purpose of Component Diagram,
Example, and various common
Component and
UNIT V modelling techniques, Deployment
Deployment Diagrams
Diagram Definition, Notations,
Examples and various common
modelling techniques
 
 
Code No: R20

III B. TECH II SEMESTER REGULAR EXAMINATION MODEL PAPER

OBJECT ORIENTED ANALYSIS AND DESIGN
(CSE BRACNCH)
Time : 3 Hours Max. Marks : 70
___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Note : Answer ONE question from each unit (5 × 14 = 70 Marks)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UNIT-I CO BL
1. a) Why software is inherently complex? Explain. [7M] CO1 L2
b) Discuss clearly about Conceptual Model of UML [7M] CO1 L2
(OR)
2. a) List the limitations of the human capacity for dealing [7M] CO1 L1
with complexity? Explain.
b) List and explain how inherent complexity derives from [7M] CO1 L1
different elements?
UNIT-II
3. a) Develop the class diagram for an online railway [7M] CO2 L3
reservation system.
b) Describe the role of classes and objects in analysis [7M] CO2 L1
and design.
(OR)
4. a) Define and explain the following with examples: [7M] CO2 L2
i) Class ii) Object iii) Attributes iv) Operations
b) Illustrate about the Modeling a System's Architecture [7M] CO2 L3
with a neat sketch
UNIT-III
5. a) Write the features that distinguish collaboration [7M] CO3 L1
diagrams from sequence diagrams
b) Draw the use case diagram for library management [7M] CO3 L4
system
(OR)
6. a) Discuss about the behavioral aspects of collaboration [7M] CO3 L2
b) Model an activity diagram through online shopping [7M] CO3 L3
cart
UNIT-IV
7. a) How do you model the lifetime of an object? Explain [7M] CO4 L4
b) Illustrate the state chart diagram for airline [7M] CO4 L3
management system.
(OR)
8. a) Examine the following: i) History states ii) Time and [7M] CO4 L3
space
b) Write a problem statement for Library Management [7M] CO4 L4
system. Draw the State chart diagram
UNIT-V
 9. a) Draw the component diagram for bank management [7M] CO5 L4
system
b) Explain Node. Draw the deployment diagram for ATM [7M] CO5 L4
system
(OR)
10. a) Demonstrate package, component and deployment [7M] CO5 L3
diagrams
b) Draw a diagram that shows set of nodes and their [7M] CO5 L4
relations for Library Management system

*****
THE ABOVE MODEL PAPER ATTAINMENTS OF BLOOM’S TEXONOMY AS
FOLLOWS

L1: 4*7 = 28 = 20%

L2: 4*7 = 28 = 20%
L3: 6*7 = 42 = 30%
L4: 6*7 = 42 = 30%

SIGNATURES OF

COURSE COORDINATER MODULE COORDINATER HOD