OOP system for dental practice.

Object Oriented Design for Priory Council Dental Practice

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 Priory Council Dental Practice. You should demonstrate a broad understanding of Object Oriented design principles and UML techniques and you should apply them on the design of the following components:

· Use case diagram

o Show one use case diagram with all primary use cases for PCDCP information system. Remember that the system box only appears on the top-level diagram (i.e. PCDCP system) and should contain use case ovals for all primary use cases such as register patient, book appointment, update booking details etc.

· Use case documentation

o Detailed use case description for the five primary use cases stated in your overall case diagram such as patients’ data registration and update, etc.

o Brief description for all other use cases

· Conceptual class diagram

o Show conceptual classes, associations with names (e.g. booking class), functions (e.g. update), and significant attributes such as in booking class you would have booking id, date, type (regular/urgent) etc.

o Show generalization, abstract conceptual classes, association classes, and aggregation if applicable

o Provide a brief description of all conceptual classes and main attributes

· Interaction diagrams

o Sequence and collaboration diagrams including boundary and control objects/classes needed for the interaction diagrams based on primary use cases e.g. how to perform a booking, cancel, fine, and/or exclusion from the PCDCP system.

o Activity diagram based on a primary use case e.g. register in the system, book appointment etc.

o Describe the proposed designs and justify your decisions.

Assignment Preparation Guidelines

Deliverables: Coursework 1

Coursework 1 (is worth 60% of the overall assignment) an individual report and will be submitted as a Microsoft Word file (suggested word count: 2000 words in total including all diagrams, documentation and description) via Turnitin on Moodle and must include all the required components related to the proposed design.

Word count

Don’t exceed the word count

You need to state the word count at the end of their assignment. 10% over the stated word count is permitted without penalty.

If students go beyond this, then there is a penalty of 5 marks for every additional 10% beyond the word count with a maximum of a 15 mark penalty reduction.

There is no specific penalty for submitting a piece which is below the word count, but please note that shorter submissions are likely to attract poorer grades, particularly where they lack the necessary depth of analysis.

How do you calculate the word count?

The word count includes the Abstract or Executive Summary and all in-text citations. The word count does not include the Bibliography and Appendices.

Please note that Appendices should only include supplementary information, not information critical to your work.

The marking criteria and assignment guidance is outlined below.

Marking Criteria – Coursework 1

Functionality	Criteria/Deliverables	Marks
Use case diagram	· list of main functional requirements · one comprehensive use case diagram with all actors, primary use cases and relevant associations	20
Use case documentation	· house style use case descriptions for two primary use cases · brief description of primary use cases (up to 10)	15
Class diagram	· conceptual classes design with names, functions and significant attributes · illustration of relations including standard association, multiplicities, inheritance, composition and aggregation - if applicable · brief description of all conceptual classes	30
Interaction diagrams	· one UML sequence diagram · one collaboration diagram · one activity diagram · brief description and justification for the proposed diagrams	35
Total		100