NTISthis.com

Evidence Guide: ICAICT403A - Apply software development methodologies

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

 

ICAICT403A - Apply software development methodologies

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

Determine and select appropriate methodology for a given activity

  1. Determine and define subject activity
  2. Define criteria for selection of development methodology
  3. Review and evaluate a range of traditional and non-traditional system development methodologies
  4. Select appropriate system development methodology to suit the activity
Determine and define subject activity

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define criteria for selection of development methodology

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review and evaluate a range of traditional and non-traditional system development methodologies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Select appropriate system development methodology to suit the activity

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Apply the selected development methodology

  1. Create an initial project plan to guide developmental processes
  2. Identify appropriate task types according to development methodology
  3. Clearly describe and articulate task types
  4. Define appropriate control structures that need to be created during task type execution
  5. Associate each task type with a set of input and output parameters
Create an initial project plan to guide developmental processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify appropriate task types according to development methodology

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Clearly describe and articulate task types

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define appropriate control structures that need to be created during task type execution

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Associate each task type with a set of input and output parameters

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Adjust project to suit appropriate methodology

  1. Identify resources to support methodology selection
  2. Apply appropriate methodology to solve tasks
  3. Monitor project flow and record effectiveness against project plan
  4. Review and document opportunities for improvement, lessons learned and recommendations for future projects
  5. Submit results to appropriate person for approval
Identify resources to support methodology selection

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Apply appropriate methodology to solve tasks

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Monitor project flow and record effectiveness against project plan

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review and document opportunities for improvement, lessons learned and recommendations for future projects

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit results to appropriate person for 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:

develop a project plan

apply a methodology to a project

produce documentation as required by the chosen methodology.

Context of and specific resources for assessment

Assessment must ensure access to:

design specifications and current methodologies

organisational standards for documentation and version control

detailed user requirements document, including model and scope

appropriate learning and assessment support when required.

Where applicable, physical resources should include equipment modified 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:

direct observation of candidate conducting the stages of a development methodology within the scope of a project

verbal or written questioning to assess candidate’s knowledge of a variety of system development methodologies and their application to a systems project

review of supporting documentation produced by candidate.

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 analyse the benefits of one methodology over another

communication skills to:

gain consensus on concepts when planning the application of the methodology to the project

present information

literacy skills to:

prepare reports required by development methodology

write business reports

planning and organisational skills to:

develop project plan

manage system development

problem-solving skills to select development methodology suitable to a client business context

technical skills to evaluate development methodologies.

Required knowledge

client business domain and organisational requirements

current project requirements

role of stakeholders and the degree of stakeholder involvement in the development process

two or more current industry 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.

Methodology may include:

traditional methodology

non-traditional methodology.

Traditional system development methodologies may include:

design methodology

structured systems analysis

system development life cycle.

Non-traditional system development methodologies may include:

multi-view

object-oriented analysis and design

prototyping

soft system methodology.

Project may include:

business improvement process

ebusiness solution involving the total organisation or part of the organisation

systems-only change

total organisational change.

Task types may include:

development process activities

cultural

organisational

procedural.

Control structures may include:

acceptance criteria

inspection

review process

test plans.

Input and output may include:

pre-conditional options, such as a check to confirm that inputs fulfil specific requirements

post-conditional options, such as a check that outputs have met quality requirements.

Appropriate person may include:

authorised business representative

client

supervisor.