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. Gather and confirm client requirements
  2. Analyse functional and related non-functional requirements
  3. Analyse the feasibility of a project
  4. Develop high-level system solutions
  5. Prepare and publish software-requirements documentation

Required Skills

Required skills

analytical skills to

evaluate audience needs

model business processes

communication skills to

determine appropriate content formats and styles

question and actively listen

literacy skills to

evaluate and present information

write reports for business requiring indepth analysis and evaluation of information in a defined range of areas

numeracy skills to produce financial models for identifying analysing and evaluating a range of solutions

planning and organisational skills to

identify target audiences

plan projects in relation to scope time cost quality communications and risk management

problemsolving skills to identify viable solutions to meet client requirements

research skills to

identify analyse and evaluate broad features of a particular business domain and best practice in system development

identify relevant content

technical skills to

use modelling tools

use wordprocessing software and multimediaauthoring tools

Required knowledge

clientbusiness domain

content features such as clarity and readability

detailed knowledge of the systems current functions

document design and usability

functions and features of templates and style guides

instructionaldesign principles

role of stakeholders and the degree of stakeholder involvement

two or more current industry systems development methodologies

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

research and analyse client requirements in order to present a range of solution options

create a software requirements document applying content format and style according to relevant organisational standards

Context of and specific resources for assessment

Assessment must ensure access to

specific requirements including client and functionality

wordprocessing software such as Microsoft Word

modelling software currently used in industry

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 software requirements documentation

verbal or written questioning to assess candidates knowledge of modelling tools

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.

Client may include:

external organisations

individuals

internal departments

internal employees.

Sources of information may involve:

business-strategic plans

change-management plans

current systems-design plans

project-management plans.

Project scope may include:

budget

features

hardware

policy and legal constraints

resource

software

time.

Unified modelling language may include:

activity diagram

class diagram

use-case diagram

use-case narrative.

Feasibility may include:

economic and schedule feasibility as well as the principal inputs and outputs

expected improvements and impacts

operational feasibility

physical requirements of each solution

revenue and cost-benefits

risks

technical feasibility.

Solutions may include:

hardware upgrades

new system implementation

new hardware

new software

software upgrades

user training.

Requirements may be in reference to:

business

network

organisational policies

people in the organisation

system.

Constraints may include:

budget

hardware

legal

organisational policy

resources

software

time.

Resources may include:

equipment

infrastructure

networks

personnel.

Software requirements document may include:

brochures

help references, such as online help

operational procedures

reports

solution design

solution feasibility

system design

system functionality

system or project specifications

technical manuals

training materials and self-paced tutorials

user guides.

Appropriate person may include:

authorised business representative

client

supervisor.

Project may include:

business improvement process

ebusiness solution involving the total organisation or part of the organisation

projects involving a business undertaking a total organisational change

systems-only change.