List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.
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.
Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the network industry, and include access to:
Computer aided software engineering (CASE) tools
future organisational business processes
organisational standards for documentation and version control
project budget and timeframe
project management process and hierarchy
legislation and organisational guidelines
technical specifications
test plans.
Assessors must satisfy NVR/AQTF assessor requirements.