User Case Diagram: Description: A new hospital is seeing an increase in the number of its…
User Case Diagram: Description: A new hospital is seeing an increase in the number of its patients. You are required to create a software system that manages the employees and patients. A part of their software requirement is given below. You also are required to do self-study on how the out-patient departments of hospitals function and create a design for managing the department.
Requirements: The people in the clinic are either employees or patients. The roaster for an employee is created every week and the system reports if any employee has worked less than 40 hours in a week. The hospital works in three shifts, each of 8 hours. The first shift starts at 7 am and employees are required to punch in. All employees work only in one of the three shifts in a day. The employees are either Administrative Staff, Operations Staff, or Technical Staff. A patient approaches the front desk and registers to see a doctor based on availability and the receptionist issues a number to the patient to wait in a queue. A patient is then met by the Operations staff, i.e. the doctors, surgeons, or nurses. Based on the outcome of the consultation the patient goes to the front desk to finalize the payment of their visit and exit the system. The patient is given a report, which includes the name of the doctor and nurse that attended the patient. The hospital also has Technical Staff, who are the surgical technologists that deal with surgical equipment and technicians that manage other office equipment. All relevant details like IDs, names, salaries, addresses, and phone numbers, of the patients and employees, are stored in the hospital system. At any point in time, the system is able to generate reports to show the details of employees that are on a particular shift, the number of patients that are in the queue, and the number of patients or technical issues handled by each employee.
• Class Design : The UML class diagram, with class relationships, and cardinality for the business case is provided. Each relationship is explained, and assumptions are listed.