NTISthis.com

Evidence Guide: ICAA5048B - Develop configuration management protocols

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

 

ICAA5048B - Develop configuration management protocols

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

Establish configuration management requirements

  1. Establish identification standards for naming and version control of system, network, software and documentation to align with organisational needs
  2. Establish tools and procedures for the required level of integration into the programming, system or network environment
  3. Determine responsibilities for configuration management within the project and for ongoing support, including approval of changes
  4. Determine the appropriate points for configuration of particular items
Establish identification standards for naming and version control of system, network, software and documentation to align with organisational needs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish tools and procedures for the required level of integration into the programming, system or network environment

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine responsibilities for configuration management within the project and for ongoing support, including approval of changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the appropriate points for configuration of particular items

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish control mechanisms

  1. Establish methods for identification and recording of change requests in line with organisational guidelines
  2. Establish acceptance criteria, test and acceptance processes and processes for approval of change requests in line with organisational guidelines
  3. Establish security, access and management control criteria, and quality benchmarks
  4. Determine necessary audit trails and alerts for variations or non-conformance
Establish methods for identification and recording of change requests in line with organisational guidelines

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish acceptance criteria, test and acceptance processes and processes for approval of change requests in line with organisational guidelines

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish security, access and management control criteria, and quality benchmarks

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine necessary audit trails and alerts for variations or non-conformance

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish monitoring mechanisms

  1. Establish mechanisms to identify software status throughout the software life cycle, or the status of the system or network during upgrading or reconfiguration
  2. Determine management of records and status reports, including the history of baselines and their links to back-ups
  3. Define target audiences and determine the level of detail required in the status reports
  4. Integrate configuration management into general project management processes for monitoring and control purposes
Establish mechanisms to identify software status throughout the software life cycle, or the status of the system or network during upgrading or reconfiguration

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine management of records and status reports, including the history of baselines and their links to back-ups

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define target audiences and determine the level of detail required in the status reports

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Integrate configuration management into general project management processes for monitoring and control purposes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage the release of the product to clients

  1. Determine physical and functional completeness of items prior to release
  2. Determine requirements for formal control of software products and documentation
  3. Determine policies for retention of baseline/master copies in line with safety, security and legislative requirements and organisational guidelines
Determine physical and functional completeness of items prior to release

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine requirements for formal control of software products and documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine policies for retention of baseline/master copies in line with safety, security and legislative requirements and organisational guidelines

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 following is essential:

Assessment must confirm knowledge of quality processes, audit trials and version control.

Assessment must confirm the ability to develop reliable and valid configuration management procedures for technical and administrative procedures for use during the software life cycle, system or network reconfiguration or the upgrade process.

To demonstrate competency in this unit the learner will require access to:

Technical specifications

Organisational standards for documentation and version control

Project management process and hierarchy

CASE tools

Future organisational business processes

Test plan

Project budget and timeframe

Context of and specific resources for assessment

The breadth, depth and complexity covering planning and initiation of alternative approaches to skills or knowledge applications across a broad range of technical and/or management requirements, evaluation and coordination would be characteristic.

Assessment must ensure:

self-directed application of knowledge and skills, with substantial depth in some areas where judgement is required in planning and selecting appropriate equipment, services and techniques for self and others.

Applications involve participation in development of strategic initiatives as well as personal responsibility and autonomy in performing complex technical operations or organising others. It may include participation in teams including teams concerned with planning and evaluation functions. Group or team coordination may also be involved.

Method of assessment

The purpose of this unit is to define the standard of performance to be achieved in the workplace. In undertaking training and assessment activities related to this unit, consideration should be given to the implementation of appropriate diversity and accessibility practices in order to accommodate people who may have special needs. Additional guidance on these and related matters is provided in ICA05 Section 1.

Competency in this unit should to be assessed using summative assessment to ensure consistency of performance in a range of contexts. This unit can be assessed either in the workplace or in a simulated environment. However, simulated activities must closely reflect the workplace to enable full demonstration of competency.

Assessment will usually include observation of real or simulated work processes and procedures and/or performance in a project context as well as questioning on underpinning knowledge and skills.

The questioning of team members, supervisors, subordinates, peers and clients where appropriate may provide valuable input to the assessment process. The interdependence of units for assessment purposes may vary with the particular project or scenario.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended

An individual demonstrating this competency would be able to:

Demonstrate understanding of a broad knowledge base incorporating theoretical concepts, with substantial depth in some areas

Analyse and plan approaches to technical problems or management requirements

Transfer and apply theoretical concepts and/or technical or creative skills to a range of situations

Evaluate information, using it to forecast for planning or research purposes

Take responsibility for own outputs in relation to broad quantity and quality parameters

Take some responsibility for the achievement of group outcomes

Maintain knowledge of industry products and services

Required Skills and Knowledge

Required skills

Problem solving skills for a defined range of unpredictable problems involving participation in the development of strategic initiatives (e.g. when determining tools and procedures for the required level of integration into the programming environment)

Plain English literacy and communication skills in relation to developing technical and business reports (e.g. when determining the level of detail required in the status reports and when defining target audiences)

Group facilitation and presentation skills in relation to transferring and collecting information and gaining consensus on concepts (e.g. when determining responsibilities for configuration management within the project, and for ongoing support, including approval of changes)

Project planning skills in relation to scope, time, cost, quality, communications and risk management (e.g. when integrating configuration management into general project management processes for monitoring and control purposes)

Research skills for specifying, analysing and evaluating broad features of a particular business domain and best practice in software development methodologies (e.g. when determining tools and procedures for the required level of integration into the programming environment)

Estimating function point analysis and other skills for use across a range of predictable project contexts in relation to either varied or highly specific functions (e.g. when determining the point at which items are subjected to configuration control)

Required knowledge

Detailed knowledge of software development methodologies (e.g. when developing configuration management requirements)

Detailed knowledge of quality assurance and quality processes (e.g. when developing configuration management requirements)

Broad knowledge of project planning methodologies and tools (e.g. when establishing control and monitoring mechanisms)

Detailed knowledge of benchmarking methodologies (e.g. when developing administrative and technical procedures throughout the software and documentation life cycle)

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.

Standards may include:

ISO/IEC/AS standards

organisational standards

project standards (for further information refer to the Standards Australia website at: www.standards.com.au)

System may include but is not limited to:

databases

applications

servers

operating systems

gateways

application service provider

ISP

Software may include but is not limited to:

Commercial

in-house

packaged

customised software

Network may include but is not limited to:

large and small LANs

WANs

the internet

the use of the PSTN for dial-up modems only

VPNs

private lines

data

voice

Documentation may follow:

ISO/IEC/AS standards

audit trails

naming standards

version control

project management templates and report writing

maintaining equipment inventory

client training and satisfaction reports

Project may include:

a total organisational change

a systems-only change

a business improvement process

an e-business solution involving the total organisation or part of the organisation

Organisational guidelines may include but is not limited to:

personal use of emails and internet access

content of emails

downloading information and accessing particular websites

opening mail with attachments

virus risk

dispute resolution

document procedures and templates

communication methods

financial control mechanisms

Acceptance criteria may include:

timeframe

cost implications

technical and logistical considerations

Test and acceptance processes

May vary according to size and type and scope of the project

AS 4006-1992 Software test documentation may be relevant to this unit

ISO/IEC/AS standards are updated and changed on a regular basis; it is therefore important to check the Standards Australia website: (www.standards.com.au ) on a regular basis for new standards

Quality benchmarks relevant quality standards include:

AS 4043-1992 Software configuration management

AS 4042-1992 Software configuration management plans

AS 3925.1-1994 Software quality assurance - plans

AS/NZS 4258:1994 Software user documentation process

AS/NZS ISO/IEC 12207:1997 Information technology - software life cycle processes

AS/NZS 14102:1998 Information technology - guideline for evaluation and selection of computer-aided software engineering (CASE) tools

International and Australian Standards are updated and changed on a regular basis, it is therefore important to check the Standards Australia website (www.standards.com.au ) on a regular basis for new standards.

May vary according to the type of organisation, and the benchmarks will cover technical, cost savings, performance and quality. Some organisations may be quality-certified and have well-documented standards for addressing quality while others will not; in a simulated environment, best practice workplace examples will be used.