University of Technology Sydney

32571 Enterprise Software Testing

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 2021 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.

Description

This subject provides students with the practical knowledge and skills that are necessary to effectively measure and control the quality of software products. It covers software quality assurance and management principles and practice together with systems and software testing approaches.

Subject learning objectives (SLOs)

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

1. Plan and execute specific processes, types and phases of testing to assure quality in software products
2. Apply exploratory and smoke testing to evaluate system operations and functions
3. Apply quality assurance and management principles to Agile and Waterfall test processes
4. Work collaboratively and actively to plan, develop, apply and document test systems
5. Understand the principles and major approaches to testing and quality management including the way testing processes support developers, projects and business outcomes
6. Understand how to communicate in a professional manner in all aspects of testing

Course intended learning outcomes (CILOs)

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

  • Socially Responsible: FEIT graduates identify, engage, interpret and analyse stakeholder needs and cultural perspectives, establish priorities and goals, and identify constraints, uncertainties and risks (social, ethical, cultural, legislative, environmental, economics etc.) to define the system requirements. (B.1)
  • Design Oriented: FEIT graduates apply problem solving, design and decision-making methodologies to develop components, systems and processes to meet specified requirements. (C.1)
  • Collaborative and Communicative: FEIT graduates work as an effective member or leader of diverse teams, communicating effectively and operating within cross-disciplinary and cross-cultural contexts in the workplace. (E.1)

Teaching and learning strategies

1.5 hour lecture and 1.5 hour tutorial per week

UTS has embraced the ‘flipped education’ model, rather than only attending lectures, students access digital resources and undertake preliminary tasks prior to coming to tutorial and lecture where they engage in collaborative, mentored activities.

Learning in this subject includes viewing videos and recommended reading (both available from the UTS Library); each lecture contains details of preparation work for the following tutorial. Tutorial participation marks depend on the completion of the FLIP learning work as well as participation in tutorial.

Content (topics)

The major topics are:

  1. Quality Assurance Principles
    Definition of quality for software products, quality characteristics and their relationships, setting measurable and testable quality attributes, the relationship between the QA Function, Software Developers and Management.
  2. Implementing Software Quality Assurance
    SQA Plans: characteristics and documentation, quality standards, configuration management, quality audit, quality assurance justification, effectiveness and cost of SQA
  3. Verification, Validation and Test
    VV&T methods and techniques, VV&T tools, relation of VV&T to all phases of the software development life cycle, the processes of VV&T appropriate to each of the life cycle phases
  4. Quality Management practice
    How Quality impacts the business and its customers. The required infrastructure including testing tools, environments. The people and skills needed for good quality and the interaction of the test team and their work on other IT groups.

Assessment

Assessment task 1: FMEA & Static testing

Objective(s):

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

1 and 6

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

C.1 and E.1

Type: Report
Groupwork: Individual
Weight: 20%

Assessment task 2: Exploratory Test

Objective(s):

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

1, 2, 3 and 6

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

B.1, C.1 and E.1

Type: Report
Groupwork: Individual
Weight: 20%

Assessment task 3: System Test

Objective(s):

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

1, 2, 3, 4 and 6

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

C.1 and E.1

Type: Report
Groupwork: Group, group and individually assessed
Weight: 30%

Assessment task 4: Tutorial Participation

Objective(s):

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

1, 4, 5 and 6

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

E.1

Type: Exercises
Groupwork: Individual
Weight: 10%

Assessment task 5: Multiple choice quiz

Objective(s):

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

4, 5 and 6

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

B.1 and C.1

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

Minimum requirements

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

Required texts

Black, R. 2009, Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing. Third Edition, Wiley Publishing Inc. ISBN: 978-0-470-40415-7

References

  1. Perry, W. E. 2006, Effective Methods for Software Testing, Third Edition, Wiley Publishing Inc.
  2. Laird, L. M and Brennan, M. C. 2006, Software Measurement and Estimation: A Practical Approach (Quantitative Software Engineering Series), First Edition, John Wiley Inc.
  3. Godbole, N. S. 2004, Software Quality Assurance: Principles And Practice, First Edition, Alpha Science International Ltd.
  4. Beydeda, S. and Gruhn, V. 2005, Testing Commercial-off-the-Shelf Components and Systems, Springer-Verlag.
  5. Chrissis, M., Konrad. M. and Shrum, S. 2003, CMMI Guidelines for Process Integration and Product Improvement, Addison Wesley.
  6. Potter, N. and Sakry, M. 2002, Making Process Improvement Work, Addison Wesley
  7. Wieger, K. E. 2002, Peer Reviews in Software, Addison Wesley.
  8. Ahern, D., Clouse, A. and Turner, R. 2001, CMMI Distilled: A Practical Introduction to Integrated Process Improvement, Second Edition, Addison Wesley.