(Solved): The Scenario: Harlow Dental Care House...

Firstly, read the scenario below and then design and evaluate a solution using an object-oriented analysis and design approach. You should use Unified Modelling Language (UML) for specifying, visualizing, constructing, and documenting the proposed systems.

The Scenario: Harlow Dental Care House

Harlow Council has built a new Central Dental Care House in the city and they want to create a new digital information management system instead of the old one, which uses Microsoft Word to manually record, search and update data. The director now feels that a fully computerised system is needed as it would give better support to their operations and better services to their customers.  It is expected that staff will use the new system to support and record the tasks they carry out; including booking, deleting, updating appointments, managing and organising the use of business resources, logistics, and facilities. 

All users should log in to the system before they can use it. Customers, administrative staff and doctors can book or cancel appointments online.

A booking can only be confirmed if there is an available slot. Any confirmation message should include all relevant information such as the doctor’s name, day, time and date of appointment. 

If the customer is a new one, their name and contact details should be taken and recorded in the system, along with other relevant details such as gender, age, medical notes. 

Administrative staff and customers will be able to review the booking history, payments already made, and their current balance as well. Doctors will also be able to see a patient’s treatment history.

The director thinks that it would be helpful if the new system alerted the customer automatically, when their balance is lower than £10.

The administration staff usually deal with the scheduling and booking of appointments, along with enquiries.  In addition, they should be able to appoint alternative doctors for patients in case the regular doctor is absent. The system should notify the administrative staff automatically once a booking cancellation takes place.

The manager should be able to organize the logistics and equipment of the surgery and should be able to update the system with all available tools and devices required to treat patients.

Part1 System Design

You are required to analyse the requirements of the new system and design the main components (e.g. overall system use case, class diagrams, interaction, sequence and collaboration diagrams) for the booking system. You should demonstrate a broad understanding of Object Oriented design principles and UML techniques, and apply them on the design of the following components: 

• Use case diagram
  • Show one use case diagram with all primary use cases for HDCH, which should show all actors involved and contain all primary use cases such as booking appointments, registering patients, updating details, etc.
  • Detailed use case description for two primary use cases stated in your overall case diagram, such as booking or cancelling appointments. 
  • Brief description of 10 primary use cases. 
• Conceptual class diagram
  • Show conceptual classes (e.g. user class), associations (e.g. composition), main functions (e.g. register), and significant attributes, for example in the user class you would have username and email.
  • Show generalisation, specialisation, multiplicities, associations including composition and aggregation, if applicable.
  • Provide a brief description of all conceptual classes.

• Behaviour diagrams
  • Sequence diagram for a specific activity, such as how to book appointments
  • Collaboration diagram for specific activities, such as how to cancel an appointment.
  • Activity diagram for a primary use case such as confirming a booking.
  • Briefly describe the proposed designs and justify your decisions.

Deliverables: Part 1

Part 1 is a report and will be done as a word document (2000 words in total including all diagrams, documentation and description).

All components (text, diagrams. code etc.) must be submitted in one word file (hand written text or hand drawn diagrams are not acceptable), any other accompanied materials such as simulation file, code, etc. should be attached in appendices.

Standard and commonly used fonts such as Times New Roman, Arial or Calibri should be used, font size must be within the range of 10 to 15 points including the headings, body text and any texts within diagrams,

The report is to be concise and technical. Needs to be an analysis, compare and evaluation rather than simply described.

All figures, screenshots, graphs and tables must be numbered and labelled.

Material from external sources must be properly referenced and cited within the text using the Harvard referencing system,

The report should be logically structured, the core of the report may start by defining the problem / requirements, followed by the proposed solution including a detailed discussion, analysis and evaluation, leading to implementation and testing stage, finally a conclusion.

Screenshots without description / discussion does not constitute understanding and maybe assumed irrelevant

Preparation Guidelines

 Part 2: Review and Evaluation Report

You should also review and evaluate the processes that you modelled and also their outcomes including recommendations for improvements.

Your evaluation report should show evidence of your reading and research and use Harvard referencing. This is a chance to look back on what you have done and to revisit the key design and technical decisions you made.  Were they the right decisions or would you do something differently? You should also discuss the lessons you have learnt from the exercise and how you would use them to implement them in further projects.

All components of the requirements (text, diagrams. code etc.) must be included in one word file (hand written text or hand drawn diagrams are not acceptable), any other accompanied materials such as simulation file, code, etc. should be attached in appendices.

Standard and commonly used fonts such as Times New Roman, Arial or Calibri should be used, font size must be within the range of 10 to 15 points including the headings, body text and any texts within diagrams,

Material from external sources must be properly referenced and cited within the text using the Harvard referencing system,

The report should be logically structured, the core of the report may start by defining the problem / requirements, followed by the proposed solution including a detailed discussion, analysis and evaluation, leading to implementation and testing stage, finally a conclusion.

Screenshots without description / discussion does not constitute understanding and maybe assumed irrelevant.

All related material must be attached as an appendix in the final document, including any computer generated document, software/ code, simulation file etc.