CSU33D06 – Software Design Analysis

Module CodeCSU33D06
Module Name Software Design and Implementation.
ECTS Weighting [1]5 ECTS
Semester TaughtSemester 2
Module Coordinator/s  Stephen Barrett

Module Learning Outcomes

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

  1. Undertake software design and construction as members of teams of various sizes using modern methodologies;
  2. Define a problem specification and devise a solution;
  3. Implement a software system of reasonable complexity;
  4. Test the solution using standard techniques;
  5. Present the solution to stakeholders.

Module Content

This module aims to inculcate practical skills in team driven software engineering through small and large group programming projects. It places students in the team setting to offer practical learning opportunity in how to work effectively with others throughout project lifecycles. Students conceive of, develop and present creative work in a competitive setting. Key practical skills include the day-to-day use of: git source code management system; team communication tools; testing techniques for quality assurance; agile development methodology.

Teaching and Learning Methods

The module is delivered with the support of a short series of lectures, with primary focus on lab and mentor-to-team engagement.

Students are assessed individually by the teaching team in terms of their contribution to the ongoing team work, their software development, their contribution to problem solving and administrative effort.

Assessment Details

Assessment ComponentBrief Description Learning Outcomes Addressed% of TotalWeek SetWeek Due
Students are assessed based on their practical development contribution to their team’s work.All40%112
Individual ReportAn individual report detailing the students contribution and the team activity.All20%112
Team ApplicationThe team application delivery. All40%112

Reassessment Details

An individual practical development task will be set, to be completed by the end of the normal reassessment period. There is no reassessment by written examination.

Contact Hours and Indicative Student Workload

Contact Hours (scheduled hours per student over full module), broken down by: 44 hours
Lecture11 hours
Laboratory 0 hours
Tutorial or seminar 0 hours
Other 33 hours
Independent study (outside scheduled contact hours), broken down by:72  hours
Preparation for classes and review of material (including preparation for examination, if applicable) 6 hours
Completion of assessments (including examination, if applicable) 66 hours
Total Hours 116 hours

Recommended Reading List

Relevant material will be introduced from the Internet. References will be provided
as the module proceeds.

Module Pre-requisites

Prerequisite modules: N/A

Other/alternative non-module prerequisites: Students should have programming experience in one or more modern languages and should have completed a personal or class programming project of reasonable scale (eg. Module programming assignment).

Module Co-requisites


Module Website