Syllabus

Software Evolution Project

Mjukvaruevolutionsprojekt

Course
DIT265
Second cycle
15 credits (ECTS)
Disciplinary domain
NA Natural sciences 100%

About the Syllabus

Registration number
GU 2025/3968
Date of entry into force
2026-03-15
Decision date
2025-11-27
Valid from semester
Autumn term 2026
Decision maker
Department of Computer Science and Engineering

Grading scale

Four-grade scale, digits

Course modules

Project, 12 credits
Assignments, 3 credits

Position

The course is a compulsory course in Software Engineering and Management, Master's Programme (N2SOF).

The course can be part of the following programmes:

  1. Computer Science, Master's Programme (N2COS)

The course is a also a single-subject course at Gothenburg University.

Main field of study with advanced study

ITSOF Software Engineering - A1F Second cycle, has second-cycle course/s as entry requirements

Entry requirements

To be eligable for this course, the student needs to have successfully completed the following requirements, or equivalent:

  • A bachelor degree in Software Engineering, Computer Science, Information Technology, Information Systems, or equivalent
  • Advanced Requirements Engineering (7.5 credits)
  • Quality Assurance and Testing (7.5 credits)

Applicants must prove knowledge of English: English 6/English level 2 or the equivalent level of an internationally recognized test, for example TOEFL, IELTS.

Content

The course consists of two modules, including a group project and individual assignments.

Objectives

On successful completion of the course the student will be able to:

Knowledge and understanding

  • explain the notion of software evolution,
  • summarize state of the art in methods and tools for software evolution tasks, such as program comprehension and software refactoring,
  • discuss the challenges associated with software evolution,
  • explain current research trends in program comprehension, and refactoring

Competence and skills

  • extract a software product’s architecture from a given code base and evaluate the quality of the software product,
  • implement one software evolution scenario,
  • implement changes to a software product that lead to an improvement of the product’s quality,
  • make use of synergies between different improvements goals for the same product.

Judgement and approach

  • detect and judge needs for quality improvement or evolution in an authentic software product,
  • plan the use of appropriate methods and techniques for performing a software evolution scenario and a quality improvement task,
  • judge needs for improvement of methods and tools to support software evolution,
  • plan and evaluate ideas for new or improved tools.

Sustainability labelling

No sustainability labelling.

Form of teaching

The course contains project- and problembased teaching.

Language of instruction: English

Examination formats

The course consists of two modules:

  • A group project carried out in groups of students.
  • One or more individual assignments.

Furthermore, individual optional assignments can be used to collect bonus points during the course.


If a student who has been failed twice for the same examination element wishes to change examiner before the next examination session, such a request is to be granted unless there are specific reasons to the contrary (Chapter 6 Section 22 HF).

If a student has received a certificate of disability study support from the University of Gothenburg with a recommendation of adapted examination and/or adapted forms of assessment, an examiner may decide, if this is consistent with the course’s intended learning outcomes and provided that no unreasonable resources would be needed, to grant the student adapted examination and/or adapted forms of assessment.

If a course has been discontinued or undergone major changes, the student must be offered at least two examination sessions in addition to ordinary examination sessions. These sessions are to be spread over a period of at least one year but no more than two years after the course has been discontinued/changed. The same applies to placement and internship (VFU) except that this is restricted to only one further examination session.

If a student has been notified that they fulfil the requirements for being a student at Riksidrottsuniversitetet (RIU student), to combine elite sports activities with studies, the examiner is entitled to decide on adaptation of examinations if this is done in accordance with the Local rules regarding RIU students at the University of Gothenburg.

Grades

Sub-courses

  1. Project, 12 credits
    Grading scale: Pass with distinction (5), Pass with credit (4), Pass (3) and Fail (U)
  2. Assignments, 3 credits
    Grading scale: Pass with distinction (5), Pass with credit (4), Pass (3) and Fail (U)

The grading scale comprises: Pass with distinction (5), Pass with credit (4), Pass (3) and Fail (U).

To pass the course, all mandatory components must be passed. To earn a higher grade than Pass, a higher weighted average from the grades of the components is required.

Course evaluation

The course is evaluated through meetings both during and after the course between teachers and student representatives. Further, an anonymous questionnaire is used to ensure written information. The outcome of the evaluations serves to improve the course by indication which parts could be added, improved, changed or removed.

Other regulations

The course is a joint course together with Chalmers.

The course replaces the course DIT588 Software Evolution Project 15 credits. The course cannot be included in a degree which contains DIT588. Neither can the course be included in a degree which is based on another degree in which the course DIT588 is included.