Course Code : MCSL-217

Course Title : Software Engineering Lab

Assignment Number : MCAOL(I)/217/Assign/2025
Maximum Marks : 100
Weightage : 40%
th
Last Dates for Submission : 30st April 2025 (for January session)
31 October 2025 (for July session)

This assignment has one question for 40 marks. Answer this question. Your Lab Records will
carry 40 Marks. Rest 20 marks are for viva voce. You may use illustrations and diagrams to
enhance the explanations. Please go through the guidelines regarding assignments given in the
programme guide for the format of presentation.

Note: You must execute the program and submit the program logic, sample input and output along
with the necessary documentation. Assumptions can be made wherever necessary.

Q1:

ABC is a network of Hospitals. Its having Hospitals across the World. Its possible to take appointment for any
Doctor for an available slot on an available date through its website. Its having a Chatbot also. There are many
specialities in each of its Hosptitals. However, not all specialities are available across all its Hospitals. Doctors
may provide consultancy services in more than one hospital of its network. Its possible to make payment of
consultation fee online while taking appointment or directly at hospital prior to consultation.
Make assumptions, wherever necessary. Also, list them very clearly.

Now, with reference to the above, answer the following:

(1) List the Entities (10 Marks)

(2) For each Entity, list Attributes (10 Marks)
(3) Define relationships between the Entities (10 Marks)
(4) Finally, draw the Entity Relationship Diagram (10 Marks)

16
 1

MCSL-217
SOLVED ASSIGNMENT 2025

Q.1 - ABC is a network of Hospitals. Its having Hospitals across the

World. Its possible to take appointment for any Doctor for an
available slot on an available date through its website. Its having a
Chatbot also. There are many specialities in each of its Hosptitals.
However, not all specialities are available across all its Hospitals.
Doctors may provide consultancy services in more than one hospital
of its network. Its possible to make payment of consultation fee
online while taking appointment or directly at hospital prior to
consultation. Make assumptions, wherever necessary. Also, list
them very clearly.
Now, with reference to the above, answer the following:

(1) - List the Entities

(2) - For each Entity, list Attributes
(3) - Define relationships between the Entities
(4) - Finally, draw the Entity Relationship Diagram
 2

ANS.- design an Entity-Relationship Diagram (ERD) for the ABC Hospital Network based on the provided
scenario.
Assumptions:
1. Doctor Specialization: A doctor can specialize in multiple medical fields.
2. Hospital Specializations: A hospital can offer multiple specializations.
3. Appointment Slots: Each appointment slot has a specific time and duration.
4. Payment Methods: Online payment can be made through various gateways like credit cards,
debit cards, net banking, etc.
5. Chatbot Interactions: Chatbot interactions are recorded for analysis and improvement.
6. Patient Demographics: Basic patient information like age, gender, and contact details are
collected for appointments.
1. Entities
 Hospital
 Doctor
 Patient
 Specialization
 Appointment
 Appointment Slot
 Payment
 Chatbot Interaction
2. Attributes
 Hospital
o HospitalID (Primary Key)
o HospitalName
o Address
o City
o Country
o ContactNumber
o Email
o Website
o Specializations (List)
 Doctor
o DoctorID (Primary Key)
o DoctorName
o Specializations (List)
o ContactNumber
o Email
o Experience
 3

o Qualifications
o Hospitals (List of HospitalIDs)
 Patient
o PatientID (Primary Key)
o FirstName
o LastName
o DateOfBirth
o Gender
o ContactNumber
o Email
o Address
o MedicalHistory (if applicable)
 Specialization
o SpecializationID (Primary Key)
o SpecializationName
 Appointment
o AppointmentID (Primary Key)
o PatientID (Foreign Key referencing Patient)
o DoctorID (Foreign Key referencing Doctor)
o HospitalID (Foreign Key referencing Hospital)
o AppointmentSlotID (Foreign Key referencing Appointment Slot)
o AppointmentDate
o AppointmentTime
o Status (e.g., Booked, Cancelled, Completed)
o ConsultationFee
o PaymentStatus (e.g., Paid, Unpaid)
 Appointment Slot
o AppointmentSlotID (Primary Key)
o DoctorID (Foreign Key referencing Doctor)
o HospitalID (Foreign Key referencing Hospital)
o Date
o StartTime
o EndTime
o Availability (Boolean)
 Payment
o PaymentID (Primary Key)
o AppointmentID (Foreign Key referencing Appointment)
o PaymentDate
 4

o Amount
o PaymentMethod
o TransactionID
 Chatbot Interaction
o InteractionID (Primary Key)
o PatientID (Foreign Key referencing Patient)
o ChatbotTimestamp
o UserQuery
o ChatbotResponse
o InteractionType (e.g., Text, Voice)
3. Relationships
 Works_At:
o Many-to-Many relationship between Doctor and Hospital.
o Represents the association of doctors with the hospitals where they practice.
 Specializes_In:
o Many-to-Many relationship between Doctor and Specialization.
o Indicates the medical fields in which a doctor specializes.
 Offers:
o Many-to-Many relationship between Hospital and Specialization.
o Shows the specializations offered by each hospital.
 Has:
o One-to-Many relationship between Hospital and Appointment Slot.
o Each hospital has multiple appointment slots available.
 Schedules:
o One-to-Many relationship between Doctor and Appointment Slot.
o Each doctor schedules multiple appointment slots.
 Books:
o One-to-Many relationship between Patient and Appointment.
o A patient can book multiple appointments.
 Belongs_To:
o One-to-One relationship between Appointment and Appointment Slot.
o Each appointment is associated with a specific appointment slot.
 Makes:
o One-to-Many relationship between Appointment and Payment.
o An appointment can have associated payment records.
 Interacts_With:
o One-to-Many relationship between Patient and Chatbot Interaction.
o A patient can have multiple interactions with the chatbot.
 5

4. Entity-Relationship Diagram

ERD diagram
Explanation of the Diagram:
 Entities: Represented by rectangles.
 Attributes: Listed within the rectangles. Primary keys are underlined.
 Relationships: Represented by lines connecting entities.
 Cardinality: Indicated by crows feet or numbers on the lines (e.g., one-to-many, many-to-many).
This ERD provides a conceptual blueprint for the database structure of the ABC Hospital Network. It can
be further refined based on specific requirements and implementation considerations.