NTISthis.com

Evidence Guide: ICAPRG419A - Analyse software requirements

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICAPRG419A - Analyse software requirements

What evidence can you provide to prove your understanding of each of the following citeria?

Gather and confirm client requirements

  1. Confirm requirements and scope with the client
  2. Gather information regarding requirements via sources of information and business processes
  3. Analyse client requirements to determine the project scope and the problem context or opportunity faced by the business
  4. Document client requirements, project scope, related problems and sources of information
Confirm requirements and scope with the client

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Gather information regarding requirements via sources of information and business processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse client requirements to determine the project scope and the problem context or opportunity faced by the business

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document client requirements, project scope, related problems and sources of information

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse functional and related non-functional requirements

  1. Map business processes using modelling tools, such as unified modelling language (UML)
  2. Determine opportunities for business process efficiencies
  3. Document functional and related non-functional processes
Map business processes using modelling tools, such as unified modelling language (UML)

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine opportunities for business process efficiencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document functional and related non-functional processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the feasibility of a project

  1. Analyse the technical feasibility of the project
  2. Analyse the operational feasibility of the project
  3. Determine the budget and schedule feasibility of the project
  4. Examine how the project will fit within the organisation
Analyse the technical feasibility of the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the operational feasibility of the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the budget and schedule feasibility of the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine how the project will fit within the organisation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop high-level system solutions

  1. Develop and document feasible solutions for client requirements
  2. Explore and document the feasibility of each solution
  3. Examine alternatives against project constraints
  4. Document assumptions, dependencies and required resources
  5. Produce a project risk analysis
  6. Document future requirements
Develop and document feasible solutions for client requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Explore and document the feasibility of each solution

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine alternatives against project constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document assumptions, dependencies and required resources

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Produce a project risk analysis

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document future requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare and publish software-requirements documentation

  1. Develop software-requirements document
  2. Submit software-requirements report to appropriate person for project approval
Develop software-requirements document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit software-requirements report to appropriate person for project approval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

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

word-processing 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 candidate’s software requirements documentation

verbal or written questioning to assess candidate’s 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 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.

Required Skills and Knowledge

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 in-depth 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

problem-solving 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 word-processing software and multimedia-authoring tools.

Required knowledge

client-business domain

content features, such as clarity and readability

detailed knowledge of the system's current functions

document design and usability

functions and features of templates and style guides

instructional-design principles

role of stakeholders and the degree of stakeholder involvement

two or more current industry systems development methodologies.

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.