NTISthis.com

Evidence Guide: ICTNWK515 - 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

 

ICTNWK515 - 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 backups
  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
  5. Document control and monitoring mechanisms
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 backups

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:

 

 

 

 

 

 

 

Document control and monitoring mechanisms

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 and 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 and 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

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Establish configuration management requirements

1.1 Establish identification standards for naming and version control of system, network, software and documentation to align with organisational needs

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

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

1.4 Determine the appropriate points for configuration of particular items

2. Establish control mechanisms

2.1 Establish methods for identification and recording of change requests in line with organisational guidelines

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

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

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

3. Establish monitoring mechanisms

3.1 Establish mechanisms to identify software status throughout the software life cycle, or the status of the system or network during upgrading or reconfiguration

3.2 Determine management of records and status reports, including the history of baselines and their links to backups

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

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

3.5 Document control and monitoring mechanisms

4. Manage the release of the product to clients

4.1 Determine physical and functional completeness of items prior to release

4.2 Determine requirements for formal control of software products and documentation

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

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Establish configuration management requirements

1.1 Establish identification standards for naming and version control of system, network, software and documentation to align with organisational needs

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

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

1.4 Determine the appropriate points for configuration of particular items

2. Establish control mechanisms

2.1 Establish methods for identification and recording of change requests in line with organisational guidelines

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

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

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

3. Establish monitoring mechanisms

3.1 Establish mechanisms to identify software status throughout the software life cycle, or the status of the system or network during upgrading or reconfiguration

3.2 Determine management of records and status reports, including the history of baselines and their links to backups

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

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

3.5 Document control and monitoring mechanisms

4. Manage the release of the product to clients

4.1 Determine physical and functional completeness of items prior to release

4.2 Determine requirements for formal control of software products and documentation

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

Evidence of the ability to:

develop technical and administrative procedures for use during the software life cycle, system or network reconfiguration or the upgrade process, including:

quality processes

audit trials

version control

configuration management procedures.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain benchmarking methodologies

outline configuration management

summarise control mechanisms, such as acceptance criteria, test and acceptance processes, and security, access and management control criteria

explain monitoring mechanisms

identify and describe standards, benchmarks and organisational guidelines that impact on management protocols

outline project planning methodologies and tools

summarise quality assurance and quality processes

clarify safety, security and legislative requirements

explain software development methodologies.