NTISthis.com

Evidence Guide: ICASAD604A - Manage and communicate IT solutions

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

 

ICASAD604A - Manage and communicate IT solutions

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

Manage identified client IT requirements and scope of solution

  1. Establish baseline client IT requirements and change control processes to track changes to requirements and solution scope
  2. Resolve issues and conflicts that emerge during final stages of identifying and analysing requirements
  3. Determine how requirements will be presented for review
  4. Secure approval of requirements from those stakeholders who have the appropriate authority
Establish baseline client IT requirements and change control processes to track changes to requirements and solution scope

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Resolve issues and conflicts that emerge during final stages of identifying and analysing requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine how requirements will be presented for review

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Secure approval of requirements from those stakeholders who have the appropriate authority

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage requirement relationships and dependencies

  1. Examine and organise the set of requirements and record the dependencies and relationships for each
  2. Perform impact analysis to assess or evaluate the impact of a change
  3. Deploy requirements management tools as necessary
Examine and organise the set of requirements and record the dependencies and relationships for each

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform impact analysis to assess or evaluate the impact of a change

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Deploy requirements management tools as necessary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Maintain requirements for re-use

  1. Identify requirements that the organisation will use in the long term
  2. Name and define requirements available for future re-use
Identify requirements that the organisation will use in the long term

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Name and define requirements available for future re-use

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare requirements package

  1. Decide which formats are appropriate for a particular project and its stakeholders
  2. Prepare requirements package according to organisational need
Decide which formats are appropriate for a particular project and its stakeholders

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare requirements package according to organisational need

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Communicate requirements

  1. Communicate requirements iteratively and in conjunction with business analysis tasks
  2. Develop and deliver presentations of requirements according to communication objectives
Communicate requirements iteratively and in conjunction with business analysis tasks

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop and deliver presentations of requirements according to communication objectives

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:

establish processes to trace requirements, and control and track changes to requirements and solution scope

package and communicate requirements according to what is appropriate for a project or stakeholder group.

Context of and specific resources for assessment

Assessment must ensure access to:

documentation, including appropriate policies, current business analysis practices, tools and legislation

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:

evaluation of a simulated or workplace project in a medium to large enterprise

direct observation of the candidate carrying out business analysis work

verbal or written questioning to assess required knowledge and skills

review of reports and plans prepared for the projects

evaluation of a portfolio of the project work undertaken.

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 perform impact analysis of possible changes to solution scope

communication skills to bring stakeholders from different backgrounds and business domains to a common understanding of the IT requirements

organisational and management skills to manage the integrity of requirements to the business goals and actual solution through uncertainty and change over time

strategic thinking skills to ensure that knowledge of the organisation gained during business analysis is available for future use

technical skills to develop evaluation criteria.

Required knowledge

conflict-resolution and issue-management techniques to handle possible changes to solution scope

requirements management and requirements traceability processes

techniques for managing version control and configuration.

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.

Requirements management tools may include:

Caliber-RM

MKS requirements

Requisite Pro

RTM Workshop

SoftREQ

Teamcenter

TestTrackRM.

Requirements package may exist in the form of:

formal documentation, usually based on a template used by the organisation, such as a vision document or software requirements specification

models, where the requirements may be presented only in the form of a model, such as a process map, or captured on a whiteboard

presentation that delivers a high-level overview of the functionality delivered by the solution.

Business analysis tasks may include:

enterprise analysis tasks

elicitation tasks

requirements analysis tasks

solution assessment and validation tasks.

Presentations of requirements may be used to:

as a precursor to delivery, e.g. examining solution options with a delivery team

ensure cross-functional fit with other business process areas within the same project

ensure that internal project quality standards have been adhered to

make decisions regarding solution scope

obtain business acceptance and sign-off

obtain delivery team sign-off

obtain testing team sign-off

prioritise a set of requirements before proceeding to next project stage.