Jinnah University for Women

Theory Assignment

Department: Computer Science and Software Engineering Class: BS(SE) 2024

Instructions:
− The assignment must be submitted on JUW LMS. Email submission will not be accepted
− Each student has to solve the assignment individually
− You are advised to go through the related topics before solving the assignment
− Make your work clear and understandable
− Plagiarism may lead to marks deduction

Question # 1 [CLO: 3, BT Level: 4, Marks: 5]

You are working as a software developer for a company called QuickRent, which specializes in managing
rentals for properties, vehicles, and equipment. Your task is to design an Object-Oriented solution to
streamline QuickRent's rental management process.

Each rental category (property, vehicle, and equipment) has unique characteristics and requirements.
Properties include apartments, houses, and commercial spaces. Vehicles include cars, trucks, and
motorcycles. Equipment includes items such as projectors, cameras, and heavy machinery.

Each rental item has details like ID, availability status, rental rate, and rental history. Additionally, different
rental types require unique information. For example, properties need to track address, square footage, and
number of rooms, while vehicles require fuel type, mileage, and insurance status.

The system should allow customers to search for available rentals, book items, and view rental histories. A
rental agreement is formed when a customer books a rental item (property, vehicle, or equipment). The
rental agreement serves as a formal record of the transaction, including details about the rental period,
customer information, payment terms, and conditions specific to each rental type.

a. Identify the classes that would be required to implement this rental system.
b. Which classes can be represented using inheritance? Describe a basic class hierarchy for the rental
categories.
c. How would you design a base class for RentalItem? What attributes and methods would you include
in this base class?
d. How would you use encapsulation to ensure that rental item attributes like rental rate and
availability status are only modified through specific methods?
e. How would you implement polymorphism to allow each rental type to have its own specific details
(e.g., properties for a vehicle, like fuel type, or for a property, like square footage)?
f. How would you use abstract classes and interfaces in conjunction with polymorphism to design
this rental system more effectively?
 g. What is the relationship between a customer and a rental item, and how does it differ from the
relationship between a rental item and a rental agreement?
h. What attributes or methods in the QuickRent system could be defined as static, and why?
i. How can constructor chaining be used in the RentalItem class to initialize properties such as ID,
availabilityStatus, and rentalRate?
j. If you override the displayDetails method in the Vehicle class, which inherits from RentalItem,
how can you call the base class’s displayDetails method before adding vehicle-specific details?

Question # 2 [CLO: 2, BT Level: 3, Marks: 5]

In a Smart Home Automation System, different user roles and device types enable personalized control and
security for the homeowner. The system manages three main user roles: homeowners, guests, and
administrators. Each role shares general characteristics, such as a unique user ID, name, and level of access,
but each has distinct permissions. Homeowners can control all devices in the system, guests may have
limited access to certain devices (such as lights or guest-room devices), and administrators are responsible
for system-wide configuration and security. Each user also has an associated profile, which contains
personal details, access level, and device preferences, enhancing personalized control.

To handle the various devices in a smart home, the system supports multiple types, such as lights,
thermostats, cameras, and locks, which share core characteristics like a unique device ID, status (e.g., on or
off), and location. However, each device type has unique features and actions based on its function. For
example, a thermostat can adjust temperature, while a camera can record video.

The system maintains strict access controls to secure sensitive device data and ensure privacy. Only
authorized users, such as homeowners and administrators, can view and modify critical information like
camera recordings or door locks. Meanwhile, guests can only control basic devices within their permission
level, such as lights or guest-room settings, if the homeowner grants them access.

The system's design is built upon a general structure for devices that defines standard behaviors, like turning
a device on or off, without needing to specify details for every device type upfront. This approach allows
the system to support new device types, such as smart speakers or blinds, without requiring a major rework
of existing code.

Additionally, the system defines a flexible relationship between users and devices. Homeowners typically
have control over all devices, while guests may only be granted access to specific devices. This setup
provides a manageable and secure structure for controlling device accessibility and sharing. To support
automation, each routine contains multiple devices, allowing users to execute a sequence of actions across
the home in a single command. The routines themselves are designed to operate independently of individual
devices, so if a particular device becomes unavailable, the rest of the routine can still run as planned. For
example, the "Good Morning" routine might involve turning on lights and adjusting the thermostat, but if
one device is offline, the routine can still partially execute.

Based on this complex problem, design a class diagram for the Smart Home Automation System. The
diagram should include:
• Different user roles (homeowners, guests, administrators) and device types (lights, thermostats,
cameras, locks) with shared and unique attributes.
• Specific actions for each device type, as well as the setup for automated routines that enable flexible
device control.
• Access restrictions to device data and settings based on user roles.
• A general structure for devices that can be extended by other device types as needed.
• Relationships between users and devices to show control and access permissions.
• A way to model routines with multiple devices that can operate even if some devices are
temporarily unavailable.
• A relationship between user accounts and profiles, ensuring profiles are deleted if the account is
removed.