Durham University
Programme and Module Handbook

Postgraduate Programme and Module Handbook 2018-2019 (archived)


Department: Computer Science


Type Open Level 4 Credits 15 Availability Available in 2018/19 Module Cap
Tied to


  • None.


  • None.

Excluded Combination of Modules

  • None.


  • To apply the phases of the internet-based software development lifecycle and to understand and appreciate the problems that are associated with each of the individual phases and the best practice for their solution.
  • To encourage students to critically evaluate the applicability of existing and emerging technologies and software tools to be used in development.


  • Development methodologies: Agile; Iterative and incremental development; Plan-driven
  • Test-driven development: Requirements specification; Use cases/stories; approaches to software testing
  • Configuration management: management of system information and systematic handling of system changes; CM tools

Learning Outcomes

Subject-specific Knowledge:
  • A knowledge of software development that is relevant and applicable to internet-based software development in industry.
  • An appreciation of the problems facing the software development industry in terms of the software development process.
Subject-specific Skills:
  • An ability to plan, organise, manage and create a large scale software application as part of a team.
  • An ability to use and critically evaluate software tools and systems with regard to the principles of software engineering so that this use and analysis aids the production of software applications.
  • An ability to conduct self-study to further their knowledge in the integration of the topic areas and to undertake a critical evaluation of software methodologies.
Key Skills:
  • 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.
  • An ability to critically evaluate their own work and that of others.
  • Recognise and apply the principles of software engineering.
  • Communicate technical information.

Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module

  • Tutorials provide the core material for management and development of a software application as part of a team project.
  • Ongoing learning over the module duration will be via problem based learning with regular group tutorials, led by an assigned staff mentor, to provide guidance on core material and additional support.

Teaching Methods and Learning Hours

Activity Number Frequency Duration Total/Hours
Tutorials 20 Term 2 1 Hour 20
Preparation and Reading 130
Total 150

Summative Assessment

Component: Coursework Component Weighting: 100%
Element Length / duration Element Weighting Resit Opportunity
Team work 60% Yes
Relective Report maximum 2500 words 40% Yes

Formative Assessment:

Feedback from a tutor at group tutorials

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