Bright smile surgery system - Coursework Example

Bright Surgery s s Grade 13th October Bright Smile Surgery System Analysis Report Activity diagram of Bright surgery Assumptions made are all patients who call the reception list are either in need of booking an appointment or rescheduling an appointment. The activity diagram above tries to show the process followed by a client before getting treated. The system assumes interaction between patients and the hospitals begins when the patient makes a phone call to the hospital through the reception desk.

In this call, it is assumed that the patient might be willing to make an appointment to see the dentist. The receptionist collects the patient’s details and validates to see if the patient is an existing patient or a new patient. The receptionist then moves forward to give the patient, issuing an appointment date. The patient is reminded of the appointment through mails by the system. After that, on the date of the appointment, the patient visits the hospital where the receptionist checks whether the patient had an appointment.

If the patient had an appointment, the reception lists checks whether the client is new or an old patient continuing with the treatment. In case of a new patient, the reception lists collect more information about the patient to add on what had been collected during the phone call. The patient then sees the doctor to receive treatments. The doctor is supposed to bill the patient. Use case diagram Actors These are the different people who interact with the system. They carry out different activities using the system. 1. Doctors 2.

Hygienist 3. Receptionist 4. Patient Use cases These are the different activities that are carried out using the system. 1. Register patient 2. Bill patient 3. Send remedy to patient 4. Reschedule appointment 5. Book appointment 6. Send appointment remedial 7. Create schedule Use case diagram This system mainly interacts with the hospital’s staff and patients. The patients can request for an appointment through the system. The hospital’s staffs are supposed to get the different schedules form within the system before giving any appointment.

Billing of the patient is automated to make sure it becomes easier. The doctor is supposed to fill the details with the prescription and then a bill is processed within the system. This ensures integrity and uniformity in the billing methods. Registration of the patient is also carried out within the patient. This is done by the patient supplying their details, which are stored within the system for future references. The use case specification for booking an appointment The diagram shows the interactions between the hospital’s staff and the patient for completion of an appointment.

The patient first applies for an appointment after which his or her information is verified. After the verification of the details, there is a need for looking at the schedule that the patients want to be allocated, to determine availability. If the schedule is available, the patient is allocated. If the schedule is not available, the application is rejected. Finally, the patient is replied to being informed on whether the requested schedule is available or not available. The complete gaining of the appointment involves the patient as the actor and the system.

Primary actor Patient Trigger The trigger of this event is the client when he or she wants to make an appointment. They trigger the event by calling the reception. Normal flow of event 1. Patient applies for appointment 2. Reception person confirms the details Exception flow 2b. The reception person takes the details and records them manually and does not move on with the process. 3. A check for availability of space is done according to the client details 4. The appointment is either accepted or rejected by the hospital Class diagram for the hospital The class diagrams show the different classes that the system has.

The first class that exists within the system is the “person class”. This class holds general information about all0020persons involved in the system. This information includes the name, contact, age, date of birth, address and phone number. This class is inherited by the class patient, doctor, hygienist, and receptionist. These classes then include additional attributes, which only belongs to them and cannot be shared with others. The class hygienist is charged with the responsibility of setting the qualification and the section he or she works.

Another class is the availability of the schedule. This class is supposed to hold details of the different schedules that can be allocated to patients. This class is supposed to create schedules and allocate the schedules to the different patients. The class “bill”, which is also included, is supposed to show the total amount the patient owes the hospital, after treatment or consultation. The class has a relationship with the ‘doctor class’ and the ‘patient class’. The doctor bills the patient using this class while the patient has an association of being billed (Quatrain, 1999).

References Quatrain, T. (1999). Visual Modeling with Rational Rose2000 and UML. New York: Addison Wesley Longman.