|Module Name||Group Design Project|
|Module Short Title||N/a|
|Semester Taught||2nd Semester|
Lecture hours: 11
Lab hours: 0
Tutorial hours: 11
Total hours: 22
|Module Personnel||Dr Gerard Lacey, Dr Stefan Webber|
On successful completion of this module, students should be able to:
- Describe the complete process of working within a team in order to develop an interactive application, such as a computer game
- Implement an Agile development methodology
- Describe the challenges of working in an inter-disciplinary team, including developing good management and communication practices and how to schedule multiple concurrent tasks meeting interim delivery dates
- Use software tools for managing the project, including source code control, issue tracking systems, implementation and testing
- Deploy a complete end-to-end process for developing an application from concept, through design, development and implementation.
- Class meetings will be devoted primarily to discussion of readings and issues that arise as the project progress; we will have some in-class exercises as well. As such, class participation is important and will be a part of the grade.
The goal of this project is to promote teamwork and also to allow students to use their individual skills and experiences within the context of developing defined projects from specification to delivery. A key aim is to develop student’s abilities in framing design problems and working iteratively to achieve a working solution
Instruction will be provided in Agile development methodologies and facilities will be provided in order to promote close collaboration between team members.
A project supervisor will meet with each team weekly and will advise on setting up the team structure including the assignment of roles and responsibilities within the team and on reporting systems both internally and externally.
Weekly "peer" code and design reviews are a core component of the delivery of the module. These are to encourage a team approach to leaning and introduce the practicalities of software quality control.
Instruction will be provided in Agile development methodologies and facilities will be provided in order to promote close collaboration between team members. The development of the project will be structured as two “releases”, each of four weeks in duration.
Each week, the current state of progress is assessed and discussed, both in the lectures and in the group meetings.
Main topics covered:
- Principles of Agile Development
- Practise of Agile Development
- Ensuring correct “delivery” of software
- Comparisons of related development styles: SCRUM, Lean.
|Recommended Reading List|
Agile Software Development with Scrum, Ken Schwaber & Mike Beedle, Prentice Hall (October 21, 2001)
An ability to program, at a level typical for rising SS Computer Science students.
Assessment is based on the project development work done, broken down as follows:
10% Individual Class Contribution: based on involvement during the class contact hours: lectures and group meetings.
10% Individual Group Contribution: based on involvement in group activities outside class contact hours, assessed using peer evaluation.
80% Group Achievement: based of features delivered at each of the two release points, both worth half of the total marks.
Supplemental Assessment 100% Coursework
|Academic Year of Data||2018/19|