Undergraduate Programme and Module Handbook 2015-2016 (archived)
Module COMP2241: SOFTWARE DEVELOPMENT THEORY AND PRACTICE
Department: Computer Science
COMP2241: SOFTWARE DEVELOPMENT THEORY AND PRACTICE
| Type | Open | Level | 2 | Credits | 20 | Availability | Available in 2015/16 | Module Cap | Location | Durham |
|---|
Prerequisites
- COMP1021 Mathematics for Computer Science OR MATH1031 Discrete Mathematics
Corequisites
- None.
Excluded Combination of Modules
- COMP2181 THEORY OF COMPUTATION
Aims
- To introduce students to: important models of computation and how they are related.
- how software can be formally modelled, validated and verified
- formal management of the build, release and deployment of software and its related documentation
Content
- Models of computation
- Formal development processes
- Integration of verification, testing, build, release and deployment of software and its related documentation
Learning Outcomes
Subject-specific Knowledge:
- To have an understanding of different models of computation and their relevance to software development.
- To have an understanding of how the software development process can be managed formally.
Subject-specific Skills:
- On completion of the module, students will be able to demonstrate:
- an ability to use different models of computation in context of software development
- an ability to apply formal tools for the verification, build, release, deployment and documentation of software systems
Key Skills:
- On completion of the module, students will be able to:
- extract an abstract computational model from a real world problem
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. These will include 'Guru Lectures' on the formal management of the software development process.
- Problem classes through practicals provide assessment (both formative and summative) to guide students in the correct development of their knowledge and skills. These will include case studies from industry.
- 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 | 44 | 2 per week | 1 hour | 44 | |
| Practicals | 20 | 1 per week | 2 hours | 40 | ■ |
| Preparation and Reading | 116 | ||||
| Total | 200 |
Summative Assessment
| Component: Coursework | Component Weighting: 34% | ||
|---|---|---|---|
| Element | Length / duration | Element Weighting | Resit Opportunity |
| Practical work | 100% | Yes | |
| Component: Examination | Component Weighting: 66% | ||
| Element | Length / duration | Element Weighting | Resit Opportunity |
| Examination | 2 hours | 100% | Yes |
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