Assessor Resource

ICAPRG515A
Review developed software

Assessment tool

Version 1.0
Issue Date: April 2024


This unit applies to senior programmers who are required to ensure the quality of software produced by others.

Quality assurance is a necessary part of any code development. Imposing quality on software development involves the review of quality standards, the determination of development quality issues, and a closer review of specific quality areas.

This unit describes the performance outcomes, skills and knowledge to apply quality standards associated with software development.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)

Prerequisites

Not applicable.

Employability Skills

This unit contains employability skills.



Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

determine quality standards and procedures that support the development of defect-free products to meet client requirements

apply appropriate quality standards to the development of products

conduct quality testing of developed software.

Context of and specific resources for assessment

Assessment must ensure access to:

data dictionaries

design specifications

data stream management system (DSMS)

simulated scenario

Australian and international software quality standards

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

evaluation of quality testing processes

review of documented processes to ensure quality

verbal or written questioning on quality standards.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

Required skills

communication skills to liaise with clients and development staff

literacy skills to interpret and write technical documents

planning and organisational skills to:

plan a project that addresses scope, time, cost, quality and risk

manage staff responsibilities

problem-solving skills to test processes during the development of defect-free software

technical skills to use data-modelling tools.

Required knowledge

client business domain

broad knowledge of industry accepted hardware and software products

input and output drivers

operating systems

programming languages: two or more procedural languages and three or more object-oriented languages

quality assurance practices and the identification of standards

real-time programming techniques

software application measuring and estimating methodology

software development and configuration-management processes

software-metrics development.

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Quality standards may include:

AS3925.1-1994 Software quality assurance - plans

AS4042-1992 Software configuration management plans

AS4043-1992 Software configuration management

AS/NZS14102:1998 Information technology - guideline for evaluation and selection of CASE tools

AS/NZS4258:1994 Software user documentation process

AS/NZS ISO/IEC 12207:1997 Information technology - Software life cycle processes

current international and Australian standards.

Standards may include:

Australian Standards (AS)

International Electrotechnical Commission (IEC)

International Organization for Standardization (ISO)

software development standards.

Appropriate person may include:

authorised business representative

client

supervisor.

Documentation may follow:

audit trails

ISO, IEC and AS standards

maintaining equipment inventory, client training and satisfaction reports

naming standards

project-management templates and report writing

version control.

Requirements may relate to:

business

database

network

people in the organisation

platform

system.

Client may include:

clubs

external organisations

individuals

internal departments

internal employees.

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
1.1 Review copies of the organisation's quality standards and standards related to software development and prepare for use 
Contact appropriate person to discuss their involvement in the review and establish their role 
Determine and document the approach to be used to validate quality during the review 
Examine and document processes that have a significant impact on the quality of a particular product under development 
Hold discussions on quality issues with development staff and establish agreed actions 
Allocate responsibilities to development staff 
Obtain agreement from appropriate person on procedures to ensure quality of development, where necessary 
Review plans to ensure that they are adequate to control the quality of the development process 
Review testing processes to ensure that defect-free software will be developed 
Examine documentation and methods for development to ensure that software will be supportable 
Monitor requirements to ensure that client needs are met 

Forms

Assessment Cover Sheet

ICAPRG515A - Review developed software
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICAPRG515A - Review developed software

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: