Skip to main content

Module

CSC8019 : Software Engineering and Team Project

  • Offered for Year: 2024/25
  • Module Leader(s): Dr Dan Nesbitt
  • Lecturer: Dr John Colquhoun
  • 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: 20
ECTS Credits: 10.0
European Credit Transfer System

Aims

To equip students with the knowledge and experience to function as successful practitioner software engineers.

This module aims to equip students with the knowledge and experience to function as successful practitioner software engineers. A team project runs as part of this module to give students experience in team working and management of a software project.

Outline Of Syllabus

Software Development Activities & Process Models:
1. Development activities: synthesis and V&V; analysis, design, implementation, test.
2. Development process models as ways of organising activities: agile, waterfall, V, evolutionary. Choosing a development model.

Software Engineering Tools & Techniques: a model-based approach:
1. The idea of modelling: data, functionality, data flow, control, consistency of models.
2. Basic Modelling Skills in UML: conceptual and specification level models using use cases, class diagrams and activity charts.
3. Issues in Requirements Modelling.
4. The Design Process.
5. Implementation.
6. The idea of correctness; V&V
7. Deployment and Maintenance.

Managing the Development Process:
1. Cost Estimation.
2. Planning Tools.
3. Product Metrics.
4. Process Improvement.

Teaching Methods

Teaching Activities
Category Activity Number Length Student Hours Comment
Scheduled Learning And Teaching ActivitiesLecture161:0016:00Lectures (PIP or online)
Guided Independent StudyAssessment preparation and completion301:0030:00Lecture follow-up
Scheduled Learning And Teaching ActivitiesPractical152:0030:00Practical
Scheduled Learning And Teaching ActivitiesSmall group teaching251:0025:00Tutorial and Group meetings (PIP and Online)
Guided Independent StudyProject work221:0022:00Practical/lab reports coursework- contributions to project specs
Guided Independent StudyProject work221:0022:00Report 1 (case study based) coursework
Guided Independent StudyStudent-led group activity301:0030:00Informal/formal group meetings (in person or online)
Guided Independent StudyIndependent study200:3010:00Assessment preparation and completion
Guided Independent StudyIndependent study151:0015:00Background reading
Total200:00
Teaching Rationale And Relationship

Lectures will be used to introduce the learning material and for demonstrating the key concepts by example. Students are expected to follow-up lectures within a few days by re-reading and annotating lecture notes to aid deep learning.

Project meetings both formal and informal, will provide team members and the team monitor with the opportunity to follow progress and address team issues.

Students aiming for distinction marks are expected to widen their knowledge beyond the content of lecture notes through background reading.

Assessment Methods

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

Other Assessment
Description Semester When Set Percentage Comment
Practical/lab report2M40Individual work (2000 words)
Practical/lab report2M60Group work (3500 words)
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
Report2MIndividual report on software engineering principles (3500 words)
Assessment Rationale And Relationship

The individual work gives students an opportunity to research and propose suitable software processes, and supports the development of the first group deliverable in the team project.

The Individual Report is used to assess what the individual has learnt about the group project, and whether he/she is able to function independently as a software engineering professional.

The Group Report is used to demonstrate what has been achieved in the Group Project, and the contribution that each group member has made.

Reading Lists

Timetable