Unit Outline

This unit provides students with the practical knowledge and skills that are necessary to ensure quality software products. It covers the four recognised levels of software testing: unit testing, integration testing, system testing and acceptance testing. The unit also covers quality management processes with a focus on quality assurance processes and planning, and quality control procedures and verification testing.

Intended Learning Outcomes

As per the Assessment and Results Policy 1.3, your results will reflect your achievement against specified learning outcomes.

On completion of this unit, you will be able to:


1.	Apply a specified testing approach to evaluate a software product
2.	Develop a quality assurance plan for a software development process to comply with best practice and industry standards
3.	Conduct quality control procedures to verify the quality of a final product

Requisites


REQUISITE TYPE	REQUISITES
Pre-requisite	KIT506 or KIT519

Alterations as a result of student feedback

A couple of industry experts will participate in a lecture.

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	Lecture (On Campus)	A real-time (i.e. synchronous) interactive activity involving the whole class whose primary purpose is the presentation and structuring of information/ideas/skills to facilitate student learning. All students are expected to attend.	2	Weekly
	Tutorial	A structured real-time (i.e. synchronous) activity in a small-group setting where the primary purpose is the clarification, exploration or reinforcement of subject content presented or accessed at another time or place (e.g. lecture, preparatory work). It is reliant on student-teacher and student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the tutorial are expected to attend.	2	2 times per week
	Independent Learning	Involving reading, listening to audio, watching video, and/or completing exercises and/or quizzes, self-study is individual work undertaken when the student chooses (i.e. asynchronous), most likely through engagement with MyLO. The content is examinable, and may need to be completed prior to attending classes and/or attempting assessment tasks.	1	Weekly

Attendance / engagement expectations

If your unit is offered On campus, it is expected that you will attend all on-campus and onsite learning activities. This is to support your own learning and the development of a learning community within the unit. If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.

If your unit is offered Online, it is expected you will engage in all those activities as indicated in the Unit Outline, including any self-directed learning.

If you miss a learning activity for a legitimate reason (e.g., illness, carer responsibilities) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.

How will I be Assessed?

For more detailed assessment information please see MyLO.

Assessment schedule


ASSESSMENT TASK #	ASSESSMENT TASK NAME	DATE DUE	WEIGHT	LINKS TO INTENDED LEARNING OUTCOMES
Assessment Task 1:	Evaluation of a software product	Week 5	25 %	LO1
Assessment Task 2:	Quality Assurance Plan	Week 8	35 %	LO2
Assessment Task 3:	Case Study for Quality Control and Assurance	Week 13	40 %	LO2, LO3

Assessment details

Assessment Task 1: Evaluation of a software product

Task Description:

Students will use a specified testing approach to evaluate a given software product. This is to assess students' ability to apply formal testing approaches to software. Students can receive formative feedback during the tutorials on the development of their report.

Task Length:

2000 words

Due Date:

Week 5 (27/Mar/2024)

Weight:

25 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Apply specified testing approaches to evaluate software	LO1
2	Report findings of each applied software test using template	LO1

Assessment Task 2: Quality Assurance Plan

Task Description:

Students will work in a group to develop a quality assurance plan to satisfy the needs of a software development process. Students can receive formative feedback during the tutorials on the development of their report.

Task Length:

3000 words (group)

Due Date:

Week 8 (24/Apr/2024)

Weight:

35 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Develop a quality assurance plan for the organisation's needs.	LO2
2	Document the quality assurance plan using best practice and industry standard notations and templates	LO2

Assessment Task 3: Case Study for Quality Control and Assurance

Task Description:

Students will work in a group to analyse a case study and develop appropriate quality control and quality assurance procedures before applying them to the case study. Students can receive formative feedback during the tutorials on the development of their report.

Task Length:

4000 words (group)

Due Date:

Week 13 (29/May/2024)

Weight:

40 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Develop and document a quality assurance plan for the organisation's needs.	LO2
2	Develop quality control procedures that will work to verify the quality of final product.	LO3
3	Conduct and document a quality assessment of the case study based upon identified procedures and plans.	LO3

How your final result is determined

To pass this unit, you need to demonstrate your attainment of each of the Intended Learning Outcomes, achieve a final unit grade of 50% or greater, and pass any hurdle tasks.

Submission of assignments

Where practicable, assignments should be submitted to an assignment submission folder in MYLO. You must submit assignments by the due date or receive a penalty (unless an extension of time has been approved by the Unit Coordinator). Students submitting any assignment in hard copy, or because of a practicum finalisation, must attach a student cover sheet and signed declaration for the submission to be accepted for marking.

Requests for extensions

If you are unable to submit an assessment task by the due date, you should apply for an extension.

A request for an extension should first be discussed with your Unit Coordinator or teaching support team where possible. A request for an extension must be submitted by the assessment due date, except where you can provide evidence it was not possible to do so. Typically, an application for an extension will be supported by documentary evidence: however, where it is not possible for you to provide evidence please contact your Unit Coordinator.

The Unit Coordinator must notify you of the outcome of an extension request within 3 working days of receiving the request.

Late penalties

Assignments submitted after the deadline will receive a late penalty of 5% of the original available mark for each calendar day (or part day) that the assignment is late. Late submissions will not be accepted more than 10 calendar days after the due date, or after assignments have been returned to other students on a scheduled date, whichever occurs first. Further information on Late Penalties can be found on the Assessments and Results Procedure.

Review of results and appeals

You are entitled to ask for a review of the marking and grading of your assessment task if there is an irregularity in the marking standards or an error in the process for determining the outcome of an assessment. Details on how to request a review of a mark for an assignment are outlined in the Review and Appeal of Academic Decisions Procedure.