Design and Develop Object Oriented Systems

Knowledge & Understanding:

1.Demonstrate in-depth knowledge and understanding of current best practice in the design and development of Object Orientated systems

Intellectual / Professional skills & abilities:

2.Design a system using advanced object orientated principles and methods, such as Behavioural, Creational and Structural design patterns, ensuring a high level of quality and data security.

3.Implement and test Object Orientated programmes using advanced techniques ensuring a high level of quality and data security.

4.Critically evaluate the effectiveness of implemented Object Orientated applications

Personal Values Attributes (Global / Cultural awareness, Ethics, Curiosity) (PVA):

5.Demonstrate a professional understanding of the importance of software quality in the development of applications.

Assessment Criteria/Mark Scheme:

See Appendix A for assessment criteria. Note that this work is worth 100% of the module and that the marks total 100 marks.

Nature of the submission required:    

Individual work:  The individual report should be a single document, and it must be in  PDF format. You are required to upload this using Turn-it-in (ELP) as an originality report is required. Your work must be uploaded no later than 2nd January 2021. You should name this file so that it is clearly your individual work and should contain your student ID as part of the document name.

Group work: A ZIP file should be created that contains your entire Visual Studio project, including the test project. Justifications of choices made such as patterns used and the data access layer need to be in a PDF document called justifications. The document should be in the root of the folder, you also need to supply a file which contains a list of all names and student ids of the group members “group.txt”.

Each C# software component should have the names of the group members within the comments at the top of the code. The ZIP file should also contain files for your Design (Task 2) and Testing (Task 4) these should be in PDF format and need to be legible (easy to read) it is your responsibility to check the PDF files are legible.

Please note that the compression format has to be zip, you must not use: ‘rar’, ‘7z’ or compression formats.

Late work carries a penalty. Even if you are one minute late, the penalty has to be applied. Please make sure you give yourselves plenty of time to upload the work. Multiple submissions are possible.

Demonstrate in-depth knowledge and understanding of current best practice in the design and development of Object Orientated systems

It is your responsibility to check that you have uploaded the file correctly to the ELP. After uploading the file to the ELP, download the file and check that the contents are what you expect.

Cite them Right can be found here

Group work

The size of a group can be between two and six students, no groups may be larger than six but may be less; you are expected to form your own groups by the end of teaching week 4. One member of each group must email the module tutor giving the names of the group members. Anyone without a group at the beginning of week 6 will be assigned to a random group. In the rare event that a group is not working well together it may be disbanded. The module tutor will have final say when this occurs, It will only happen if there is sufficient documented proof that one member is not contributing to the work, in such eventualities it will be expected that each member does the remaining work on an individually basis, Alternatively students may be able to join another group who is willing to accept you and that there is still enough time to make a sufficient contribution to the new group. In such cases the module tutor must be notified.  

Expected size of the submission:

Expected size of written work is stated on the individual sections.

Academic Misconduct:

You must adhere to the university regulations on academic misconduct. Formal inquiry proceedings will be instigated if there is any suspicion of misconduct or plagiarism in your work. Refer to the University’s regulations on assessment if you are unclear as to the meaning of these terms. The latest copy is available on the university website. Quote or paraphrase other work with caution. Please discuss with the module tutor if you are unsure what is expected.

Handbook of Student Regulation can be found here

Fair use of code from the internet:

You are not permitted to use templates from the internet; any group which uses a template to create the architectural foundation of their work will be formally investigated for academic misconduct, all the work must be your own.

Small amounts of code can be taken and modified from the internet however all occurrences must be clearly indicated in the comments section at the top of each class. You must including in the comments section a reference to the original source. Methods and properties should also be marked as “copied from: URL” or “biased on: URL” if they have originated from an external source.

Monitoring of assessment progress:

You are required to use github as a repository for your assessment. Your progress on the assessment will be monitored it is important that the group work is started early, groups which have not made sufficient progress can expect emails, you will be required to give the module tutor access to the github project at the commencement of the technical part of the assessment.

Reflective writing:

Tasks 5 and 6 are reflective writings; although many of you are aware of what reflective writing is. Past evidence indicates that some students do not understand what is required. It is not about ‘book work’ where your answer is basing on external sources, although you should use some academic papers to support your arguments. These questions are about what you and your group have done and what you have learned from the process. You are required to indentify positives and weaknesses in the group work.  Use the theory covered in the module to effectively aid you in this reflective evaluation of your work. The reflective commentary should be critical; you should identify what when wrong and demonstrate you have learned from the process.

Extensions and Illness:

Please make sure that all group items are held in a central repository so that it does not rely on a single individual. If someone in your group is ill then you must all discuss the possibility for extensions with Ask4Help. Module tutors and Course leaders cannot grant extension, you must go to Ask4Help.

Individual and Group components

Each task clearly states if the task is individual or group work. Submission of individual work will be at the same time as group work however these will be separate submission.

Peer Assessment and Group Diary

In order to complete the group work you will need to work with other students. It is important that you evenly distribute the work between yourselves and work effectively with each other.  You are required to keep a diary so that you log and minute all communication and meetings. The diary will be required as part of the evidence in the portfolio. Given the current situation regarding covid-19 you will be required to hold group meetings using software such as zoom or teams.

Background

Radiant Smile Dental practice requires you to build a windows application to support dental practice. The dental practice only deals with NHS patients however it does offer a number of treatments not covered by the standard NHS services such: teeth whiting, dental implants.   

Design a system using advanced object orientated principles and methods, such as Behavioural, Creational and Structural design patterns, ensuring a high level of quality and data security.

Patients

When a patient is registered their details such as date of birth, name, address, email are captured and stored by the system. A medical questionnaire is given during the registration process. The questionnaire captures information regarding any medical conditions which may affect the treatment and any allergies the patient may have such as to latex or antibiotics.

When a patient visits the dental surgery a check is done to see when they last updated their medical history. If this was more than a year ago the system will prompt the reception staff to ask if they has been any changes to their medical history. If there has they will be required to fill in a new medical questionnaire.

All patients must provide the name and address of their GP practice. It is likely that many of the patients in the dental practice will be register to a small number of local GP practices.

All treatments private / NHS should be easily maintained by the practice staff. This may be the change of pricing in line with changes to the NHS fees. It could also include new private services or accommodate a change in price due to a special offer.

Checkups (15 minute appointment)

Checkups can be booked in one of three ways

·When a patient comes to the end of a treatment plan of has had a check-up which requires no work they are offered an opportunity to book a six month check-up.

·When they first register with the practice.

·If they telephone in and ask for a check-up, a check is made to make sure they have not already had a check up within the last four months.

In the case of new patient or coming to the end of the treatment plan, the system must prompt the reception staff to ask the patient to make an appointment.

The system should identify any patients who have not visited the dental practice in the past six months and have no future appointments books. The system will produce a reminder letter which will be mailed out to the patient asking them to make an appointment. They will be contacted again is six months if they have not made an appointment and has not visited the dental practice.  

Any patient who has not made contact with the dental practice for a two year period will be removed from the list of active patients.

Implement and test Object Orientated programmes using advanced techniques ensuring a high level of quality and data security.

Emergency Appointments

A practice holds 2 hours non advance appointments each day; these are for dental emergencies and are allocated on a first come first served basis.  

Recording a treatment plan

A person will have 32 adult teeth, and when they are younger 20 baby teeth. During someone’s life the state of the teeth may change: all the way from a filling to an extraction.

The system should only record information only about a ‘treatment plan’ the work identified as needing to be carried out following an examination.

The dentist will fill out a visual representation on a pre-printed view of the teeth so that the patient is aware of what is going to be done. This visual representation is not recorded by the system instead the dentist makes professional medical notes. These medical notes will be short multi line text documents which are written in such as way that any trained dentist will understand.  

Treatment plan consent and payments

Many NHS patients will pay a fixed free for the detail service which is split into three bands. Some patients are entitled to free treatment, depending on their individual circumstances. In both cases the patient signed a standard NHS form consent/treatment form, these are scanned and a copy is held on the system.

In the event of an emergency appointment this may be done immediately after the treatment is carried out.    

Appointment Reminders

The practice has suffered from many missed appointments, patients forget about appointments which are often set weeks or months in advance. In order to try and solve this problem SMS text message is sent to the patient five working days before the appointment, and another is send the day prior to the appointment.

It is also policy to phone parents who have long appointments. Some dental work may require 40 or more minutes to complete. Patients who have long appointments are contacted by phoned by a member of the reception team to double check that they will be attending. This normally takes place two working days before the appointment.

A third party service is used to contact patients via SMS text messages. The system should provide the following text document which will be sent to the service. The text document contains a list of the reminders to the sent that day; it has the mobile phone number and the day/time of the appointment. This should be in the form of a comer delimited file.

The system will also produce the list of phone numbers, names and appointment details for all those who have a long appointment in three working days time. This will be processed by the reception staff during quiet periods. Reception staff should be able to mark those who have been successfully contacted, those who have not been contacted by the end of the day will appear on the following day’s list. No further attempts will be made if they are not contacted on the second consecutive day.