Undergraduate Programme and Module Handbook 2005-2006 (archived)
Module COMP2092: SOFTWARE ENGINEERING (40 CREDITS)
Department: COMPUTER SCIENCE
COMP2092: SOFTWARE ENGINEERING (40 CREDITS)
| Type | Open | Level | 2 | Credits | 40 | Availability | Available in 2005/06 | Module Cap | None. | Location | Durham |
|---|
Prerequisites
- Programming and Data Structures (COMP1082) OR Introduction to Programming (COMP1011).
Corequisites
- None.
Excluded Combination of Modules
- None.
Aims
- Have gained a detailed understanding of the phases of the software development lifecycle and know the best practice and problems that are associated with each of the individual phases.
Content
- Project management.
- Human computer interaction.
- Software requirements analysis.
- Software design.
- Software testing and software quality assurance.
- Advanced software lifecycles.
- Business and professional issues.
Learning Outcomes
Subject-specific Knowledge:
- Have gained a first hand experience of software development that is realistic and applicable to software development in industry.
- Have an appreciation of the problems facing the software development industry in terms of the software development process and general project management.
- Able to describe and analyse how each of the issues within software engineering interrelate.
- Have gained additional knowledge of the problems faced in 'real world computing' through representatives from industrial software development companies.
Subject-specific Skills:
- Have gained experience in planning, organising, managing and implementing a large scale software application.
Key Skills:
- Written and oral presentation.
- The ability to work with others.
- Problem solving.
Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module
- Lecturing demonstrates what is required to be learned and the application of the theory to practical examples.
- Problem classes through practicals provide assessment (both formative and summative) to guide students in the correct development of their knowledge and skills.
- Tutorials provide active engagement and feedback to the learning process.
- The end of year examinations assess the knowledge acquired and the ability to use this knowledge to solve problems.
Teaching Methods and Learning Hours
| Activity | Number | Frequency | Duration | Total/Hours | |
|---|---|---|---|---|---|
| Lectures | 38 | 2 per week | 1 Hour | 38 | |
| Tutorials | 2 | 1 Hour | 2 | ||
| Seminars | 9 | 1 hour | 9 | ||
| Practicals | 38 | 2 per week | 2 hours | 76 | |
| Preparation and Reading | 275 | ||||
| Total | 400 |
Summative Assessment
| Component: Coursework | Component Weighting: 60% | ||
|---|---|---|---|
| Element | Length / duration | Element Weighting | Resit Opportunity |
| group work | 50% | ||
| individual report | 50% | ||
| Component: Examination | Component Weighting: 40% | ||
| Element | Length / duration | Element Weighting | Resit Opportunity |
| two-hour examination | 100% | ||
Formative Assessment:
Example exercises given through the course.
■ 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