Module Catalogue 2026/27

CSC2033 : Software Engineering Team Project

CSC2033 : Software Engineering Team Project

  • Offered for Year: 2026/27
  • Module Leader(s): Dr Marie Devlin
  • Lecturer: Dr John Colquhoun, Dr Gary Ushaw
  • Teaching Assistant: Mr Nicholas Smith, Mr Oshada Lokuhetty, Mr Muhammad Khalid
  • Other Staff: Mr Chris Napier
  • Owning School: Computing
  • Teaching Location: Newcastle City Campus
Semesters

Your programme is made up of credits, the total differs on programme to programme.

Semester 2 Credit Value: 30
ECTS Credits: 15.0
European Credit Transfer System
Pre-requisite

Modules you must have done previously to study this module

Code Title
CSC1034Programming Portfolio 1
CSC1035Programming Portfolio 2
Pre Requisite Comment

N/A

Co-Requisite

Modules you need to take at the same time

Co Requisite Comment

N/A

Aims

To provide hands-on experience in real-world software development, collaborative team working, and managing a software project.

To enhance graduate employability skills by training students in industry-standard tools, workflows and professional practices.

This module simulates a professional software engineering environment, combining practical software development with dedicated career development activities. Students will gain first-hand experience navigating the end-to-end software delivery lifecycle within a team setting.

Key components:
Practical Software Engineering - students explore the foundational skills required of a modern software engineer beyond core programming, including agile project management, version control, and collaborative development.

The module begins with a series of lectures on software processes, lifecycles, and architectural design, alongside practical toolchain tutorials. These hands-on workshops cover industry-standard tools for collaborative planning, automated testing, continuous integration, and software deployment.

Working in assigned teams, students will select a software project based on one of multiple briefs. Where possible, guest lectures from industry practitioners will provide real-world insights. Regular lab check-ins allow teams to demonstrate progress and articulate their contributions. Assessment is based on code delivery, technical documentation, a trade-show demonstration, and peer evaluations.

Team Structure
Students are organised into teams of 5 to 8 members, assigned by the module leader to ensure a balance of diverse backgrounds, skills, and perspectives. Teams are expected to self-manage, leverage individual strengths, and assign roles and responsibilities effectively to deliver their project.

Outline Of Syllabus

Professional skills:
• The software engineering skillset.,
• Employability techniques e.g. interviews/CVs.

Processes and Project Management:
• Life-cycle and process models.
• Team organisation, roles and responsibilities.
• Configuration management principles.

Software Engineering Techniques and Tools:
• Requirements Engineering, UML design, Principles of verification.
• Tools for collaborative planning, building, verification and release of software systems.

Learning Outcomes

Intended Knowledge Outcomes

To be able to:

• Select an appropriate toolset for a particular application.
• Categorise the typical roles and skills of a software engineer.
• Reflect on the issues that relate to planning and execution of a team-based software project.
• Critically evaluate common software engineering processes and process models.

Intended Skill Outcomes

To be able to:

• Design and implement a large software system.
• Work as a member of a team.
• Demonstrate practical experience in issues such as team structure, document preparation, project management.
• Fulfil appropriate roles within a team and to apply particular skills to the job in hand.
• Evaluate own learning, progress and quality of solution objectively.
• Demonstrate technical writing & report writing.
• Practice critical self-evaluation, reflection & peer evaluation.
• Demonstrate effective presentation of results.

Teaching Methods

Teaching Activities
Category Activity Number Length Student Hours Comment
Guided Independent StudyAssessment preparation and completion501:0050:00Team preparation of design documentation including development logs.
Guided Independent StudyAssessment preparation and completion1121:00112:00Team programming, software engineering tooling, submission for final code.
Scheduled Learning And Teaching ActivitiesLecture221:0022:00Lectures (in person) on software processes, techniques, project management.
Guided Independent StudyAssessment preparation and completion161:0016:00Team preparation for trade fair/technical demonstration.
Scheduled Learning And Teaching ActivitiesPractical112:0022:00Tutorials (in person) and Team programming – in labs.
Scheduled Learning And Teaching ActivitiesSmall group teaching16:006:00Demo day in the style of a Trade Fair.
Scheduled Learning And Teaching ActivitiesDrop-in/surgery221:0022:00Twice weekly – teams to meet in person to discuss progress and ask module staff questions .
Guided Independent StudyIndependent study501:0050:00Background reading.
Total300:00
Teaching Rationale And Relationship

This is a practical course with students learning and developing skills within a team environment. Lectures are used to introduce and explore the main topics. The tutorials provide background in the range of software development tools. Students are expected to work together and individually to develop a large piece of software and provide appropriate documentation. Regular meetings are held with staff to check progress of the teamwork.

Reading Lists

Assessment Methods

The format of resits will be determined by the Board of Examiners

Other Assessment
Description Semester When Set Percentage Comment
Report2M35Formal design document and development log (team)
Design/Creative proj2M55Coding & Documentation: Final system’s code and related documentation for testing/using and future developers (team).
Prof skill assessmnt2M10Technical demonstration (team).
Formative Assessments

Formative Assessment is an assessment which develops your skills in being assessed, allows for you to receive feedback, and prepares you for being assessed. However, it does not count to your final mark.

Description Semester When Set Comment
Practical/lab report2Mpractical work is formative and students get face to face feedback during the session
Assessment Rationale And Relationship

Assessment is via team deliverables which require students to work together to produce software and its documentation and to demonstrate that they are able to work collectively to produce an end product. To simulate a real world environment, students will present their final system at a trade fair/workshop and receive feedback in discussion with employers. Peer assessment is used to identify each individual's contribution to the team. Details of the deliverables may vary from year to year depending on the involvement of an industrial consultant. Full details will be available at the beginning of the module through the University VLE.

Timetable

Past Exam Papers

General Notes

N/A

Welcome to Newcastle University Module Catalogue

This is where you will be able to find all key information about modules on your programme of study. It will help you make an informed decision on the options available to you within your programme.

You may have some queries about the modules available to you. Your school office will be able to signpost you to someone who will support you with any queries.

Disclaimer

The information contained within the Module Catalogue relates to the 2026 academic year.

In accordance with University Terms and Conditions, the University makes all reasonable efforts to deliver the modules as described.

Modules may be amended on an annual basis to take account of changing staff expertise, developments in the discipline, the requirements of external bodies and partners, staffing changes, and student feedback. Module information for the 2027/28 entry will be published here in early-April 2027. Queries about information in the Module Catalogue should in the first instance be addressed to your School Office.