CSU33013 – Software Engineering Project II

Module CodeCSU33013
Module Name Software Engineering Project II
ECTS Weighting [1]5 ECTS
Semester TaughtSemester 2
Module Coordinator/s  Inmaculada Arnedillo-Sánchez

Module Learning Outcomes

On successful completion of this module, students will be able to further develop their skills for building large, important object-oriented software systems:

  1. Differentiate, apply and exploit the key concepts of software lifecycle models;
  2. Compare and apply strategies for the gathering of software requirements and the generation of software specifications;
  3. Analyse and design software by means of UML diagrams;
  4. Compare and apply concepts for software testing, software debugging and software version management;
  5. Compare and apply techniques for managing software projects and teams;
  6. Recognise the challenges and opportunities posed by working in project groups and apply best-practice solutions to group management issues;
  7. Produce a requirements document for a substantial software engineering project;
  8. Make project plans and presentations;
  9. Write a reflective essay;
  10. Produce a management report.

Module Content

This course follows on directly from CSU33012 (Software Engineering) and focuses on the practical application of the various concepts and tools related to building software systems studied in third year software engineering. This practical application takes the form of a large “hands-on” group project that covers numerous aspects of building object-oriented software systems including problem analysis, usage of development environments, project management, team management, design, implementation, testing and documentation. Students will take a leadership role within these groups which are combined with students taking course CSU22013.

Teaching and Learning Methods

Lectures, practice-based learning.

Assessment Details

Practical Development Work Students are assessed exclusively by a series of practical development and written submissions.

Assessment ComponentBrief Description Learning Outcomes Addressed% of TotalWeek SetWeek Due
Project PlanLO1, LO2, LO3, LO4, LO5, LO6, LO7, LO835%
Management ReportLO10, LO615%
Software SystemLO1, LO2, LO3, LO4, LO5, LO7, LO820%
Individual Reflective EssayLO6, LO920%
Attendance and ParticipationLO2, LO3, LO4, LO5, LO6, LO7, LO8, LO1010%

In addition to achieving a pass mark for the module, students are also required to attend 75% of the scheduled team meetings (with the teaching staff, the demonstrators and the team itself). If a student does not satisfy this requirement he/she will be deemed to have failed the module.

Reassessment Details

A practical and/or written individual task will be set, with a deadline of the end of the reassessment period. There will be no written examination.

Contact Hours and Indicative Student Workload

Contact Hours (scheduled hours per student over full module), broken down by: 22 Hours
Lecture22 hours
Independent Study (outside scheduled contact hours), broken down by:86 hours
Preparation for classes and review of material (including preparation for examination, if applicable)6 hours
Group meetings, meetings with clients & demonstrators30 hours
Completion of assessments (including examination, if applicable)50 hours
Total Hours108 hours

Recommended Reading List

  • Agile Software Development with Scrum, Ken Schwaber & Mike Beedle.
  • The Mythical Man Month – Essays on Software Engineering, Frederick Brooks.
  • Object-Oriented Software Engineering – Practical Software Development using UML and Java, Timothy Lethbridge and Robert Laganiere.
  • UML Distilled, Martin Fowler.
  • Classical and Object-Oriented Software Engineering, David Schach.
  • The Art of Unix Programming, Eric Raymond.

Module Pre-requisites

Prerequisite modules: N/A

Other/alternative non-module prerequisites: Programming languages.

Module Co-requisites

N/A

Module Website

Blackboard