Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

ITO5171 Software testing, quality and standards

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

ITO5171 Software testing, quality and standards (19 Jun 2020, 3:02pm) [Sftw Test Qual Stand (19 Jun 2020, 3:45pm)]

Reasons for Introduction

Reasons for Introduction (19 Jun 2020, 3:45pm)

Created as part of the Master of Computer Science degree, and is one of six core requirements for the Software Engineering specialisation.

Reasons for Change (05 Feb 2021, 3:32pm)

05/02/2021: Updating assessment

Role, Relationship and Relevance of Unit (19 Jun 2020, 3:47pm)

Created as part of the Master of Computer Science degree, and is one of six core requirements for the Software Engineering specialisation.

This unit is intended to provide a deep coverage of various testing techniques and analysis of results such as test coverage according to various criteria. It also builds skills and experience in the student, w.r.t. building and maintaining quality code with automated testing tools.

Software Quality Engineering is covered as the need for the culture of quality is critical for SE students. They need to believe that they are real engineers and must develop a sense of engineering ethos and an understanding of the responsibilities of an engineer in producing and maintaining quality products through techniques such as regression testing, prioritization of test artefacts etc. V and V must adhere to industry standards and SE standards.

Objectives

Objectives (05 Feb 2021, 3:32pm)

On successful completion of this unit students should be able to:

  1. explain the importance of quality assurance in software engineering; articulate the role of validation and verification methods in the system development life cycle; key issues in software testing, testing levels and testing techniques;
  2. categorise and apply selection and combination of techniques and test related measures;
  3. measure, evaluate and analyse software under test using different quality and complexity metrics;
  4. develop adequate test cases to help detect software system defects using industry-strength IDEs, unit testing frameworks such as JUnit, code coverage tools such as Cobertura, and other similar products;
  5. Implement continuous integration (CI) at unit, integration & system testing level using a CI server such as Jenkins to automatically run regression test suites on the system under test.

Unit Content

ASCED Discipline Group Classification (19 Jun 2020, 3:50pm)

020199

Synopsis (19 Jun 2020, 3:51pm)

This unit covers the core software engineering disciplines concerned with managing and delivering quality software. Topics include processes, tools and techniques for system validation and verification, including major commercial tools used in industry. It shows how to detect, analyse and control defects in complex software systems. Inspection and testing methodologies, analysis of artefacts, robustness, quality assurance, and advanced software validation and verification methods are covered.

Teaching Methods

Mode (19 Jun 2020, 3:51pm)

Online

Assessment

Assessment Summary (05 Feb 2021, 3:33pm)

In-semester Assessment: 100%

Workloads

Resource Requirements

Teaching Responsibility (Callista Entry) (19 Jun 2020, 3:52pm)

FIT

Prerequisites

Prerequisite Units (19 Jun 2020, 3:53pm)

ITO5047, ITO5136, ITO5163

Corequisites (19 Jun 2020, 3:54pm)

Must be enrolled in the Master of Computer Science.

Prohibitions (19 Jun 2020, 3:53pm)

FIT5171

Proposed year of Introduction (for new units) (19 Jun 2020, 3:54pm)

MO-TP6, 2020

Location of Offering (19 Jun 2020, 3:54pm)

Monash Online

Faculty Information

Proposer

Emma Nash

Approvals

School:
Faculty Education Committee:
Faculty Board:
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

19 Jun 2020 Emma Nash modified UnitName; modified Abbreviation; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RoleRelationshipRelevance; modified ReasonsForIntroduction/RoleRelationshipRelevance; modified UnitObjectives/Objectives; modified UnitContent/ASCED; modified UnitContent/Synopsis; modified Teaching/Mode; modified Assessment/Summary; modified ResourceReqs/SchoolReqs; modified Prerequisites/PreReqUnits; modified Prohibitions; modified Corequisites; modified LocationOfOffering; modified DateOfIntroduction
10 Feb 2021 Jeanette Niehus

This version: