Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

  1. Evaluate software-requirement specification
  2. Create a proof-of-concept prototype
  3. Evaluate software design
  4. Evaluate source code
  5. Evaluate testing requirements
  6. Document validation

Required Skills

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 nontechnical information from a range of sources

technical skills to use

software design tools such as unified modelling language UML tools

wordprocessing 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

objectoriented programming

opensource development tools

organisational procedures for documenting technical specifications

softwaretesting techniques

Evidence Required

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 candidates 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 nonEnglish speaking background may need additional support

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

Range Statement

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