All students who wish to exit at the ordinary degree stage are required to submit a report together with a presentation and a demonstration of their completed work. The project focuses on the three stages of system development, namely analysis, design and implementation. The software system must meet the requirements of an ordinary degree. Each student is required to generate their own project idea. They are then required to expand this idea into a formal project proposal. If the proposal is of an acceptable standard the student may proceed with the project. The student should produce a project manual, containing details of analysis, design, implementation, testing and deployment (if appropriate). The students are provided with guidelines which explain the exact requirements of the project.
An interim report is submitted by the student when the research and analysis phases of the project are completed. At the end of the project the student submits the system software and a project manual documenting the project. The student also makes a formal presentation of the report and a demonstration of their completed work.
The aim of this module is to enable the student to complete an individual software project. The student is required to use the skills that they have developed from previous modules to analyse, design and implement a substantial software system. The use of best practice and software tools is strongly encouraged.
The student is free to pick their own project topic, so the precise content is not mandated. However, the content must contain a significant software component.
Each student is assigned a supervisor. The student must meet the supervisor on a weekly basis. The supervisor will provide project guidance. The bulk of project work requires self-study.
Projects are assessed under a number of categories, which are outlined below:
- Interim Deliverable (Requirements & Design Document)- the quality of the student’s analysis and design work. This deliverable will be submitted before the end of the first semester.
- Implementation – this is broken down into two areas:
-
Completeness and Complexity - some projects are by nature technically more complex than others. In such cases, these projects are not required to be as complete; this category reflects how complete a particular project is, with respect to its complexity.
-
Achievement - the value and the usability of the project, including the report and any software designed and implemented.
-
- Testing - the quality of the student’s testing approach and implementation e.g. unit testing, integration testing, user acceptance testing etc.
- Project Report - the quality of the student’s project report.
- Presentation- the quality of the student’s presentation of the report and demonstration.
| Module Content & Assessment | |
|---|---|
| Assessment Breakdown | % |
| Other Assessment(s) | 100 |