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. |
Softwarelifecycle may include: | AS/NZS ISO/IEC 12207:1997 Information technology - Software life cycle processes AS/NZS 15271:1999 Guide for AS/NZS ISO/IEC 12207 Information technology - software life cycle processes) |
Test and acceptance processes may include: | AS 4006-1992 Software test documentation AS/NZS 14143.1:1999 Information technology - software measurement - functional size measurement - definition of concepts AS/NZS 15026:1999 Information technology - system and software integrity levels AS 4006-1992 Software test documentation, IEEE Standard for software unit testing International and Australian Standards are updated and changed on a regular basis. It is therefore important to check the Standards Australia website on a regular basis for new standards: http://www.standards.com.au |
Quality benchmarks | There are several organisations that have developed standards for software review mainly: US Department of Defence (DoD) standards, IEEE, the Software Engineering Institute (SEI), and ISO standards. Relevant quality standards include: AS 4043-1992 Software configuration management AS 4042-1992 Software configuration management plans AS 3925.1-1994 Software quality assurance - plans AS/NZS 4258:1994 Software user documentation process AS/NZS ISO/IEC 12207:1997 Information technology - software life cycle processes AS/NZS 14102:1998 Information technology - guideline for evaluation and selection of CASE tools International and Australian Standards are updated and changed on a regular basis. It is therefore important to check the Standards Australia website on a regular basis for new standards: http://www.standards.com.au |
Test and acceptance criteria | Dependent on the type of test (e.g. functional, efficiency, cohesion) |
Documentation and reporting | Documentation for version control may follow ISO/IEC/AS standards. Audit trails, naming standards, version control, project management templates and report writing styles will vary according to organisational approach. Information gathering processes may have associated templates |
Test tools may include: | Code/unit/class testing: AssertMate, BoundsChecker, C-Cover, CodeReview, CodeWizard, DeepCover, FailSafe, Hindsight, Insure++, JCAST, Logiscope, JavaPureCheck Stress load testing: automated test facilities, e-Load, E-TEST Suite, e-MONITO, Astra SiteManager, Astra SiteTest, AutoTester Web, LoadRunner, JavaLoad Applications testing: DataShark, Cyrano Suite, Datatect, preVue-C/S |