Assessment Criteria/Mark Scheme
- LO1: Demonstrate in-depth knowledge and understanding of current best practice in the design and development of Object Orientated systems
- LO2: 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.
- LO3: Implement and test Object Orientated programmes using advanced techniques ensuring a high level of quality and data security.
- LO4: Critically evaluate the effectiveness of implemented Object Orientated applications
- LO5: Demonstrate a professional understanding of the importance of software quality in the development of applications.
Assessment Criteria/Mark Scheme:
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 the deadline specified on the first page. 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. It is your responsibility to make sure that the project can be loaded from a decompressed zip. 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.
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.
It is your responsibility to check that you have uploaded the file correctly to the ELP/turn-it-in. After uploading the file to the ELP, download the file and check that the contents are what you expect.
You must check you work does not contain any viruses before submitting.
The maximum size of a group is four students; 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 or more members are 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 which is willing to accept them and that there is still enough time to make a sufficient contribution to the new group (group size limits still apply). In such cases the module tutor must be notified. If your group is not working well together then you must inform the module tutor no later than week 10.
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.
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”. If you have changed the code, however it is not radically different from the original copied code, you still need to mark it in the same way.
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.
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.
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. Please make sure you read the questions carefully and that you answer matches the question being asked. If you require further clarification please email the module tutor.
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.
You must also supply one peer-assessment form for each group member. This will need to be agreed and signed by each group member. The peer assessment template is available on the module web page. Completed forms need to be scanned or photographed and need to be uploaded as part of your group work assessment.