Print as pdf if you want a pdf! If you want a nicer printout, click off the browser's automatically added header and footer.

Blekinge Institute of Technology
Department of Software Engineering

Revision: 3
Reg.no:


Course syllabus

Software Metrics

Software Metrics

7.5 credits (7,5 högskolepoäng)

Course code: PA2559
Main field of study: Software Engineering
Disciplinary domain: Technology
Education level: Second-cycle
Specialization: A1N - Second cycle, has only first-cycle course/s as entry requirements

Language of instruction: English
Applies from: 2024-11-01
Approved: 2024-11-01

1. Descision

This course is established by Dean 2016-08-30. The course syllabus is approved by Head of Department of Software Engineering 2024-11-01 and applies from 2024-11-01.

2. Entry requirements

Completed courses of at least 120 ECTS credits including completed courses in Programming, Data structures and Algorithms, and Software Engineering or Team Software Engineering Project. In addition completed courses in Mathematics of at least 15 credits are required.

3. Objective and content

3.1 Objective

To understand, assess and control software and software development projects, one must be able to measure various aspects of software and its development. The measurement may concern for example the software’s quality, the efficiency of processes and tools, or the productivity of the staff. Measurements make it possible to detect and diagnose problems and to follow up whether various actions have had the desired effect.
The goal of the course is to provide students with the fundamentals of software measurement. Students will acquire knowledge of how measurements can be used to control, manage and predict software development processes. Students will also acquire a basic understanding of measurement processes and an awareness of the problems associated with software measurement, as well as experience in creating measurement models and carry out measurements.

3.2 Content

The course comprises the following modules:

  • Basics of measurement: the need for measuring, measurement frameworks. This includes measurement theory (scales, validation and meaningfulness), Goal-Question-Metric (GQM) paradigm, collection and analysis of data, classification of software metrics.
  • Metrics for Software: internal product attributes, external product attributes, resource measurements, quality models (ISO/IEC 9126 and 25010).
  • Processes for software measurement: process models (ISO/IEC 15939), introducing measuring program.

4. Learning outcomes

The following learning outcomes are examined in the course:

4.1. Knowledge and understanding

On completion of the course the student should be able to:

  • present and discuss the basics of measuring software,
  • present, argue and discuss in a professional manner, how metrics can be used in software development processes.

Skills and abilities

On completion of the course the student should be able to:

  • apply the GQM framework in a real context,
  • apply measurements in a professional manner in a real context.

Values and attitudes

On completion of the course the student should be able to:

  • Present, argue and discuss issues related to software measurement in a professional manner.

5. Learning activities

The teaching consists of lectures in which students are expected to take active part through discussion, questions and personal experiences. The course also comprises mandatory exercises with fixed deadlines.
The course commences with an introductory lecture and continues with a series of lectures where a number of subjects (see Contents) is introduced. Each lecture includes time for discussions and exercises.
The course comprises three mandatory examinations: an assignment, a project and a written exam. The assignment and the project require that students immerse themselves in an assigned topic related to metrics and measurement, and to apply the acquired knowledge in a given
context / project.

6. Assessment and grading

Modes of examinations of the course

Code Module Credit Grade
1705 Review assignment 2 credits AF
1715 Project Assignment 4 credits AF
1725 Written exam 1.5 credits AF

The course will be graded A Excellent, B Very good, C Good, D Satisfactory, E Sufficient, FX Failed result, a little more work required, F Fail.

The examiner may carry out oral follow-up of written examinations.

To get a passing grade for the course, all modules must be approved. The final grade of the course is the unweighted, rounded average of the grades of the modules.

The information before a course occasion states the assessment criteria and make explicit in which modes of examination that the learning outcomes are assessed.

An examiner can, after consulting the Disability Advisor at BTH, decide on a customized examination form for a student with a long-term disability to be provided with an examination equivalent to one given to a student who is not disabled.

7. Course evaluation

The course evaluation should be carried out in line with BTH:s course evaluation template and process.

8. Restrictions regarding degree

The course can form part of a degree but not together with another course the content of which completely or partly corresponds with the contents of this course.

9. Course literature and other materials of instruction

Course literature

Software Metrics - A Rigorous & Practical
Approach, 3rd edition
Authors: N. E. Fenton, J. Bieman
Publisher: CRC Press
Published: 2015
ISBN: 978-1-4398-3822-8
Reference literature

1. Software Measurement?: Establish, Extract, Evaluate, Execute
Authors: Christof Ebert, Reiner Dumke
Publisher: Springer
Published: 2007
ISBN: 978-3-540-71648-8

2. Software Metrics: A Guide to Planning, Analysis and Application
Authors: C. Ravindranath Pandian
Publisher: Auerbach Publications, CRC Press Company
Published: 2003
ISBN: 9780849316616

3. Metrics and Models in Software Quality
Engineering, 2nd edition
Author: Stephan H. Kan
Publisher: Addison-Wesley Publishing Company
Published: 2002
ISBN: 0201729156

10. Additional information

This course replaces PA1407