Assessor Resource

ICAPRG426A
Prepare software development review

Assessment tool

Version 1.0
Issue Date: April 2024


This unit applies to staff in the software development area who are required to ensure that the software development process incorporates quality.

This unit describes the performance outcomes, skills and knowledge required to establish standards associated with IT technical requirements in the context of quality assurance processes applicable to 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:

establish the standards associated with the IT technical requirements, taking into account quality assurance processes that are in place for the development of software

monitor the application of these standards within the project.

Context of and specific resources for assessment

Assessment must ensure access to:

technical specifications

organisational standards for documentation and version control

project management process and hierarchy

future organisational business processes

software requirement specifications

interface requirement specifications

system requirements

design specifications

project budget and timeframe

appropriate learning and assessment support when required

modified equipment for people with special needs.

Note: Data used in preparing the development review should be validated and come from other projects or related organisational activities.

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:

verbal or written questioning to assess candidate’s knowledge of:

quality assurance

appropriate quality standards for software development

benchmarking

review of candidate’s documented software standards

evaluation of candidate’s report to stakeholders.

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

analytical skills to analyse and evaluate a range of solutions using database modelling

communication skills to:

liaise with stakeholders

provide clear communication and distribution strategies to meet project plan requirements

literacy skills to provide clear and coherent technical reports

numeracy skills to account for cost considerations in project plan

planning and organisational skills to develop a detailed project plan and schedule of quality reviews

problem-solving skills to develop technical solutions

technical skills to use metrics software.

Required knowledge

current industry-accepted software configuration management processes

quality assurance practices and the identification of standards

software metrics development

client business domain.

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.

Stakeholders may include:

development team

project team

sponsor

user.

Organisational requirements may include:

how and what the organisation wants in regard to work environment

preventative maintenance and diagnostic policy

problem solution processes

roles and technical responsibilities in the IT department

vendor and product service level support agreements.

Standards may include:

International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) standards

Java coding standards

GNU coding standards

organisational standards

project standards.

Project standards may include:

change control

delivery against required milestones and budget

development methodology

ease of modification and maintenance

project plan

quality of software modules

reporting mechanisms

sharing of code or libraries.

Communication may include:

non-verbal methods, such as written messages, emails and memos

verbal methods, such as telephone, meetings and video conferencing.

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
Ensure that stakeholders have an understanding of the organisational requirements 
Document software standards according to project standards 
Assign software standards to functions according to detailed technical plan 
Take action to ensure that communication and distribution strategies are clear, coherent and meet overall project plan requirements 
Monitor and report on implementation of standards against acceptance criteria and detailed technical specifications 
Define metrics related to the project milestones, and timeframe and cost considerations 
Develop schedule of quality reviews 
Determine quality considerations by identifying in-process measurement points that relate to critical organisational requirements 
Determine method to benchmark and scale achievement against stated stakeholders requirements and cost considerations 
Report metrics and milestones to stakeholders in a clear and coherent manner and take action to ensure written agreement 

Forms

Assessment Cover Sheet

ICAPRG426A - Prepare software development review
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

ICAPRG426A - Prepare software development review

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: