Modification History
Not Applicable
Unit Descriptor
Unit descriptor |
This unit defines the competency required to plan and conduct acceptance testing as part of the process whereby clients will determine whether to accept the system. These units are linked and form an appropriate cluster:
No licensing, legislative, regulatory or certification requirements apply to this unit at the time of publication. |
Application of the Unit
Application of the unit |
Licensing/Regulatory Information
Refer to Unit Descriptor
Pre-Requisites
Prerequisite units |
||
ICAW4027B |
Relate to clients on a business level |
|
Employability Skills Information
Employability skills |
This unit contains employability skills. |
Elements and Performance Criteria Pre-Content
Elements describe the essential outcomes of a unit of competency. |
Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the required skills and knowledge section and the range statement. Assessment of performance is to be consistent with the evidence guide. |
Elements and Performance Criteria
ELEMENT |
PERFORMANCE CRITERIA |
1. Identify acceptance criteria and develop test plan |
1.1. Review system requirements documentation and project plans to identify mandatory system objectives and optional criteria/conditions for acceptance of system 1.2. Develop test plan based on system requirements 1.3. Review and validate the test plan based on mandatory criteria/conditions, and system objectives and requirements 1.4. Clearly communicate the test plan to the client and prepare the client for the acceptance test 1.5. Notify appropriate person of the scheduled acceptance test |
2. Perform functional testing on software modules |
2.1. Prepare the test environment for client use 2.2. Perform the testing according to the test plan and documentation 2.3. Execute each test cycle 2.4. Document errors, difficulties or communicated problems |
3. Validate test results against expected results |
3.1. Record and investigate discrepancies and corrections according to project procedures and timeframe 3.2. Brief the client on outcomes to ensure the client understands test results 3.3. Monitor system performance as required 3.4. Reschedule required code changes or modifications |
4. Obtain signoff and acceptance |
4.1. Confirm with the client the results of the test 4.2. Identify and document client concerns over system operation, identify possible solutions, and if necessary notify appropriate development staff 4.3. Obtain client acceptance and sign-off by the client of that acceptance 4.4. Seek and formalise the agreement of involved parties regarding the rescheduling of further required maintenance |
Required Skills and Knowledge
REQUIRED SKILLS AND KNOWLEDGE |
This section describes the skills and knowledge required for this unit. |
Required skills |
|
Required knowledge |
|
Evidence Guide
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:
To demonstrate competency in this unit the person will require access to:
|
Context of and specific resources for assessment |
Formal acceptance testing is conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. Such testing is designed to determine whether the system meet the requirements specified in the contract or by the user. Client user acceptance is a phase within the overall development life cycle of a system. Client acceptance testing usually occurs during the implementation phase, but planning and preparation should begin in the design phase, and run concurrently (design/code/implementation). Acceptance tests relate to the functionality of the system as stated in the requirements specification, and functional test cases must be selected to satisfy the agreed acceptance criteria. These tests cover areas such as performance, security, reliability, load/stress testing, volume testing, human computer interaction tests, configuration testing, compatibility testing, documentation, and human procedures. Client acceptance tests should be a strictly controlled process. 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:
The person will need to ensure that:
|
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.
|
Guidance information for assessment |
Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, for example:
An individual demonstrating this competency would be able to:
|
Range Statement
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. |
|
Client may include but is not limited to: |
|
Appropriate person may include: |
|
Unit Sector(s)
Unit sector |
Test |
Co-requisite units
Co-requisite units |
||
Competency field
Competency field |