University of Technology Sydney

32603 Systems Quality Management

Warning: The information on this page is indicative. The subject outline for a particular session, location and mode of offering is the authoritative source of all information about the subject for that offering. Required texts, recommended texts and references in particular are likely to change. Students will be provided with a subject outline once they enrol in the subject.

Subject handbook information prior to 2024 is available in the Archives.

UTS: Information Technology: Computer Science
Credit points: 6 cp

Subject level:

Postgraduate

Result type: Grade and marks

There are course requisites for this subject. See access conditions.
Anti-requisite(s): 49264 Software Quality Processes

Description

As products and the methods of producing them become more complex, organisations need methods of ensuring that their products are as intended. This subject teaches how to plan, implement and improve quality management processes, and how such systems are common to almost every organisation. Software and systems products are often complex and increasingly part of life critical systems, with matching demands on their development methods and quality management. This subject reviews how quality management systems are an integral part of organisation management, how quality management systems are spread through the different layers of organisations, and how such systems operate. Real-world examples are used throughout the subject to examine aspects of quality management systems, culminating in an industry-based project to devise an improvement to solve a quality management system problem.

Subject learning objectives (SLOs)

Upon successful completion of this subject students should be able to:

1. Analyse the value and costs of quality in a specific context. (D.1)
2. Using a quality model describe those qualities that are important in a specific context. (D.1)
3. Describe how quality management, control and improvement can be implemented in a specific context. (D.1)
4. Determine and describe the practical considerations for quality management in a specific context. (D.1)
5. Apply some of the current research issues in software quality. (D.1)

Course intended learning outcomes (CILOs)

This subject also contributes specifically to the development of the following Course Intended Learning Outcomes (CILOs):

  • Technically Proficient: FEIT graduates apply theoretical, conceptual, software and physical tools and advanced discipline knowledge to research, evaluate and predict future performance of systems characterised by complexity. (D.1)

Teaching and learning strategies

Lectures are available online. The lectures provide foundation knowledge of quality management that can, and probably will, be applied when investigating and solving a commercial quality management problem.

During the tutorials problem will be presented for students to suggest ways to respond to the different stages of problem investigation. The student responses will be summarised to inform discussion about the investigation.

The main learning activity of this subject is for group (4-5 students) of students to investigate and develop responses to a problem provided. Each week student teams will develop another phase of their investigation and suggested solution to the problem.

Content (topics)

Quality management systems:

  • Quality, quality management and quality management systems.
  • Process based systems. System based models of product or service production. Quality management processes for strategic management, tactical management and operations. ISO 9001 and other standards.
  • How different parts of the organisation affect quality management and how quality emerges from the collective effects of those different parts.

The history of quality management:

  • How quality management accompanied and was an essential part of factory production. The wide reaching effects of production methods and their consequences for quality management.

Quality management strategies:

  • High reliability systems: Specific requirements for achieving high reliability in products and services. Risk driven quality assurance: Risks and their treatment in developing products and services.
  • Quality management in human based systems: Crew Resource management as a quality management method
  • Economics of quality management systems: How much does the customer value quality. Quality management in an agile world. How quality management systems will differ for plan based development vs agile development. Good enough quality. Quality at any price.

Quality and process improvement:

  • Reporting in quality management and quality assurance: Audits and assessments, Defect reports. Assessing quality management, and improvement opportunities. Methods for improvement: TQM, Reflective practitioner, Capability and maturity based improvement, Lean production, Six Sigma. Planning and implementing improvements.

Assessment

Assessment task 1: Class test

Intent:

A set of questions to assess how well the student understands and applies the main concepts.

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

1

This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs):

D.1

Type: Quiz/test
Groupwork: Individual
Weight: 25%

Assessment task 2: Individual project

Intent:

Demonstrate that the student understands the objectives, scope, constraints and risks of the proposed project and to align industry, academic and student expectations for the project.

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

1, 2 and 3

This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs):

D.1

Type: Project
Groupwork: Individual
Weight: 45%
Length:

Approximately 2000 to 3000 words

Criteria:

Relevant: The proposal addresses the project objectives, constraints and risks.

Complete: The proposal reasonably identifies all of the relevant objectives, constraints and risks.

Informed: The identified objectives, constraints and risks inform the project strategy and plan.

Justified: The proposed strategy and plan is shown to be the best alternative in the project circumstances.

Assessment task 3: Group project

Intent:

Students will carry out a project to investigate and document a principle of software quality management. The principle should guide industry decision making about achieving software quality objectives in a given context.

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

3, 4 and 5

This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs):

D.1

Type: Project
Groupwork: Group, group assessed
Weight: 30%
Length:

Approximately 1500 to 2000 words

Criteria:

Description: Clear description of the principle for software quality management.

Benefits: Benefits arising from the principle for the organization.

Applicability: Applicability of the principle with clear and succinct rationale.

Evidence: Evidence supporting the principle in achieving quality management.

Minimum requirements

In order to pass the subject, a student must achieve an overall mark of 50% or more.

References

  • UTS Business School's Writing Guide
  • Writing Your Dissertation One Paragraph at a Time, Barry Jay, on UTSOnline

References for software quality management (no prescribed text):

Useful websites:

  1. http://www.apqc.org/pcf (APQC Process Framework)
  2. http://www.sei.cmu.edu (Software Engineering Institute)
  3. http://www.rspa.com/spi/SQA.html (Roger Pressman & Associates)
  4. http://www.rspa.com/reflib/QualityMgmt.html

Books on software quality management:

  1. Horch, J. W. (2003): Practical Guide to Software Quality Management, 3rd edition, Artech Publishing.
  2. Meyerhoff, D. et al (eds) (2002): Software Quality and Testing in Internet Times, Springer-Verlag.
  3. Nance, R. and Arthur, J. (2002): Managing Software Quality, Springer-Verlag.
  4. O'Regan, G. (2002): A Practical Approach to Software Quality, Springer-Verlag.
  5. Sanders, J. and Curran, E. (1994): Software Quality: A Framework for Success in Software Development and Support, Addison-Wesley.

Software reviews:

  1. Wieger, K. (2002): Peer Reviews in Software: A Practical Guide, Addison-Wesley.
  2. Gilb, T. and Graham, D. (1993): Software Inspection, Addison-Wesley.
  3. IEEE Std 1028 Software Reviews and Audits

The classics:

  1. Deming, W. E. (1986): Out of the Crisis, MIT Press.
  2. Juran, J. M. (1992): Juran on Quality by Design, Free Press.
  3. Crosby, P. (1979): Quality is Free, McGraw-Hill.
  4. Crosby, P. (1995): Quality is Still Free, McGraw-Hill.