Undergraduate Programme and Module Handbook 2012-2013 (archived)
Module COMP2201: GROUP PROJECT
Department: Computer Science
COMP2201: GROUP PROJECT
| Type | Open | Level | 2 | Credits | 20 | Availability | Available in 2013/14 onwards | Module Cap | None. | Location | Durham |
|---|
Prerequisites
- Introduction to Programming
Corequisites
- Software Engineering
Excluded Combination of Modules
- None
Aims
- To develop a significant piece of software within a team environment.
Content
- Project management and planning.
- Configuration management.
- Risk analysis.
- Team structures and communications.
- Intellectual property rights.
- Data Protection Act.
- Professional bodies.
- Business and professional issues.
Learning Outcomes
Subject-specific Knowledge:
- On completion of the module, students will be able to demonstrate:
- a knowledge of the problems faced in 'real world computing'
- an understanding of the important legal, ethical and moral issues relating to the building and use of computer applications.
Subject-specific Skills:
- On completion of the module, students will be able to demonstrate an ability to plan, organise, manage and implement a large scale software application as part of a team.
Key Skills:
- On completion of the module, students will be able to demonstrate:
- an ability in technical writing, oral presentation and social interaction
- an ability to work with others as part of a team
- an ability to solve problems in a team environment.
Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module
- Lectures provide the core material and how core methods and techniques might be applied to practical scenarios.
- Workshops provide a facility for active engagement and feedback to the learning process.
- The Design Report examines the intial phases of the project including requirements, design and initial iterative development.
- The Final Report examines the reflective analysis of the group project in both the process and product produced.
- The Product Demonstration examines the software developed during the project and presentation skills.
- Industry seminars from representatives from industrial software development companies.
Teaching Methods and Learning Hours
| Activity | Number | Frequency | Duration | Total/Hours | |
|---|---|---|---|---|---|
| lectures | 10 | 1 per fortnight | 1 hour | 10 | |
| workshops | 10 | 1 per fortnight | 2 hours | 20 | |
| industry seminars | 10 | 1 per fortnight | 1 hour | 10 | |
| supervision | 3 | 1 per term | 1 hour | 3 | |
| preparation, reading and project work | 157 | ||||
| Total | 200 |
Summative Assessment
| Component: Coursework | Component Weighting: 100% | ||
|---|---|---|---|
| Element | Length / duration | Element Weighting | Resit Opportunity |
| Product Demonstration (group mark) | 30% | Yes | |
| Design Report (group mark) | 30% | Yes | |
| Final Report (individual mark) | 40% | Yes | |
Formative Assessment:
Formative feedback through lecturer-led group discussion will be given part way through the development of both reports and a prototype of the software system will be demonstrated. Industry workshops are sessions offered by external specialists (subject to availability).
■ Attendance at all activities marked with this symbol will be monitored. Students who fail to attend these activities, or to complete the summative or formative assessment specified above, will be subject to the procedures defined in the University's General Regulation V, and may be required to leave the University