Understanding and Abstraction

into Classes and Interconnections

Assignment 1
AU22B1041
1. Describing the Entire application Inputs, Outputs and Processes
involved with complete Problem Definition.

Inputs:
1.Inventory Management (Pharmacy):
• Item IDs and quantities for updating inventory.
2.Patient Record Management (Admin):
• Patient information such as name, date of birth (DOB), medical condition.
3.Billing Department Management (Billing):
• Patient IDs for generating invoices.
4.COVID Identification and Probability (R&D):
• List of symptoms with corresponding values for COVID probability
calculation.
5.Insurance Management (Third Party):
• Patient IDs and claim amounts for processing insurance claims.
1. Describing the Entire application Inputs, Outputs and Processes
involved with complete Problem Definition.

Outputs:
1.Inventory Management (Pharmacy):
• Updated inventory status.
2.Patient Record Management (Admin):
• Patient records created and managed.
3.Billing Department Management (Billing):
• Invoices generated for patients.
4.COVID Identification and Probability (R&D):
• Probability of COVID-19 based on symptoms.
5.Insurance Management (Third Party):
• Processed insurance claims.
1. Describing the Entire application Inputs, Outputs and Processes
involved with complete Problem Definition.

Processes Involved:
1.Inventory Management (Pharmacy):
• Update inventory based on item IDs and quantities.
2.Patient Record Management (Admin):
• Create and manage patient records with name, DOB, and medical
condition.
3.Billing Department Management (Billing):
• Generate invoices for patients based on patient IDs.
4.COVID Identification and Probability (R&D):
• Calculate COVID-19 probability using symptom data.
5.Insurance Management (Third Party):
• Process insurance claims based on patient IDs and claim amounts.
2. Abstraction ( Identification of correct classes and their associations) to
implement the project.

•Hospital class: This class represents the hospital as a whole. It has

associations with the other classes, such as the Inventory class, the
PatientRecord class, the Billing class, the COVIDIdentification class, and the
Insurance class.
•Inventory class: This class represents the inventory of the hospital. It has
associations with the Pharmacy class and the Billing class.
•PatientRecord class: This class represents the patient records of the
hospital. It has associations with the Admin class and the Billing class.
•Billing class: This class handles the billing for the hospital. It has
associations with the Inventory class, the PatientRecord class, and the
Insurance class.
•COVIDIdentification class: This class identifies COVID-19 patients. It has
associations with the R&D class and the Insurance class.
•Insurance class: This class handles the insurance for the hospital. It has
associations with the Billing class and the COVIDIdentification class.
3. Features and Methods available within classes

1.InventoryManagement:
•updateInventory(int itemId, int quantity)
2.PatientRecordManagement:
•createPatientRecord(string name, string dob, string condition)
3.BillingDepartmentManagement:
•generateInvoice(int patientId)
4.CovidIdentification:
•calculateProbability(vector<float> symptoms)
5.InsuranceManagement:
•processClaim(int patientId, float amount)
4. Classes Messaging and Interconnections.
5. Graphical User Interface and Main Flow of the Project

4. Classes communicate to each other when needed, e.g., billing might depend
on patient records and insurance might depend on patient IDs.

5. 1.GUI: The application could have a user interface to input data for different
functional areas.
2.Main Flow:
• Users input data for inventory updates, patient records, billing, symptom
data, and insurance claims through the GUI.
• The application processes the input data through respective classes'
methods.
• Classes interact to perform necessary actions (e.g., billing requires
patient records).
• Results are displayed through the GUI.