NTISthis.com

Evidence Guide: ICTICT304 - Implement system software changes

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

 

ICTICT304 - Implement system software changes

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

Determine system changes required

  1. Determine and record required changes to system
  2. Ensure documentary evidence exists to support changes and evaluate changes required
  3. Complete documentation required according to maintenance methodologies
  4. Clarify and confirm nature of the changes with the client
  5. Obtain technical data from reliable sources and request other resources that may be required to complete the changes
Determine and record required changes to system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure documentary evidence exists to support changes and evaluate changes required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Complete documentation required according to maintenance methodologies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Clarify and confirm nature of the changes with the client

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Obtain technical data from reliable sources and request other resources that may be required to complete the changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Carry out system changes

  1. Plan the procedure to effect intended changes
  2. Consult with colleagues and users involved in the proposed changes and agree a mutually acceptable timeline and method of implementation
  3. Copy initialisation or configuration files prior to implementation
  4. Create a roll-back path in the event of failure
  5. Ensure changes required in software are made according to project or organisational guidelines
  6. Test and verify that the changes have been made according to implementation guides and organisational standards
Plan the procedure to effect intended changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consult with colleagues and users involved in the proposed changes and agree a mutually acceptable timeline and method of implementation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Copy initialisation or configuration files prior to implementation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create a roll-back path in the event of failure

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure changes required in software are made according to project or organisational guidelines

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test and verify that the changes have been made according to implementation guides and organisational standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Present changes to client

  1. Demonstrate changes to the client and explain the impact of these changes
  2. Work towards making these changes acceptable to the client if changes are rejected, or making further modifications if required
  3. Update documentation and repositories according to standards and update modifications made to the change management system
Demonstrate changes to the client and explain the impact of these changes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Work towards making these changes acceptable to the client if changes are rejected, or making further modifications if required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Update documentation and repositories according to standards and update modifications made to the change management system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform handover to client

  1. Update documentation and client procedures to reflect changes made
  2. Secure sign-off of acceptance documents by client
  3. 4.3 Facilitate handover of modified system to client's operational area
Update documentation and client procedures to reflect changes made

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Secure sign-off of acceptance documents by client

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

4.3 Facilitate handover of modified system to client's operational area

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. Determine system changes required

1.1 Determine and record required changes to system

1.2 Ensure documentary evidence exists to support changes and evaluate changes required

1.3 Complete documentation required according to maintenance methodologies

1.4 Clarify and confirm nature of the changes with the client

1.5 Obtain technical data from reliable sources and request other resources that may be required to complete the changes

2. Carry out system changes

2.1 Plan the procedure to effect intended changes

2.2 Consult with colleagues and users involved in the proposed changes and agree a mutually acceptable timeline and method of implementation

2.3 Copy initialisation or configuration files prior to implementation

2.4 Create a roll-back path in the event of failure

2.5 Ensure changes required in software are made according to project or organisational guidelines

2.6 Test and verify that the changes have been made according to implementation guides and organisational standards

3. Present changes to client

3.1 Demonstrate changes to the client and explain the impact of these changes

3.2 Work towards making these changes acceptable to the client if changes are rejected, or making further modifications if required

3.3 Update documentation and repositories according to standards and update modifications made to the change management system

4. Perform handover to client

4.1 Update documentation and client procedures to reflect changes made

4.2 Secure sign-off of acceptance documents by client

4.3 Facilitate handover of modified system to client's operational area

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. Determine system changes required

1.1 Determine and record required changes to system

1.2 Ensure documentary evidence exists to support changes and evaluate changes required

1.3 Complete documentation required according to maintenance methodologies

1.4 Clarify and confirm nature of the changes with the client

1.5 Obtain technical data from reliable sources and request other resources that may be required to complete the changes

2. Carry out system changes

2.1 Plan the procedure to effect intended changes

2.2 Consult with colleagues and users involved in the proposed changes and agree a mutually acceptable timeline and method of implementation

2.3 Copy initialisation or configuration files prior to implementation

2.4 Create a roll-back path in the event of failure

2.5 Ensure changes required in software are made according to project or organisational guidelines

2.6 Test and verify that the changes have been made according to implementation guides and organisational standards

3. Present changes to client

3.1 Demonstrate changes to the client and explain the impact of these changes

3.2 Work towards making these changes acceptable to the client if changes are rejected, or making further modifications if required

3.3 Update documentation and repositories according to standards and update modifications made to the change management system

4. Perform handover to client

4.1 Update documentation and client procedures to reflect changes made

4.2 Secure sign-off of acceptance documents by client

4.3 Facilitate handover of modified system to client's operational area

Evidence of the ability to:

evaluate, document and implement changes to the system with minimum disruption to the system and client users

hand over the project to the client with instructions and updated documentation.

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:

identify and describe business scheduling requirements

identify change control procedures

describe client business domain

discuss current industry accepted hardware and software products

discuss emerging standards for data and voice communications

outline the system's current functionality

discuss the features of the system under modification

outline the organisational policy and procedures with regard to system changes

recognise vendor software services with regard to system changes.