Coursework: Activity Diagrams, Use Cases and Class Diagrams
Deadline: 09:30, Thursday 17th of November 2011)
(BSS) is a new dental surgery located in central London. BSS has four dentists, one hygienist, and two receptionists working full time. They are embarking on developing a new software system to support their basic needs (managing patients, their treatments, and appointments), as they are unhappy with the services that they could buy off the shelf. You are responsible for creating a specification for this system. Below you will find a description of how they operate.
Whenever patients are seen for the first time, they complete a patient information form that asks their name, address, phone number, date of birth, details of their General Practitioner (GP), information on their previous dentist, and a brief medical history, which are stored in the patient information file. When a patient calls to schedule a new appointment or change an existing appointment, the receptionist checks for an available time slot. Once a good time slot if found for the patient, the appointment is scheduled. If the patient is a new patient, an incomplete entry is made in the patient file, containing only the name, telephone number and address; the full information will be collected when they arrive for their appointment. Because appointments are often made far in advance, a receptionist usually mails a reminder postcard to each patient two weeks before their appointment.
Immediately after each appointment, brief details on the treatment received (selected from a standard list) and amount due are entered in the system. Once payment for a treatment is received, that information is reflected in the system. Every other week, a receptionist will send letters to all patients with an outstanding bill to pay.
At the end of each month, every patient that has had their last check-up between four and twelve months before is sent a reminder postcard to book their next check-up. 2
II. The Task
1. Create an activity diagram for the system described above.
2. For the BSS system described above, you should produce a use case model.
a. Identify the main use cases.
b. Produce a use case diagram. This should include system, actors, use cases and all relationships. If appropriate to simplify and/or clarify the model, you might also use include and extend relationships, as well as use case and/or actor generalisation in your diagram.
c. Provide the use case specifications covering the processes followed when a patient is interested on booking an appointment with BSS.
You may include a glossary for clarity. The complete use case model, including any clarification notes, must fit in at most 4 pages (font: Times 10 or larger; margins: 2.5 cm or larger); it may well fit in fewer pages.
3. Produce a class diagram for BSS (containing only entity classes). Include attributes, operations, types associations, multiplicities, roles and association names as appropriate.
III. Criteria for Marking
Coursework submissions must follow the submission guidelines below in order to be marked.
Marks will be allocated for (in order of decreasing priority):
correctness: how well your set of models matches the requirements given for BSS. If the requirements are incomplete, you must state any suitable assumptions that you made to fill the gaps. Pay attention to consistency between and within your models. A submission that correctly represents the requirements, and uses UML correctly, guarantees a pass mark.
good readability: ability to give a clear but concise description, conveying the required information without being too verbose; and especially good use of UML features to achieve this goal
adherence to the style rules taught.
Also pay extra attention to make your various models consistent with one another. 3
The diagrams must be computer-generated so as to be completely readable, using a UML diagram drawing package.
or any generic drawing package. You