Software Design and Development Project

Module overview

This module gives students experience of working in a team to design and develop a significant interactive software system. This practical activity is balanced with taught material to give students a theoretical understanding of the supporting disciplines.

Aims and Objectives

Learning Outcomes

Knowledge and Understanding

Having successfully completed this module, you will be able to demonstrate knowledge and understanding of:

The multidisciplinary nature of the design of software systems, and the range of contributory disciplines (software engineering, human factors, cognitive psychology, graphics design, ethics, etc.)
Agile methodologies for software project management
The main concepts that underpin the design of user interfaces
User-centred and participatory design processes

Transferable and Generic Skills

Having successfully completed this module you will be able to:

Solve complex problems in creative and innovative ways
Work effectively as part of a team, recognising the different roles within the team, and reflecting on both your own and the team's performance
Identify, evaluate and mitigate risks
Manage a project effectively
Reflect on your self-learning

Subject Specific Intellectual and Research Skills

Having successfully completed this module you will be able to:

Apply appropriate software engineering techniques and tools
Specify, design, develop, test and evaluate a prototype interactive software

Learning and Teaching

Teaching and learning methods

The content of this module is delivered through lectures, the module website, directed reading and pre-recorded materials. Students work on their understanding through a combination of independent study, preparation for timetabled activities and supervision meetings, along with formative assessments in the form of coursework assignments. Students work on their practical skills, professional skills and technical understanding in peer discussions, design meetings and supervision meetings.

Study time
Type	Hours
Completion of assessment task	151
Wider reading or practice	61
Follow-up work	18
Lecture	36
Project supervision	12
Revision	16
Preparation for scheduled sessions	6
Total study time	300

Resources & Reading list

Textbooks

Fitzpatrick and Collins-Sussman. Debugging Teams.

M. Fowler and K. Scott (1997). UML Distilled. Addison-Wesley.

Cockburn. Agile Software Development.

Sims and Johnson. Scrum: a Breathtakingly Brief and Agile Introduction.

I. Sommerville (2007). Software Engineering. Addison-Wesley.

Cohn. User Stories Applied.

T. Lethbridge and R. Laganiere (2005). Object-Oriented Software Engineering. McGraw Hill.

Assessment

Assessment strategy

This module is assessed by a combination of group and individual coursework.

Summative

This is how we’ll formally assess what you have learned in this module.

Breakdown
Method	Percentage contribution
Tutor and Peer Assessment	40%
Individual reflection	10%
Group project report	50%

Referral

This is how we’ll assess you if you don’t meet the criteria to pass this module.

Breakdown
Method	Percentage contribution
Coursework	100%

Repeat

An internal repeat is where you take all of your modules again, including any you passed. An external repeat is where you only re-take the modules you failed.

Breakdown
Method	Percentage contribution
Tutor and Peer Assessment	40%
Group project report	50%
Individual reflection	10%