| Module Code | CSU22013 |
| Module Name | Software Engineering Project I |
| ECTS Weighting [1] | 5 ECTS |
| Semester Taught | Semester 2 |
| Module Coordinator/s | Prof. Inmaculada Arnedillo-Sánchez |
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;
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;
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 CSU3013. The course provides students with their first formal experience of a large “hands-on” group project that covers numerous aspects of building a 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 Component | Brief Description | Learning Outcomes Addressed | % of total | Week due |
| Project Planning & Design | Iterative plan and design of the Sweng project. | LO1, LO2, LO3, LO5, LO6, LO7 | 30% | 2, 4, 6, 8, 10 & 12 |
| Project Execution & Delivery | Iterative execution of the Sweng project. | LO1, LO2, LO3, LO4, LO5, LO6, LO7, LO8 | 55% | 2, 4, 6, 8, 10 & 12 |
| Presentation/Demonstration | Presentation and demonstration of the progress & final version of the Sweng project | LO8, LO9 | 10% | TBC |
| Attendance & Participation | Attendance to all the meetings and active participation in the Sweng project development. | LO8, LO9 | 5% | 1-12 |
In addition to achieving a pass mark for the module, students are also required to attend all the scheduled team meetings (with the company client, 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 |
| Lecture | 22 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 & demonstrators | 30 hours |
| Preparation for classes and review of material (including preparation for examination, if applicable | 6 hours |
| Total Hours | 108 hours |
Recommended Reading List
- Agile Software Development with Scrum, Ken Schwaber & Mike Beedle
- The Mythical Man Month – Essays on Software Engineering, Frederick Brooks
Module Pre-requisites
Prerequisite modules:
Other/alternative non-module prerequisites: Students should be comfortable in programming using one or more modern programming languages