Modification History
Not Applicable
Unit Descriptor
Unit descriptor |
This unit defines the competency required to implement administrative and technical procedures throughout the software development and documentation life cycle. 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 |
||
ICAD4217B |
Create Technical Documentation |
|
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 and clarify configuration management requirements |
1.1. Develop and/or assemble identification standards for the naming and version control of software and documentation , and provide to stakeholders 1.2. Identify the software configuration tools and procedures for the required level of integration into the programming environment 1.3. Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes 1.4. Take action to ensure that stakeholders are aware of their roles 1.5. Identify the point at which items are subjected to configuration control with stakeholders |
2. Employ appropriate control mechanisms |
2.1. Identify and document the method for identification and recording of change requests in line with organisational requirements and ensure this is maintained during development process 2.2. Take action to ensure that the evaluation criteria and process for approval of change requests are employed according to organisational requirements 2.3. Take action to ensure that other management, security and access control criteria are employed according to organisational requirements 2.4. Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development |
3. Implement monitoring mechanisms |
3.1. Implement controls to ensure that mechanisms to identify the status of software throughout the software development life cycle are continuously maintained 3.2. Document the development and maintenance of records and status reports required to show the history of baselines and their links to back-ups 3.3. Take action to ensure that the level of detail required in the status reports, and identification of target audiences, meets the configuration management procedures, ISO/IEC/AS standards and organisational requirements 3.4. Integrate configuration management into general project management processes for monitoring and control purposes and document |
4. Manage release of product |
4.1. Take action to ensure the physical and functional completeness of items for the purpose of release to all stakeholders 4.2. Identify and implement the requirements for formal control of software products 4.3. Determine and document policies for retention of baseline/master copies, taking into account safety and security, legislative requirements and organisational guidelines |
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 |
Implementation of configuration management will usually include observation of real or simulated work processes and procedures, the results of previous configuration projects may be used to assist in understanding configuration management in a global context. The breadth, depth and complexity of knowledge and skills in this competency would cover a broad range of varied activities or application in a wider variety of contexts most of which are complex and non-routine. Leadership and guidance would be involved when organising activities of self and others as well as contributing to technical solutions of a non-routine or contingency nature. Assessment must ensure:
|
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. An individual demonstrating this competency would be able to:
To demonstrate this unit of competency the following should be addressed:
|
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. |
|
Documentation may follow: |
|
Stakeholders may include: |
|
Requirements may be in reference to: |
|
Organisational requirements may include but is not limited to: |
|
Software may include but is not limited to: |
|
Software configuration tools may include: |
|
Organisational guidelines may include but is not limited to: |
|
Unit Sector(s)
Unit sector |
Build |
Co-requisite units
Co-requisite units |
||
Competency field
Competency field |