This is an archived handbook for a previous year. The current undergraduate and postgraduate handbooks can be viewed using the links above.
Undergraduate Handbook 2012-2013 (archived)
Module COMP2191: SOFTWARE ENGINEERING
Department: Computer Science
COMP2191: SOFTWARE ENGINEERING
| Type | Level | Credits | Availability | Module Cap | Location |
|---|---|---|---|---|---|
| Open | 2 | 20 | Not available in 2012/2013 | None. | Durham |
Pre-requisites
- Introduction to Programming OR Computational Thinking
Corequisites
- None
Excluded Combinations
- None
Aims
- To gain a detailed understanding of the phases of the software development lifecycle.
- To understand and appreciate the problems that are associated with each of the individual phases and the best practice for their solution.
Content
- Software requirements analysis.
- Software design.
- Software testing.
- Human computer interaction.
- Software development.
- Software processes.
Learning Outcomes
Subject-specific Knowledge
- On completion of the module, students will be able to demonstrate:
- a knowledge of software development that is relevant and applicable to software development in industry
- an appreciation of the problems facing the software development industry in terms of the software development process and general project management.
Subject-specific Skills
- On completion of the module, students will be able to demonstrate:
- an ability to describe and analyse the different core facets of software engineering and how they interrelate
- an ability to critically analyse systems with regard to the principles of software engineering so that this analysis aids the production of software applications
- an ability to conduct self-study to further their knowledge in the integration of the topic areas.
Key Skills
- On completion of the module, students will be able to demonstrate:
- an ability to produce written documentation according to scientific writing principles
- an ability to apply methods and techniques to general problem solving.
Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module
- Lectures enable students to learn the principles and methodology as regards software engineering, and appreciate how these are applied.
- Practical classes enable students to correctly develop their knowledge and methodological skills in practical scenarios.
- Tutorials provide active engagement and an opportunity to explore a specific topic in a group environment.
- Examinations assess the knowledge acquired and coursework the ability to use this knowledge to solve problems.
Teaching Methods and Learning Hours
| Activity | Number | Frequency | Duration | Total Hours | Attendance Monitored |
|---|---|---|---|---|---|
| lectures | 44 | 2 per week | 1 hour | 44 | |
| workshops | 10 | 1 per fortnight | 2 hours | 20 | |
| tutorials | 2 | 1 hour | 2 | ||
| preparation and reading | 134 | ||||
| Total | 200 |
Summative Assessment
| Component | Component Weighting | Element | Length/Duration | Element Weighting | Resit Opportunity |
|---|---|---|---|---|---|
| Examination | 66% | Examination | 2 hours | 100% | Yes |
| Coursework | 34% | Coursework | 100% | Yes |
Formative Assessment
Formative feedback will be given during the coursework students undertake.
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.