mattanderson97/software-engineering-2017

software-engineering-2017

Assessment overview

The manager of the Over Surgery would like to change the existing paper based system used by the receptionist with an electronic system. The receptionist should be able to:

• login into the system
• check the GP or nurse’s availability on a specific day;
• check all the GPs and nurses on duty on a specific day;
• register a new patient by entering their details; after registration the system should generate an unique patient ID
• find a patient that can provide either the patient ID or the name and date of birth or the name and the address;
• book, change and cancel an appointment for a patient;
• extend the prescriptions for a patient; the list of medications the patient is on should be displayed and the receptionist should extend what the patient asks for and can be extended (there are prescriptions that can be extended only once a month for instance).
• check and print the results of the tests the patent did.

Intended learning outcomes for the assessment

• Apply and critically appraise software engineering approaches to developing software applications.
• Understand key object-oriented design principles.
• Demonstrate an understanding of and apply current theories, models, and techniques that provide a basis for problem identification and analysis, software design, implementation, verification, and documentation.
• Work effectively as part of a team to design, develop and deliver quality software artefacts.
• Use a software development environment supporting the development of computer programs to develop a software application.

Marking scheme

• Homework element (10 in total, one in each week between weeks 2-11) Value: 10% of 100
• Presentation of final solution in your timetabled lab session from week 12 Value: 5% of 100
• The report (see below what it has to contain), your own logbook and a CD/memory stick with the whole application. Value: 85% of 100. This is detailed below. Problem Definition Document and Description of the Software Requirements Value: 10% of 100 Case Study Description, Current System Description, Project Aims, Project Plan Software Design Value: 20% of 100 Software Implementation Documentation Value: 30% of 100 Testing Value: 20% of 100 Plan of the Software Maintenance Value: 5% of 100

software-engineering-2017's Issues

Database Problem

There are some inconsistencies between the example database and the instructions given for making the database in the lecture notes. I've done all I can with it for now. Hopefully, the issues are cleared up in the lecture on Wednesday, if not we can ask on Friday.

To-Do List

TO-DO:

Get application ready for presentation.