Skip to main content

Trinity College Dublin, The University of Dublin

Menu Search

Module Descriptor School of Computer Science and Statistics

Module CodeCS3013
Module NameSoftware Engineering Group Project
Module Short Title
Semester Taught
Contact Hours

Lecture hours: 22

Module PersonnelInmaculada Arnedillo-Sánchez and Stephen Barrett
Learning Outcomes

Upon successful completion of the module students will be able to:

  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;
Learning Aims

This course follows on directly from CS3012 (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 CS2013.

The overall aim of this course is for students to further develop their skills for building large, important object-oriented software systems. This entails (i) the application of the general software lifecycle and its stages from domain analysis to maintenance, (ii) to differentiate and apply appropriate models for analysing, designing and testing object-oriented software, (iii) to differentiate and apply appropriate approaches for managing software projects and teams, (iv) to distinguish and assume specific roles in a software project in general and in software teams in particular, (v) to have exposure to working as a member of a group.

Module Content
  • Problem statement and working model
  • Project management plan, work plan and testing plan
  • Theory and practice of project group organisation including group management, communication strategies and problem resolution
  • Requirements and specification
  • Object-oriented analysis and design
  • Progress report
  • Test report
  • Product demonstration
  • Project presentation and evaluation
  • Project team self-assessment
Recommended Reading List

Recommended Texts:

  • 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 Prerequisites
Assessment Details

This course will be assessed by practical only, with no final exam at the end of the year. Students will be assessed on their deliverables, project demonstration and project presentation. These assignments are a combination of presentations, group, and individual work. As part of the final assessment each student is required to produce a reflective essay on their experience in the project and their development of authentic practice. Students also report on the group management process and outcomes, including an assessment of their responsibilities to other group members and to their clients. The quality of the final system is assessed by the course lecturers and the group project supervisor.

Supplemental assessment is by individual project work

In addition to achieving a pass mark for the module, students are also required to attend 75% of the scheduled team meetings or, in exceptional circumstances, to provide the teaching assistant with a satisfactory written explanation for any absence. If a student does not satisfy this requirement he/she will be deemed to have failed the module.

Module Website
Academic Year of Data2018/19