Registry
Module Specifications
Archived Version 2003 - 2004
|
Module Title |
Project
|
|
Module Code |
CA400
|
|
School |
School of Computing
|
Online Module Resources
|
|
Level |
4
|
Credit Rating |
15
|
|
Pre-requisite |
CA465
|
|
Co-requisite |
None
|
|
|
Module Aims
|
To allow the student to develop a reasonably large software system
or
To allow the student to carry out some element of research and investigation under the direction
of a member of academic staff. This investigation is carried out in such a way that it is thorough
and detailed and will involve some element of independent analysis of findings. The investigation
will be reported through documentation and a final presentation of results.
|
|
Learning Outcomes
|
Having completed this module the student will have been able to put into practice some of the
theoretical work covered in earlier years and in the final year of the programme and have been
able to gauge the value of this.
|
|
Indicative Time Allowances
|
|
|
Hours
|
|
Lectures |
0
|
|
Tutorials |
0
|
|
Laboratories |
50
|
|
Seminars |
0
|
|
Independent Learning Time |
175
|
|
|
|
|
Total |
225
|
|
Placements |
|
|
Assignments |
|
|
|
NOTE
|
Assume that a 15 credit module load represents approximately 225 hours' work, which includes all teaching, in-course assignments, laboratory work or other specialised training and an estimated private learning time associated with the module.
|
|
Indicative Syllabus
|
|
In the final year project students work individually or in small groups and may take one of a
number of approaches to their project:
Students normally develop a software application which addresses some real practical or
research problem. The problem addressed may have been specified by a member of Faculty,
may have been the student's own idea or may have been specified by an outside organisation.
Students may address some research problem requiring some combination of a literature search,
data analysis, evaluation or comparison of systems, analysis of findings, and so on.
In all cases, assessment of the project is by a panel of academic staff and students either
demonstrate their software application or present the findings of their other work. Assessment is
also based on other submitted documentation including, where appropriate, functional
specification, technical manual, user manual, code or equivalent and research manual.
|
| Assessment | | Continuous Assessment | 100% | Examination Weight | 0% |
|
|
Indicative Reading List
|
|
Essential
Supplementary
|
|
|
|
Programme or List of Programmes
|
| CACSSE | BSc in Computer Apps (Comp Sci-Soft Eng) |
| CAE | BSc in Computer Applications (Evening) |
| CAIS | BSc in Computer Applications (Inf.Sys.) |
| Archives: | |
