CSU22013 – Software Engineering Project I

Module CodeCSU22013
Module NameSoftware Engineering Project I
ECTS Weighting[1]5 ECTS
Semester taughtSemester 2
Module Coordinator/s  Inmaculada Arnedillo-Sanchez and Stephen Barrett

Module Learning Outcomes

On successful completion of this module, students will be able to:


LO1. Analyse, specify, design, write and test a complete software solution to a complex problem;
LO2. Apply industry standard methodologies and tools to complex projects;
LO3. Formulate and schedule intermediate goals and activities in the context of a large group project.
LO4. Implement a software system of reasonable complexity;
LO5. Compare and apply concepts for software testing, software debugging and software version management;
LO6. Contribute to the design and analysis of software by means of UML diagrams;
LO7. Contribute to requirements document for a substantial software engineering project;
LO8. Recognise the challenges and opportunities posed by working in project groups and apply best-practice solutions to group management issues;
LO9. Produce a development report and presentations;
LO10. Write a reflective essay;

Module Content

This module introduces students to the discipline of software engineering and requires them to work in groups with more senior students taking the course CSU33013. The course provides students with their first formal experience 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.

Teaching and learning Methods

Lectures, practice-based.

Assessment Details

Assessment ComponentBrief DescriptionLearning Outcomes Addressed% of totalWeek setWeek Due
Project planLO1, LO2, LO3,
LO5, LO6, LO7
10n/an/a
Development
report
LO1, LO2, LO3,
LO4, LO5, LO6,
LO7
30n/an/a
Software SystemLO1, LO2, LO3,
LO4, LO5, LO8
30n/an/a
Individual
reflective
essay
LO7, LO820n/an/
Attendance &
participation
LO2, LO3,LO4, LO6, LO7, LO8, LO910n/an/a

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 she/he 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
completion of assessments (including examination, if applicable)50 hours
Group meetings, meetings with clients & demonstrators30 hours
Preparation for classes and review of material (including preparation for
examination, if applicable
6 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: list module codes.

Other/alternative non-module prerequisites: programming languages

Module Co-requisites

None

Module Website

Blackboard