This is an archived handbook for a previous year. The current undergraduate and postgraduate handbooks can be viewed using the links above.
Undergraduate Handbook 2010-2011 (archived)
Module COMP3282: SOFTWARE ENGINEERING PROJECT
Department: Computer Science
COMP3282: SOFTWARE ENGINEERING PROJECT
| Type | Level | Credits | Availability | Module Cap | Location |
|---|---|---|---|---|---|
| Open | 3 | 40 | Available in 2010/2011 | None. | Durham |
Pre-requisites
- Software Engineering (COMP2092).
Corequisites
- Advanced Software Engineering (20 credits) (COMP3221). Or Advanced Software Engineering (40 credits) (COMP3152).
Excluded Combinations
- Computer Science Project (COMP3012), Artificial Intelligence Project (COMP3292).
Aims
- Conduct a substantial piece of academic, scientific software engineering work as an individual initiative and to write to and present it orally in a scholarly fashion.
Content
- a software engineering project taken from requirements to implementation and then carrying out an evaluation of the implementation produced.
Learning Outcomes
Subject-specific Knowledge
Subject-specific Skills
- By the end of the module students will be able to write and present a scientific report based upon detailed background research, demonstrating strong implementation and evaluation techniques through a substantial piece of work involving the appropriate use of Software Engineering approaches.
Key Skills
Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module
- Students are taught the expectations of the management of projects through the lecture series and personal subject based tuition is given within their tutorials.
- The research conducted and the implementation developed will be written up in the form of the scientific report.
- A bench test will evaluate the implementation based on the design produced and review the students' logs.
- In addition a project presentation will discuss the process conducted and preliminary results obtained.
Teaching Methods and Learning Hours
| Activity | Number | Frequency | Duration | Total Hours | Attendance Monitored |
|---|---|---|---|---|---|
| Workshops | 10 | 1 Hour | 10 | Yes | |
| Tutorials | 22 | 30mins | 11 | Yes | |
| Preparation and Reading | 379 | ||||
| Total | 400 |
Summative Assessment
| Component | Component Weighting | Element | Length/Duration | Element Weighting | Resit Opportunity |
|---|---|---|---|---|---|
| Coursework | 100% | coursework | 100% |
Formative Assessment
This is given to students using the project meeting review forms and the formal deliverable evaluation document used by all Software Engineering tutors.
Students who do not attend monitored activities shown under Teaching Methods
and Learning Hours, or who fail to complete the summative or formative
assessment(s) specified above, may be subject to the Academic Progress
procedures defined in the University's General Regulation V, and may be
required to leave the University.