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