CY-604-B Ooad - Jun 2025 Question Paper

Under each question, How to answer lists the points an answer should cover, outlined by CampusPrep from the syllabus. Check the details against your textbook.

1. 7 Marks
   aWhat are the primary reasons for adopting an object-oriented approach in software development?
   How to answer

   • Define object-oriented approach and its goals
   • Reasons: abstraction, encapsulation, modularity, maintainability
   • Handles complexity of large software, models real world
   • Improves reusability, extensibility and productivity
2. 7 Marks
   bWhat benefits does object orientation provide in terms of code reuse?
   How to answer

   • Define code reuse in OOP
   • Role of inheritance, polymorphism, class libraries
   • Reduced development time, cost and redundancy
   • Improved reliability and maintainability with example
3. 14 Marks
   Explain the terms and concepts of Object diagram with suitable examples.
   How to answer

   • Define object diagram as instance snapshot of class diagram
   • Concepts: objects, links, attribute values at runtime
   • Notation and difference from class diagram
   • Suitable example with object boxes and links
4. 14 Marks
   What is the purpose of the object model in OMT? And how are relationships such as associations, aggregations, and inheritance represented in an object model?
   How to answer

   • Define OMT and its three models, focus on object model
   • Purpose: static structure, classes, attributes, operations
   • Representation of association with multiplicity
   • Representation of aggregation and inheritance/generalization
5. 7 Marks
   aWhat is the difference between Multilevel and Multiple Inheritance?
   How to answer

   • Define multilevel inheritance with chain example
   • Define multiple inheritance with multiple parents example
   • Compare on structure, ambiguity, complexity
   • Diagram for each type
6. 7 Marks
   bExplain the relationships in the UML.
   How to answer

   • List UML relationships: association, aggregation, composition
   • Explain generalization, realization, dependency
   • Notation for each relationship
   • Simple example diagram
7. 7 Marks
   aWhy is translating OOD into implementation important in software development?
   How to answer

   • Define OOD and implementation phase
   • Bridges design to executable code, preserves design intent
   • Ensures traceability, quality and maintainability
   • Enables verification of requirements
8. 7 Marks
   bWhat are the challenges of moving from design to implementation in OOP?
   How to answer

   • Mapping abstract design to language-specific constructs
   • Handling inheritance, polymorphism, performance constraints
   • Language limitations and library support issues
   • Testing, integration and maintaining design integrity
9. 14 Marks
   What is UML, and why is it important and how does UML differ from other modeling languages?
   How to answer

   • Define UML as standardized modeling language
   • Importance: visualization, specification, documentation
   • Features: multiple diagram types, tool support
   • Difference from other languages: standard, extensible, language-independent
10. 14 Marks
    What is the difference between a sequence diagram and a collaboration diagram?
    How to answer

    • Define sequence diagram: time-ordered interactions
    • Define collaboration/communication diagram: structural organization
    • Compare on focus, notation, lifelines vs links
    • Example scenario showing both views
11. 7 Marks
    aWhat are examples of query languages used in Object-Oriented Databases?
    How to answer

    • Define object-oriented database query needs
    • Examples: OQL, ODMG OQL, Object SQL extensions
    • Features: navigation of objects, methods, complex types
    • Vendor examples
12. 7 Marks
    bCan standard SQL be used with Object-Oriented Databases?
    How to answer

    • Define standard relational SQL limitations
    • Need for object extensions: OIDs, inheritance, methods
    • SQL:1999 object extensions and OODB interfaces
    • Conclusion with suitability and workarounds