Course Information Undergraduate prospectus

Project (CIS)

Course summary

Course code: COMP1682
Level: 6
Credits: 60
School: Architecture, Computing and Hums
Department: Computing and Information Sys.
Course Coordinator(s): Keeran Jamil

Specification

Pre and co requisites

To have passed Level 5 of an appropriate programme

Introduction and rationale

Prospective employers often require that the student is able to tackle a non-standard problem, organise their work, show a a high level of commitment with an awareness of their target audience and present their conclusions both orally and in a written report. Similarly, admissions tutors for Postgraduate courses and Research awards need to be reasonably certain that an applicant will be able to employ these same skills in order to carry out research and put those results in a thesis. This course is designed to provide students with the opportunity to carry out an individual piece of supervised work, a pre-determined, templated project or an industry work practice project with an agreed topic relevant to their degree.

Aims

The aims of the course are to:
Provide the student with the opportunity to research, specify, design, implement and test a software product to an appropriate level of professional competence.
Encourage the student to evaluate critically the work of others and relate it to their own work where appropriate.
Develop a student's ability to create, plan, organise and work independently on an appropriate product, drawing on and extending ideas, skills and techniques encountered during the programme of study.
Develop the student's ability to appraise critically, by means of a written report, the product and the process of its production as well as lessons learnt during the course of the project.
Develop the student's ability to evaluate critically the work of others and relate it to their own work where appropriate.
Develop the student's ability to critically appraise their own academic, creative and technical practice, by means of a written report, the product outcome and the process of its production.

Learning outcomes

On completion of this course the student will be able to:
A. Produce a formal Project Proposal including a critical justification for the project and an appropriate set of objectives and estimates for the project.
B. Critically evaluate and use appropriate project management techniques to plan, organise, schedule and control their project.
C. Undertake a critically evaluative and appropriate literature search, using a variety of sources and methods for collecting reference material.
D. Carry a software development project through to a logical conclusion.
E. Document a project with evidence of appropriate research, development methodology, technical documentation and critical refection on their progress and response to changing circumstances.
F. Satisfy any professional requirements specific to the student's programme.

Indicative content

This course will guide students through the stages of an individual substantive project through personal supervision and tutorials. During these tutorials and personal supervisions, students will be directed to undertake a student led project, which originates from within the School, from a sponsor, or from their own interests. Students can also carry out a pre-determined, templated project or an industry work practice project which has been agreed with their supervisor. Acceptable projects lead to the design and implementation of a software product and a written report of the project and the development process.

Lectures cover; project proposals, research skills and methodologies, project planning, requirements analysis, appropriate testing and implementation. Other skills covered include presentation skills, record keeping, report writing, appropriate referencing, Computing and Information Systems Legal, Social, Ethical laws and professional practice.

Stages of Project

1. Students are assigned a supervisor who will provide advice and guidance. Students are expected to meet regularly with their supervisor throughout the year. The first semester will involve a taught component covering basic project development process and appropriate research methodologies.
2. Developement of an Initial report on the subject area. It could include (where appropriate):
a. A definition of the problem that the student is trying to solve.
b. A Literature review of how other practitioners/researchers have tried to solve the defined problem. This should involve research into theories and practices relevant to their field of study and could include an investigation of existing artefacts, their authors┬┐ influences and methodologies.
c. An investigation into relevant techniques/technologies and their potential application to a project artefact.
d. An investigation into target audiences and the implications for artefact content and design.
3. A project idea pitch proposing their potential solutions/products with consideration towards their target audience. The pitch must be presented clearly and effectively, taking account of different audiences. if the initial pitch is not approved, the student can attempt more than once before the proposal is accepted.
4. Following acceptance of the proposed project idea, students can develop and document their artefacts, reflect on the process in a weekly log that explains and evaluates work done.
5. A regular progress meeting with tutors to demonstrate work completed to date and an overview of work going forward.
6. A demonstration of the completed artefact(s) where the student should be prepared to defend their decisions, using an evidence-based approach.
7. Finished artefact(s) professionally presented/described within a final project report, written in an appropriate academic structure and style.

Teaching and learning activity

Learning Time (1 credit = 10 hours)
Scheduled contact hours:

Note: include in scheduled time: project supervision, demonstrations, practical classes and workshops, supervised time in studio or workshop, scheduled lab work , fieldwork, external visits, work-based learning where integrated into a structured academic programme.
Lectures 0;
seminars 0;
supervised practical sessions 0;
Tutorials 18;
formative assessment 0;
other scheduled time 12;
Guided independent study:

Note: include in guided independent study preparation for scheduled sessions, follow up work, wider reading or practice, revision.
Independent coursework 200;
Independent laboratory work 185;
other non-scheduled time 185;
Placements (including work placement and year abroad) 0;
Total hours (Should be equal to credit x 10) 600.

Assessment

Coursework - 100%
Project Report and Demonstration.
10000-12000 words.
Pass mark - 40%

The project will be equally assessed by two members of the academic staff, one of whom will normally be the supervisor.

The project will be assessed by each marker taking into account all of the relevant information available to make an informed judgement. This information will normally come from four key sources:
1. The project report
2. The demonstration and student's oral presentation to both markers
3. All supporting work (e.g. product) submitted for examination by the student
4. The student's diary of work carried out throughout the project life span as recorded in the student┬┐s log.

Marks will be recorded by both markers on the Project Assessment Forms used within the School of Computing and Mathematical Sciences.

All project marks are subject to consideration and review by the project moderation panel.