BETA

Skip links

  • Skip to primary navigation
  • Skip to content
  • Skip to footer
Queensland government logo Queensland government logo
Sign in Sign out
Sign in
  • Profile summary
  • Sign out
Department of Education Department of Education Developer Portal
  • Home
  • Tags
  • Chat
  • Beta
    APIs
  • SDLC
  • Help
  • Contact us
  • Dark mode
  • Home
  • Tags
  • Chat
  • Beta
    APIs
  • SDLC
  • Help
  • Contact us
  • My profile
  • Dark mode

Testing SDLC Artefact Glossary

Jeny Amatya2 Government
by Jeny Amatya2
27 October 2025
About
About

SDLC Artefact glossary

Artefact Required for Type 1 Release Required for Type 2 Release Required for Type 3 Release
SDLC Track Artefacts      
Information Security Assessment ✓ ✓* ✓*
Cloud Assessment Report [1] ✓ ✓ ✓
Release Risks/Issue Register ✓ ✓ ✓
Needs Stage Artefacts      
Idea Definition Document/Problem or Need Statement ✓    
Concept Stage Artefacts      
Operational Concept [2] ✓    
Terms of Reference for Project or Application Governance Board ✓    
Project Brief ✓    
Preliminary Business Requirements Specification (BRS) ✓    
Requirements Stage Artefacts      
System Requirements Specification Document (SRS) [3] ✓ ✓  
Analysis And Design Stage Artefacts      
Logical Solution Architecture[4] ✓ ✓ ✓
Physical Solution Architecture ✓ ✓ ✓
Design Review Report [5] ✓ ✓ ✓
Implementation Stage Artefacts      
All codes and scripts fully finalized and checked into DET’s selected source control environment. ✓ ✓ ✓
Test Summary Report [6] ✓ ✓ ✓
Code Review Report [7] ✓ ✓ ✓
Deployment Plan ✓ ✓ ✓
Enterprise Integration Platform Engagement [8] ✓ ✓ ✓
Accessibility Review Report [9] ✓ ✓ ✓
Quality assurance certificate ✓ ✓ ✓
Test Stage Artefacts      
Acceptance Test Summary Report ✓ ✓ ✓
Secondary Acceptance Test Summary Report (for releases with high levels of risk) [10] ✓ ✓ ✓
Production Readiness Certificate[11] ✓    
Operational Support Plan ✓ ✓ ✓
Deployment Stage Artefacts      
Vulnerability Test Report [12] ✓ ✓ ✓
Load Test Report ✓    
Release Completion Report [13] ✓ ✓ ✓
Maintenance Stage Artefacts      
System Release Schedule [14] ✓ ✓ ✓
Retirement Stage Artefacts      
Retirement Report ✓ ✓ ✓

Type 1 release

This track starts from the Needs stage and ends at the Maintenance stage and accordingly, such releases will require the artefacts and controls highlighted in all the included stages.

Type 2 release

This track starts from the Requirements stage and ends at the Maintenance stage and accordingly, such releases will require the artefacts and controls highlighted in all the included stages.

Type 3 release

This track starts from the Analysis and Design Stage and ends at the Maintenance stage and accordingly, such releases will require the artefacts and controls highlighted in all the included stages.

Footnotes

*Optional depending on whether or not data models have changed during the development of the release.

  1. Only applicable to releases with cloud-based components being used for the first time ↑
  2. Optional ↑
  3. For development activities delivering integration middleware, this artefact may be different from a System Requirements Specification (e.g. Enterprise Integration Platform (EIP) may use an Engagement artefact that wraps requirements) ↑
  4. Not applicable for Integration Middleware ↑
  5. The report can be extracted from application life cycle management tools, if used. ↑
  6. The report can be extracted from application life cycle management tools, if used. It should cover unit tests, integration tests, system tests and regression tests. ↑
  7. The report can be extracted from application life cycle management tools, if used. ↑
  8. Not applicable for development activities delivering Integration Middleware. Only applicable to solutions with system-to-system integration ↑
  9. Not applicable to Integration Middleware. Only applicable to solutions/releases with a user interface ↑
  10. Only applicable to releases with a high level of risk ↑
  11. A Production Readiness Certificate may be dependent on the results of Vulnerability and Load Tests that may be performed at later stages. ↑
  12. Only applicable to cases defined under “Vulnerability Testing Applicability Criteria” ↑
  13. This report may be extracted from application life cycle management or release management tools (e.g. Service Now) ↑
  14. This schedule may be managed and extracted from application life cycle management tools. ↑
Powered by Link to AI chat
  • Copyright
  • Disclaimer
  • Privacy
  • Right to information
  • Accessibility
  • Jobs in Queensland Government
  • Other languages

© The State of Queensland (Department of Education) 2025

Queensland Government