CS8592-OOAD Question Bank

BUILDERS/CSE/ CS8592-OBJECT ORIENTED ANALYSIS AND DESIGN -Question Bank Page 1 of 9
CS8592 - OBJECT ORIENTED ANALYSIS AND DESIGN (V- Semester)
QUESTION BANK
Syllabus
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 and 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.

UNIT I - UNIFIED PROCESS AND USE CASE DIAGRAMS
PART – A (2 MARKS)
1. What is Object-Oriented Analysis and Design? (OR) What is analysis and design?
2. List the principles of modeling in UML.
3. List out the components of a POS system.
4. Define: Inception. (OR) What is inception?
5. When to use Generalization use case relationship.
6. List out the various phases of Unified Process.
7. Difference between Include and Extend use case relationships.
8. What are the primary goals in the design of UML?
9. List the relationships used in class diagram.
10. Define an object. Identify the probable attributes that will be modelled in a Library database for the
object BOOK.
11. Outline the purpose of using use cases, to describe requirements.
12. What is UML? (OR) What is Unified Modeling Language?
13. Distinguish between Method and Message in object.
14. What are the three perspectives to apply UML?
15. When to use Use-cases?
16. List out any four reasons for complexity of software.
PART – B (13/15 MARKS)
1. Consider an elevator that has the basic functions such as moving up and down open and close doors
and pick up passengers. The elevator is supposed to be used in a building having floors numbered from
1 to n. There are call buttons in the elevator corresponding to each floor. For every floor except floors
1 and n, there are two floor call buttons for the passengers to call elevator for going up and down.
There is only one down call button at floor n and one up call button in floor 1. Then the car stops at a
floor, the doors are opened and the elevator light indicating the current direction the elevator is going
is illuminated so that the passengers can get to know the current moving direction of the elevator. When
the elevator is moving a music, audio is played inside the elevator.
Draw class diagram, activity diagram and component diagram for designing this system. (OR)
List various UML diagrams and explain the purpose of each diagram with an example problem. (OR)
Write a problem statement for Library Management System. Draw the UML Use Case, Activity
Diagram, Class Diagram, Sequence Diagram, State Chart Diagram, Package Diagram, Component and
Deployment Diagram. (OR)
Discuss about UML Deployment and Component Diagrams. Draw the diagrams for a banking
application. (OR)

Explain the conceptual model of the UML in detail? Explain various common mechanisms used in
UML. (13) (OR)
i) Model a use case diagram for the following scenario: (7)
Deepthi super market wants a subsystem to process supply orders via the Web. The user will supply
via a form their name, password, account number and a list of supplies along with an indication of the
quantities desired. The subsystem will validate the input, enter the order into a database and generate
a receipt with the order number, expected ship date and the total cost of the order. If the validation step
fails, the subsystem will generate an error message describing the cause of the failure.
ii) "A component represents a modular, deployable and replaceable part of a system that encapsulates
implementation and exposes a set of interfaces”. Elucidate with an example. (6) (OR)
i) Draw and discuss an analysis model for Banking system. (7)
ii) Explain the software development life cycle of object oriented approach. (6)
2. Explain in detail about the interaction diagrams and also notations.
3. Explain in detail about Unified Process in Object Oriented Analysis and Design. Explain the phases
with neat diagrams. (OR)
i) Present an outline of object-oriented analysis and object-oriented design. (7)
ii) Why the Unified process has emerged as a popular and effective software development process? (6)
(OR)
Explain about Unified process phases.
4. Model a state transition diagram for the following scenario. (13)
Here is what happens in a microwave oven:
• The oven is initially in an idle state with door open, where the light is turned on.
• When the door is closed it is now in idle but the light is turned off.
• If a button is pressed, then it moves to initial cooking stage, where the timer is set and lights are
on and heating starts.
• At any moment the door may be opened, the cooking is interrupted, the timer is cleared and heating
stops.
• Also, while cooking, another button can be pushed and extended cooking state starts, where the
timer gets more minutes. At any moment door can be opened here also.
• If the timer times out, then cooking is complete, heating stops, lights are off and it sounds a beep.
• When the door is open, again the oven is in idle state with the door open.
5. Explain about Use Case Model for a POS case study. (OR) Explain about the Next Gen POS System.
6. Model a class diagram for a "Banking System". State the functional requirements you are considering.
--------------******--------------

UNIT II - STATIC UML DIAGRAMS
1. Define design class diagrams.
2. What is the need for modelling?
3. When to create a subclass of a superclass?
4. What is the relationship of a conceptual super class to a subclass?
5. Define Aggregation and Composition.
6. What are the tasks performed in elaboration?
7. How to create a Domain Model?
8. Define Conceptual class.
9. When to define new datatype classes?
10. Why call a Domain Model a ‘Visual Dictionary’?
11. Define: Use Case Model.
12. When to use Class Diagrams?
13. List the advantages of Use Case Modeling.
14. What is Elaboration? What are the tasks performed in elaboration?
15. Define refinement.
16. How a sequence diagram is related to a use case?
1. Write about elaboration and discuss the differences between elaboration and Inception with suitable
diagram for university domain. (OR)
Write briefly about elaboration and discuss the differences between elaboration and inception with
examples.
2. Construct design for library information system which comprises and following notations
(i) aggregations (ii) compositions (iii) associations. (OR)
Explain association, aggregation and composition relationships in detail. (OR)
i. Explain in detail about use case diagrams. (6)
ii. Discuss about aggregation and composition. (7) (OR)
i) What is multiplicity of an association? Explain with an example the different types of
multiplicities.(7)
ii) Explain with an example aggregation and composition. (6)
3. What are the guidelines used to partition the class in the domain model to be organized into packages?
Explain with suitable examples. (OR)
Illustrate the concept the domain model with examples. (OR)
Define domain model with suitable examples.
4. Explain the guidelines for finding conceptual class with neat diagrams. (OR)

Discuss in detail about the three strategies to find conceptual classes. (OR)
For the hospital management system draw and explain Conceptual Class Diagram (Overall system). (OR)
Describe the strategies used to identify conceptual classes. Describe the steps to create domain model
used for representing conceptual classes.
5. What is the purpose of a Use Case model? Identify the Actors, Scenarios and Use Case for a Library
Management System. (OR)
Explain with an example, how use case modeling is used to describe functional requirements. Identify
the actors, scenario and use cases for example.
6. i) Explain with an example a concrete use case and an abstract use case. (5)
i)Explain with an example generalization and specialization and write a note on abstract class and
abstract operation. (8)
7. Illustrate with an example, the relationship between sequence diagram and use cases.
--------------******--------------
UNIT III - DYNAMIC AND IMPLEMENTATION UML DIAGRAMS
1. Outline the key reason for modeling a package diagram.
2. Name the two types of UML interaction diagrams.
3. What are the strength and weakness of Sequence and Collaboration Diagram?
4. What is SSD?
5. What is meant by System Behavior?
6. What do you mean by sequence number in UML? Where and for what it is used?
7. Differentiate Synchronous message and Asynchronous Message.
8. What is Activity Diagram? Mention the elements of an Activity Diagram.
9. When to use activity diagram?
10. What is Guard condition?
11. What is the use of Rake symbol in UML Activity diagram?
12. What is qualified association?
13. How to Naming System Events and Operations?
14. When to use Package Diagrams and Collaboration diagram?
15. Define component diagram.
16. When to use Component and Deployment diagrams?
1. Explain details about various static and dynamic UML important diagram with suitable example. (OR)
Explain the UML Interaction Diagrams for Library Management System. (OR)

Explain about Interaction Diagram Notation for inventory management system. (OR)
Explain with an example UML Interaction diagram. (OR)
What do you mean by Interaction diagram? Explain them with suitable example. (OR)
Compare Sequence versus Collaboration diagram with suitable example. (OR)
Explain how Interaction diagram used to model the dynamic aspects of the system. (OR)
What are interactive diagrams? Explain the components involved in interactive diagram. (OR)
2. Consider the following use cases that play a role in a banking system:
i. Deposit
ii. Withdraw (Minimum balance has to be checked)
Model Sequence diagram for the above two use cases. (OR)
What is System Sequence Diagram? What is the relationship between SSDs and Use cases? Explain
with an example.
3. Explain about State Machine and activity diagram with an example. (OR)
When to use State Machine and activity diagram? Describe the situation with an example. (OR)
Explain the features of basic UML State Machine and activity diagram notations.
4. Write a problem statement for Library Automation System. Explain UML Package Diagram,
Component and Deployment Diagram with neat sketch. (OR)
When to use Packages, Component and Deployment diagrams? Explain with suitable examples.
--------------******--------------
UNIT IV - DESIGN PATTERNS
1. Mention the list of behavioural patterns used during design phase of software development.
2. List out the types of coupling.
3. Distinguish between coupling and cohesion. (OR) Define cohesion and coupling.
4. Define Patterns and Design pattern. What are design patterns?
5. When to use patterns? (OR) State the use of design pattern.
6. Define Modular Design.
7. What is meant by Low Coupling and High Cohesion?
8. What is GRASP?
9. Define Object with an example.
10. ‘A system must be loosely coupled and highly cohesive’. Justify,
11. Differentiate Adaptor and Bridge.
12. Define Factory method.
13. How to select a design pattern?

14. Define Push model and Pull Model.
15. What are the advantages of Factory Objects?
16. What are the steps for mapping Designs to Code? (OR)
Mention the steps involved in mapping Designs to Code.
1. What is GRASP? Explain the following GRASP patterns: Creator, Information Expert, and Low
Coupling, and High Cohesion. (OR)
What is GRASP? Explain the design patterns and the principles used in it. (OR)
Explain in detail about the GRASP pattern and also explain in designing objects with responsibilities.
2. Compare cohesion and coupling with suitable example.
State the role and patterns while developing system design.
3. i) Write short notes on: adaptor pattern and observer pattern. (7)
ii) Compare between different categories of design patterns. (6) (OR)
Differentiate Bridge and Adapter. How will you design the behavioral pattern? (OR)
What is Design pattern? Explain GOF design Patterns. (OR)
Write a short note on Adapter, Bridge, Factory Method, Strategy and Observer patterns. (OR)
Explain with an example the factory method design pattern. (OR)
Explain in detail about the Factory Pattern and mention the Limitations and applications of Factory
pattern.
4. Designing the Use Case realizations with GOF design patterns.
5. What GRASP? Explain the following GRASP patterns: Creator, Information Expert, Low Coupling,
High Cohesion, Controller. (or)
Explain creator and controller design pattern with examples. (or)
Explain the design principle in object modeling. Explain in detail the GRASP method for designing
objects with examples.
6. Elucidate the operation of Mapping Designs to Code. (OR)
Explain in detail the design artifacts to implementation code in Object Oriented Language. (OR)
Explain in detail about the Mapping of Deign to Code implementation in an Object-Oriented Language.
(OR)
Explain about implementation model (Mapping Designs to Code). (OR)
Explain how the designs are translated to code.
--------------******--------------

UNIT V - TESTING
1. Define software quality assurance.
2. What are the three different parts of OMT modelling?
3. What is OO testing?
4. Define OOM.
5. What is Micro Development Process?
6. Differentiate OOSE and OOBE.
7. List the Object-Oriented Metrics?
8. Why do peer review in SQA?
9. Differentiate static, dynamic and passive testing.
10. What is unit testing and GUI testing??
11. Define a test case. Give example.
12. List out the issues in OO Testing.
13. Distinguish between OO Integration Testing and OO System Testing. (OR)
Explain about OO Integration Testing.
14. What is refactoring? (OR) What is refactoring and testing?
15. Define Regression and Stress testing.
16. What are the challenges of class testing?
17. What are the various levels of Testing?
18. How UML supports Integration Testing?
19. Define MM path.
20. Why to use test plan? Give test plan types.
1. Discuss the various types of testing strategies in object-oriented environment.
2. Explain Jacobson and Booch Object Oriented Methodologies in detail. (OR)
Discuss briefly about Object-Oriented Methodologies. (OR)
Give the structure of OOM. Explain Rumbaugh’s Object Modelling Technique.
3. Explain in detail about Software Quality Assurance. (6)
4. i) Why do we write test cases? Explain test in detail. (7)
ii) Why to use a test plan? Briefly explain test plan. (6)
5. What is OO testing? Explain in detail about the Concepts of OO testing in OOAD. (OR)
i) Explain in detail about GUI testing. (6)
ii) Comparison between OO integration testing and OO system testing. (7) (OR)
i) How is class testing different from conventional testing? Explain with an example. (7)
ii) Write a note on system testing. (6) (OR)

What is Integration Testing? Discuss in detail about its impact in OO testing. (OR)
What is integration testing? Explain the same with respect to object-oriented systems.
6. Discuss the various types of testing strategies in object-oriented environment. (OR)
Explain in detail about the different types of testing in OOAD. (OR)
Discuss in detail about OO Integration Testing and OO System Testing. (OR)
Write a short note on integration testing and class testing. (OR)
--------------******--------------

CS8592-OOAD Question Bank

Recommended

More Related Content

What's hot (20)

Similar to CS8592-OOAD Question Bank (20)

More from Gobinath Subramaniam (20)

Recently uploaded (20)

CS8592-OOAD Question Bank