Question Paper 1

Define Software Engineering and explain its importance.

Software Engineering is the application of engineering principles to the development of software in a systematic method. It
ensures the software is reliable, efficient, and meets user needs while being maintainable and scalable.

What are the key principles of Object-Oriented Design?

The key principles are:

 Encapsulation: Wrapping data and methods into a single unit.

 Abstraction: Focusing on essential qualities while hiding implementation details.
 Modularity: Dividing the system into manageable modules.
 Inheritance: Enabling reuse by deriving new classes from existing ones.
 Polymorphism: Allowing entities to take multiple forms.

Differentiate between abstraction and encapsulation.

 Abstraction is the process of hiding unnecessary details to show only essential information.
 Encapsulation is the technique of bundling data and methods that operate on the data into a single
unit (class) and restricting access.

Explain the concept of aggregation with an example.

Aggregation is a "has-a" relationship where one object contains other objects but both can exist independently.
Example: A department has employees. If the department is deleted, employees still exist.

What is UML? Why is it used?

UML (Unified Modeling Language) is a standard for visualizing, specifying, constructing, and documenting software systems. It is
used to design object-oriented systems and understand system architecture.

Describe the role of a class diagram in software development.

A class diagram represents the static structure of a system, showing classes, their attributes, operations, and relationships. It
helps in understanding system structure and designing software architecture.

List the phases of the Unified Process model.

The phases are:

 Inception
 Elaboration
 Construction
 Transition

Define artifacts in the context of architectural modeling.

Artifacts are tangible outputs or deliverables in software development, such as code, design documents, models, and executable
files.

What is the difference between a sequence diagram and a collaboration diagram?

 Sequence Diagram: Focuses on the order of interactions between objects over time.
 Collaboration Diagram: Focuses on the structural organization of objects and their interactions.
Explain inter-class test case design in object-oriented testing.

Inter-class test case design tests interactions between classes, focusing on relationships, method calls, and the exchange of data
between objects to ensure proper collaboration.

Discuss the various software engineering development activities in detail.

 Analysis: Identifying user needs and documenting requirements.

 Design: Creating software architecture, interfaces, and components.
 Implementation: Writing and integrating code.
 Testing: Verifying that the software meets requirements and is defect-free.
 Deployment: Installing the software for users.
 Maintenance: Updating and improving the software post-deployment.

Illustrate the process of identifying classes and objects in object-oriented modeling with an example.

 Steps:
o Identify nouns in the problem statement.
o Map nouns to classes and objects.
o Define their attributes and operations.
Example: For a library system:
 Classes: Book, Member, Librarian
 Attributes: (Book - title, author), (Member - ID, name)
 Operations: Borrow(), Return(), Register().

Explain the conceptual model and architecture of UML.

UML's conceptual model includes three components:

 Basic Building Blocks: Elements (e.g., classes, objects), Relationships (e.g., association, dependency), Diagrams.
 Rules: Syntax and semantics of UML elements.
 Common Mechanisms: Specifications, adornments, common divisions.
Architecture:
 User View (Behavioral models)
 Design View (Structural models)
 Implementation View (Artifacts)
 Process View (Workflows and interactions).

Discuss the importance of activity diagrams in behavioral modeling.

Activity diagrams represent workflows and processes, showing control flow from one activity to another. They are crucial for:

 Visualizing processes.
 Understanding complex workflows.
 Identifying dependencies and bottlenecks.

Compare and contrast association, aggregation, and composition relationships with suitable examples.

 Association: General relationship between objects (e.g., Teacher teaches Students).

 Aggregation: Weak "has-a" relationship (e.g., Department has Employees).
 Composition: Strong "has-a" relationship; parts cannot exist without the whole (e.g., House has Rooms).

* Draw a use case diagram for an online shopping system and explain its components.

 Actors: Customer, Admin, Payment Gateway.

 Use Cases: Search Product, Add to Cart, Place Order, Make Payment, Manage Inventory.
Diagram:

* A library management system needs to be developed. Identify the classes and objects, specify their
attributes and operations, and create a class diagram for the system.

 Classes:

 Book (Attributes: title, author; Operations: Borrow(), Return()).

 Member (Attributes: name, ID; Operations: Register(), BorrowBook()).
 Librarian (Attributes: name, ID; Operations: AddBook(), ManageInventory()).

Class Diagram:
 Question Paper 2

Define the term "object-oriented modeling" and explain its purpose.

Object-oriented modeling is a methodology for analyzing, designing, and implementing systems by using object-oriented
principles (classes, objects, inheritance). Purpose:

 Enhances system visualization.

 Promotes code reusability.
 Provides better alignment with real-world scenarios.

What is modularity in software engineering? Mention its advantages.

Modularity divides a system into smaller, manageable components.

 Advantages: Improves maintainability, reduces complexity, enables parallel development, and

fosters code reuse.

Describe the relationship between classes and objects.

 Class: A blueprint defining properties (attributes) and behaviors (methods).

 Object: An instance of a class.

Differentiate between association and dependency in UML with examples.

 Association: A relationship where one class uses another. Example: Teacher teaches Students.
 Dependency: A weaker relationship; a class relies on another temporarily. Example: OTT
_Subcription depends on Basic_Subscription and Premium_Subscription

Write a brief note on the conceptual model of UML.

UML's conceptual model involves elements like:

 Basic building blocks (classes, interfaces).

 Relationships (association, aggregation).
 Diagrams (class, use case).

What is the significance of state chart diagrams in behavioral modeling?

State chart diagrams show an object's states and transitions, helping to model reactive systems (e.g., ATM states like idle,
processing, and dispensing).

Define encapsulation and mention its benefits.

Encapsulation binds data and methods together and restricts direct access to some components.

 Benefits: Protects data integrity, enhances security, and simplifies system maintenance.

List the types of testing strategies used in Object-Oriented Testing.

 Unit Testing
 Integration Testing
 System Testing
 Scenario-Based Testing
Explain the term "dynamic binding" with an example.

Dynamic binding decides which method to invoke at runtime.

What is an artifact diagram, and where is it used?

An artifact diagram represents physical files like source code, binaries, and documents in the system. Used in deployment
modeling/Impletation model.

Discuss the architecture of UML and its role in software development.

 Architecture of UML: Includes views like use-case view,design view, Implementation view, process view, and
deployment view.
 Role: Simplifies system visualization, fosters communication, and ensures consistent documentation.

Explain the concept of inheritance and describe its types with examples.

 Inheritance: Allows a class (child) to inherit properties of another class (parent).

 Types:

 Single Inheritance: One parent, one child.

 Multiple Inheritance: One child, multiple parents (not supported in Java directly).
 Multilevel Inheritance: Grandparent → Parent → Child.

* Draw and describe a Sequence Diagram for a ticket booking system.

Actors: Customer, Ticket System, Payment Gateway.

 Steps:

 Customer selects a ticket.

 System checks availability.
 Payment is processed.
 Confirmation is sent.

Compare and contrast deployment diagrams and component diagrams in UML.

 Deployment Diagram: Physical distribution of artifacts on nodes.

 Component Diagram: Logical grouping of classes and interfaces representing system functionality.

Explain the Unified Process and its four phases with suitable examples.

 Inception: Define scope.

 Elaboration: Refine architecture and resolve risks.
 Construction: Build the system.
 Transition: Deploy the system.

Case Study: Employee Management System Class Diagram.

 Classes: Employee, Department, Manager.

 Attributes: Employee (ID, name, position); Department (ID, name); Manager (ID, level).
 Operations: AssignDepartment(), PromoteEmployee(), GetManagerDetails().

*Use Case Diagram for Banking System:

Actors: Customer, Teller, Manager.
Use Cases: Deposit, Withdraw, Check Balance, Loan Processing.
 Question Paper 3

What is Software Development Life Cycle (SDLC)? Name its stages.

SDLC is a structured process for developing software.

 Stages: Requirement analysis, System design, Implementation, Testing, Deployment, Maintenance.

Describe the significance of abstraction in Object-Oriented Design.

Abstraction focuses on essential details and hides complexities.

 Significance: Simplifies development, enhances reusability, and ensures modularity.

Differentiate between classes and interfaces in UML.

 Classes: Define properties and methods with implementation.

 Interfaces: Only define method signatures, with no implementation.

What are the different types of relationships used in UML diagrams?

 Association: "Uses-a" relationship.

 Inheritance: "Is-a" relationship.
 Realization:
 Dependency: when one class relies on other class.
 Aggregation: "Has-a" relationship (weak).
 Composition: "Part-of" relationship (strong).

Why is the Unified Process considered iterative and incremental?

It develops software in repeated cycles (iterative) and delivers small portions of functionality (incremental).

What is the role of a package in UML modeling?

Packages group related classes, interfaces, and diagrams for better organization and modularization.

Define polymorphism and give a practical example of its application.

Polymorphism allows objects to take multiple forms.

Describe the importance of interaction diagrams in behavioral modeling.

Interaction diagrams (sequence and collaboration) model object interactions and message flow, ensuring clarity in system
behavior.

What are the components of the System Design Process in Object-Oriented Design?

Partitioning analysis model, concurrency allocation, subsystem allocation, data management, task management, and resource
management.

Briefly explain the importance of test case design for object-oriented software.

 Validates functionality.
 Ensures class and object interactions work as intended.
 Prevents errors during inheritance and polymorphism.
Explain the role of Use Case Diagrams in software development. Illustrate with a diagram for a student
management system.

 Role: Models system functionalities, defines interactions between actors and use cases, and ensures requirements are
met.
 Diagram: Actors: Student, Admin.
Use Cases: Register, View Grades, Update Profile.

Discuss the importance of managing software development effectively. Highlight key techniques.

 Importance: Reduces risks, improves productivity, ensures timely delivery.

 Techniques: Agile methodologies, risk management, task scheduling, quality assurance, and effective communication.

Draw and explain an Activity Diagram for an online food delivery system.

 Activities: User places an order → Restaurant confirms → Delivery process → Order delivered.
 Swimlanes: Customer, Restaurant, Delivery Agent.

* Describe the differences between behavioral modeling and structural modeling in UML.

 Behavioral Modeling: Focuses on system behavior (e.g., Use Case, Sequence diagrams).
 Structural Modeling: Represents static structure (e.g., Class, Object diagrams).

Explain object relationships like aggregation and composition with examples.

 Aggregation: Weak association. Example: A department has employees.

 Composition: Strong ownership. Example: A house has rooms (rooms cannot exist without the house).

Case Study: Hospital System Class Diagram.

 Classes:

 Doctor: Attributes (ID, specialization); Methods (ScheduleAppointment, ViewPatients).

 Patient: Attributes (ID, name); Methods (Register, ViewRecords).
 Appointment: Attributes (date, time); Methods (Book, Cancel).

 Diagram: Include relationships (association between Doctor and Patient).

* State Chart Diagram for a Traffic Light Control System:

States: Red → Green → Yellow.
Transitions: Timer expiration.

 Concurrency and Subsystem Allocation: Multiple traffic lights can operate in parallel, each as a subsystem.
Communication between subsystems ensures coordination.