Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners

ICAPRG520A Mapping and Delivery Guide
Validate an application design against specifications

Version 1.0
Issue Date: April 2024


Qualification -
Unit of Competency ICAPRG520A - Validate an application design against specifications
Description This unit describes the performance outcomes, skills and knowledge required to check the software application design against specifications and apply validation techniques across the system life cycle.
Employability Skills This unit contains employability skills.
Learning Outcomes and Application This unit applies to individuals employed in the area of software development responsible for verifying and validating software-design specifications.They may be individuals who work as software project managers, testers, software engineers, system analysts and software developers.
Duration and Setting X weeks, nominally xx hours, delivered in a classroom/online/blended learning setting.
Prerequisites/co-requisites Not applicable.
Competency Field
Development and validation strategy and guide for assessors and learners Student Learning Resources Handouts
Activities 		Slides
PPT 		Assessment 1 Assessment 2 Assessment 3 Assessment 4
Elements of Competency Performance Criteria              
Element: Evaluate software-requirement specification
  • Review software requirement specifications document to ensure that requirements are completely specified and correct before software design begins
  • Validate the software requirement specifications document
       
Element: Create a proof-of-concept prototype
  • Use rapid application development tools to create prototype system
  • Present prototype system for demonstration to appropriate person
  • Validate proof of concept
       
Element: Evaluate software design
  • Determine if the design is complete, accurate, consistent and feasible
  • Validate software design document
  • Validate database structure and elements
  • Validate user interface (UI)
  • Review software risk analysis
       
Element: Evaluate source code
  • Validate consistency between code and software design document
  • Validate logical structure and syntax using static analysis tools
       
Element: Evaluate testing requirements
  • Review and validate test plans
  • Review and validate test cases
       
Element: Document validation
  • Document results of validation exercise
  • Recommend current software design or itemise required alterations
  • Submit report to appropriate person for action
       


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:

verify and validate software application design, including:

creating proof of concept (PoC) prototype

evaluating the technical specification and comparing against the PoC

interpreting and evaluating software design documentation requirements and confirming details with the client

analysing and validating user interface and database requirements

effectively using static analysis tools

walkthrough documents, test plans and test cases.

Context of and specific resources for assessment

Assessment must ensure access to:

tools to create prototype systems

static analysis tools

test plan and test cases

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:

review of candidate’s validation documents

evaluation of validation documents.

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, assignment, 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 determine audience needs

communication skills to:

interact with developer to ensure proper implementation

provide leadership and motivation

literacy skills to:

create technical documentation related to software design

read and interpret complex technical and non-technical information from a range of sources

technical skills to use:

software design tools, such as unified modelling language (UML) tools

word-processing software

UI design.

Required knowledge

basic knowledge of database design and implementation

business and technical modelling using UML tools at intermediate level

current software development methodologies

detailed knowledge of system development life cycle (SDLC)

object-oriented programming

open-source development tools

organisational procedures for documenting technical specifications

software-testing techniques.

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.

Software requirement specifications document may include:

reports

risks and resourcing

software functions

software system inputs and outputs

timeframe.

Software design document may include:

module test plan generation

test-design generation

traceability analysis

update software risk analysis.

Database structure and elements may include:

database consistency

database integrity

database structure.

User interface may include:

appearance

consistency

design

functions

navigation.

Static analysis tools may include:

Blast (c language)

Checkstyle (for Java)

JSLint (JavaScript checker)

StyleCop (for .net languages).

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
Review software requirement specifications document to ensure that requirements are completely specified and correct before software design begins 
Validate the software requirement specifications document 
Use rapid application development tools to create prototype system 
Present prototype system for demonstration to appropriate person 
Validate proof of concept 
Determine if the design is complete, accurate, consistent and feasible 
Validate software design document 
Validate database structure and elements 
Validate user interface (UI) 
Review software risk analysis 
Validate consistency between code and software design document 
Validate logical structure and syntax using static analysis tools 
Review and validate test plans 
Review and validate test cases 
Document results of validation exercise 
Recommend current software design or itemise required alterations 
Submit report to appropriate person for action 

Forms

Assessment Cover Sheet

ICAPRG520A - Validate an application design against specifications
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

ICAPRG520A - Validate an application design against specifications

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: