QGEA document hierarchy

  • PDF

The Queensland Government Enterprise Architecture (QGEA) provides a consistent governing framework for issuing government ICT direction and supporting advice.

QGEA direction

The QGEA provides a framework for the Queensland Government to define ICT strategic direction, policy and other requirements. These documents support agencies in achieving the Government’s priorities and delivering services to Queenslanders.

The following table provides a definition of these document types:

Principles  These represent the core beliefs and values of the Queensland Government in relation to the application and management of information and underpinning technologies. They influence decisions made about resource and initiative portfolios across the sector. They are provide direction in the absence of specific policy.
Strategy Strategies are short high-level documents intended to gain in-principle agreement from senior executives to a course of action. The course of action will seek to achieve an agreed desired future state 
Action Plan An action plan tactically complements a strategy and details how a strategy will be achieved.  Action plans focus on implementation and set out information about objectives, initiatives,  and responsibilities.
Policy
(Mandatory)

These mandatory documents are clear and specific statements of direction which support achievement of long terms strategies or provide a response to issues. QGEA policies set out a government plan or course of action intended to influence decisions, actions, and other matters relating to a particular purpose. A QGEA policy contains a set of rules (requirements) expressed as either an obligation, authorisation, permission or prohibition.

QGEA policies and information standards are equivalent in their function. Information standards will be phased out over time and replaced, where applicable, with QGEA policies.

QGEA support

Generally, QGEA supporting documents are non-mandatory. These documents are designed to assist agencies and initiatives in the implementation of strategies and policies. Common support documents include frameworks, guidelines, templates, examples and methodologies. 


Some QGEA supporting documents will be mandatory if they are specified in a QGEA policy as required to be followed. For example, the Client identity management policy mandates the use of the Client identity management standard when creating new services that require client registration and/or client identification. Frameworks, positions, methodologies and standards are the most common types of QGEA supporting documents that may be mandated through a QGEA policy.  


The following table provides a definition of these document types:

Framework

A document that sets out a basic structure underlying a system or concept in a particular topic area.  Generally, a QGEA framework provides the reader with detailed information, consistent approaches, defined best practice processes, and decision making guidance. E.g. ‘ICT program and project assurance framework’, ICT as-a-service decision framework, Network transmission security assurance framework (NTSAF).

This term can also be used when referring to the QGEA classification frameworks (also commonly known as reference models or taxonomies).  These types of frameworks provide readers with a common view point of a particular topic area.

Methodology Usually consists of detailed processes, techniques, tools and guidance in a particular topic area.  A methodology does not provide solutions, but offers a range of best practice approaches that can be applied.  For example the Queensland Government ICT planning methodology assists agencies in undertaking ICT resources (investment) strategic planning activities and has a range of techniques and tools to help agencies apply a systematic and consistent approach to collecting and analysing their information, application and technology assets .
Standard Sets out detailed information in a particular area and tend to be technical in nature.  Standards are generally mandated through a QGEA policy and set out a range of mandatory, recommended elements and guidelines in a particular area. E.g. ICT cabling infrastructure technical standard.
Blueprint Translates business requirements into example architectures, patterns, plans, models and designs which are intended to provide reusable and value adding input to similar initiatives   While it can include vision and principles to support the architecture, these should not be the main focus of the document.  E.g. One William Street – State ICT Architecture Blueprint.
Guideline A guideline provides information on the recommended practices for a given topic area. Guidelines are for information only and departments are not required to comply. They are intended to help departments understand the appropriate approach to addressing a particular issue or doing a particular task.
Factsheet Similar to a guideline, but usually shorter in terms on content and length.
Template Provides a standard structure for certain documents which allows agencies to adopt, use, adapts for their own purposes.
Example Provides an illustration of what something should look like.  Within the QGEA examples can be set as part general guidance, or agencies may submit specific examples to the knowledge base as part of cross agency sharing.

QGEA governance

QGEA governance provides a mechanism for developing, reviewing and consulting on the QGEA documents. It uses a defined consultation process (Queensland Government employees only) which includes significant collaboration across the sector to ensure that the true impact and risks of creating (or not creating) a policy mandate is understood. The process also defines the roles and responsibilities for approval of the various QGEA document types.

A formalised exception process (Queensland Government employees only) also exists to accommodate the variations and demands of agency service delivery requirements to ensure flexibility of the process.

Knowledge base

The knowledge base (Queensland Government employees only) is also available to share agency specific examples to promote collaboration and reuse across the sector. Documents published in the knowledge base do not undergo the QGEA governance process.

Authority and applicability of the QGEA

Click here for information on the authority and applicability of the QGEA.