METRICS, QUALITY AND RELIABILITY

CSE3MQR

2015

Credit points: 15

Subject outline

This subject examines the different attributes of the quality of a piece of software, the techniques of measuring them and the means of developing quality software. The topics covered include measurement techniques, empirical relations, representation conditions, measurement types and scales, direct and indirect measurements, measurement prediction, meaningfulness in measurement, software quality attributes, software metrics, different types of metrics, software complexity, size estimation, software productivity, GQM, management by metrics, software reliability concepts, reliability model, reliability estimation, testing issues in the real world, test suite design, testing techniques, management issues in testing, software release policies, fault and failure, fault report, and fault and failure analysis.

SchoolSchool Engineering&Mathematical Sciences

Credit points15

Subject Co-ordinatorRichard Lai

Available to Study Abroad StudentsYes

Subject year levelYear Level 3 - UG

Exchange StudentsYes

Subject particulars

Subject rules

Prerequisites CSE2DES or CSE3SDM

Co-requisitesN/A

Incompatible subjects CSE41FSM or CSE3SMM or CSE5MQR

Equivalent subjectsN/A

Special conditionsN/A

Readings

Resource TypeTitleResource RequirementAuthor and YearPublisher
ReadingsSoftware Metrics: A Practical and Rigorous ApproachRecommendedNorman FentonA COPY IS AVAILABLE IN THE LIBRARY

Graduate capabilities & intended learning outcomes

01. Be able to compare the different measurement methods and explain how measurement is used for understanding, controlling and improving a project.

Activities:
Students are taught the concepts of software metrics, measurement methods and measurement data, and how measurement enables a project to be understood, controlled and improved. Case studies are employed to demonstrate how it is done.
Related graduate capabilities and elements:
Discipline-specific GCs (Discipline-specific GCs)
Critical Thinking (Critical Thinking)

02. Be able to construct the important test cases and a test suite for testing a software system more adequately and effectively

Activities:
Students are taught how poor quality software could affect many aspects of lives. For instance, a poor quality software affects the performance of an organisation and jeopardises human lives when it is used in a safety-critical system. Students are required to construct test cases that have a good coverage of the specification so that it is well tested before being shipped to a customer.
Related graduate capabilities and elements:
Critical Thinking (Critical Thinking)
Ethical Awareness (Ethical Awareness)

03. Be able to justify how some of the software metrics and framework (eg Halstead complexity metrics, McCabe Cyclometric metrics, Function Point and GQM) are used for measuring certain attributes of a software system.

Activities:
Students are taught the techniques of devising software metrics in relation to software goals and the goals of a company. The Halstead complexity metrics, McCabe Cycolmetric metrices, Function Point, Goal-Question-Metrics (GQM) framework are explained as to how they are used for measuring the certain attributes of a software system. Case studies are employed to demonstrate how they are put into practice.
Related graduate capabilities and elements:
Critical Thinking (Critical Thinking)
Creative Problem-solving (Creative Problem-solving)

04. Be able to explain the causes of software faults and relate them to software reliability and software reliability modelling

Activities:
Students are taught software reliability, software reliability modelling and how to analyse software faults. A case study on a past faulty safety critical system will be presented. Students are to discuss and to analyse faults during tutorial and laboratory classes.
Related graduate capabilities and elements:
Creative Problem-solving (Creative Problem-solving)
Critical Thinking (Critical Thinking)

Subject options

Select to view your study options…

Start date between: and    Key dates

Melbourne, 2015, Semester 2, Day

Overview

Online enrolmentYes

Maximum enrolment sizeN/A

Enrolment information

Subject Instance Co-ordinatorRichard Lai

Class requirements

Tutorial Week: 32 - 43
One 2.0 hours tutorial per week on weekdays during the day from week 32 to week 43 and delivered via face-to-face.

Lecture Week: 31 - 43
Two 1.0 hours lecture per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.

Assessments

Assessment elementComments% ILO*
Exam (2 hours)30 01, 02, 03, 04
Problem Solving Tasks2000 words22 01, 02, 03, 04
Reflective Learning Tasks1000 words12 01, 02, 03, 04
Laboratory submissions1200 words14 01, 02, 03, 04
Tutorial exercises1200 words14 01, 02, 03, 04
QuizzesTen quizzes each of 15 minutes8 01, 02, 03, 04