CO531 Software Engineering Practice. Where it is not possible to take CO531 at Stage 2 it may be taken at Stage 3 as a co-requisite.
In the event of failure no alternative assessment will be available. Credit can only be retrieved by repeating the module. Where it is not appropriate for a candidate to repeat the module, the School reserves the right to require a candidate to take an alternative module as substitute.
OverviewThe project gives you the opportunity to follow and develop your particular technical interests, undertake a larger and less tightly specified piece of work than you have before (at university), and develop the project organisation, implementation and documentation techniques which you have learnt in other modules. The technical and professional aspects of project courses are seen as particularly important by both employers (who will often bring them up in interviews) and by professional bodies.
The project may be self-proposed or may be selected from a list of project proposals. Typically, a project will involve the specification, design, implementation, documentation and demonstration of a technical artefact. The project is supervised by a member of the academic staff, who holds weekly meetings with the group, during which s/he will give general advice and will assess the progress of the group and the contributions by individual students.
Project deliverables are:
- a technical report, in the style of an academic paper, describing the scientific/technical outcome of the project;
- a well-indexed corpus of material that supports the achievements claimed.
In addition, each individual prepares a report outlining his/her contributions to each of the various aspects of the project. This report should not be a repeat of other material delivered as part of the project, but an assessment of the progress of the project and reflections on what the individual has learnt from undertaking it. In particular, it should include a description of the particular activities and outcomes that individual has contributed to the project, and of how the group worked together. This report will be discussed at a viva voce examination which should include a short presentation/demonstration of the project.
This module appears in:
- Computing Stage 2/3 Canterbury
- Computing Stage 2/3 Medway
- Humanities Undergraduate Stage 2 & 3
- Social Sciences Undergraduate Stage 2 & 3
- STMS Undergradute Stage 2 & 3
The project constitutes one quarter of the year's work and a student is expected to expend about 1¼ days each week on it. Each group has a weekly meeting with their project supervisor which supports students in their self-learning and indicates appropriate resources.
CO600 is only available to students registered for an Applied Computing Joint Honours Programme, and it or CO620 is compulsory in Stage 3.
The module web page contains further information together with notes of guidance which all students taking this are advised to read
An in depth understanding of particular technical topics (for instance, use of a particular programming language, or software development tool, component architecture or mathematical technique) beyond that obtainable from the rest of the programme
An enhanced understanding (gained from practical experience) of project organisation,implementation and documentation techniques (as studied in other courses)
The ability to specify, design and implement a computer-based system;
The ability to evaluate and choose between potential solutions to a technical problem
The ability to evaluate and deploy appropriate tools and techniques
An appreciation of the dynamics of working in a group
Oral presentational skills
Ability in writing technical reports
Ability to acquire technical knowledge and understanding in an independent fashion
Ability to reflect on and evaluate work performed