Home >> ICT Strategy & Governance >> Australian Government Architecture >> AGA Reference Models version 3.0 >> 3 Metamodel

3 Metamodel

• 3.1 Introduction
• 3.2 Structure
• 3.3 Metamodel Concepts
• 3.4 Metamodel Elements by Layer

 

3.1 Introduction

The Australian Government Architecture (AGA) Metamodel describes the alignment of agency entities to the AGA Reference Models.

3.2 Structure

This document is organised into the following sections:

Metamodel Structure

Section	Description
Metamodel concepts	Introduces the key concepts of the AGA Metamodel and provides an overview of the AGA Reference Models.
Metamodel elements by layer	Describes each metamodel element in detail, including all entity types, type attributes and relationships. These elements are grouped logically into layers aligning with the AGA Reference Models.

3.3 Metamodel concepts

To understand this document, it is important to be aware of some of the key concepts of enterprise architecture modelling.

The AGA Metamodel defines the types of information described by the AGA Reference Models. The types of data the metamodel describes are called entity types. Conceptually, related entity types are grouped into layers which are described below in Table 1: Description of the AGA Metamodel Layers.

Each entity type contains one or more attributes describing the entity. Further, each entity type may be conceptually linked to one or more other entity types in a relationship of some kind.

3.3.1 AGA Metamodel layers

Enterprise Architecture frameworks are organised into layers, or perspectives. The Australian Government Architecture Reference Models define the five layers of enterprise architecture (Performance, Business, Service, Technical and Data).

This version of the AGA Metamodel outlines the Business, Service and Technical layers. A short description of these layers is in Table 3-1.

Table 3-1: Description of the AGA Metamodel layers

Layer	Description
Performance	This will align to the AGA Performance Reference Model (PRM).
Business	Describes government initiatives and business processes, aligned to the AGA Business Reference Model (BRM).
Service	Describes the services and the components that implement business processes, aligned to the AGA Service Reference Model (SRM).
Technical	Describes the technology and the standards that implement the Components of the Service Layer, aligned to the AGA Technical Reference Model (TRM).
Data	This will align to the AGA Data Reference Model (DRM).

The layers are organised from top to bottom in the order described above with the AGA Reference Models and the Agency context is separated for clarity.

3.3.2 Common attributes

There is a set of entity attributes common to all entity types. These are:

Attributes	Type	Description
Name	String	An instance name that uniquely identifies the entity instance
Description	String	A brief description of the entity instance.

These common attributes will not be repeated, unless there is a special requirement.

3.3.3 Metamodel overview diagram⁵

Figure 3‑1: Metamodel Overview
click on image to view larger size

3.4 Metamodel elements by layer

3.4.1 Performance layer

This section is still being developed, and will be released in a future version of the AGA

3.4.2 Business layer

The Business layer describes the relationship between a Business entity and:

• The AGA Business Reference Model
• The Service layer Service.

Figure 3.2: Business Layer
click on image to view larger size

Entity Name	BRM Business Area
Entity Description	Used to classify the government functionality and activities surrounding the operations of government.
Relationships	BRM Line of Business
Examples	1. Services for Citizens 2. Service Paths
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	BRM Line of Business
Entity Description	Used to classify various sectors of government including support services, service delivery paths and managing government resources
Relationships	BRM Business Area BRM Business Subfunction
Examples	1. Financial management 2. Health care 3. Credit and insurance
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	BRM Business Sub function
Entity Description	Used to breakdown the BRM Line of Business into smaller, more precise business functions.
Relationships	BRM Line of Business Business layer Business Process
Examples	1. Payments to citizens 2. Health Insurance schemes 3. Community health services
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	Business Initiative
Entity Description	A government initiative underpinned by legislation or any agency level initiative to attain measurable benefit. A government initiative is also known as a Program at the Australian Government level. A Business Initiative defines business requirements and has deliverables.
Relationships	Business layer Deliverable Business layer Business Requirement
Examples	1. Australian Childhood Immunisation Program 2. Aged Care Program
Attributes	Type	Description
Legislation	String	Any associated legislation tied to this initiative
Scheduled date	Date	Date initiative is or was expected to be available
Actual date	Date	Date initiative was actually made available

Entity Name	Deliverable
Entity Description	A product which forms the output of a Business Initiative.
Relationships	Business layer Business Initiative
Examples	1. Australian Childhood Immunisation Register 2. Online system for tracking immunisation for citizens
Attributes	Type	Description
Scheduled date	Date	Date deliverable is or was expected to be available
Actual date	Date	Date deliverable was actually made available
Is delivered	Boolean	Whether deliverable is currently available for use
Version number	String	Current version of the deliverable

Entity Name	Business Requirement
Entity Description	A Business Requirement details the Business Initiative to be delivered including the Business Processes required. A Business Requirement should be SMART (specific, measurable, attainable, relevant and time-bound). Business Requirements will be bound by any legislation that underpins the Business Initiative. There will usually be more than one Business Requirement to each Business Initiative.
Relationships	Business layer Business Process Business layer Business Initiative
Examples	1. "Australian childhood immunisation should maintain a register for each individual child to track what immunisation they have received so far and what they are scheduled to receive". 2. "All agencies should have IPv6 capable hardware and software platforms by 2012".6
Attributes	Type	Description
Requirement source	String	Legislation or other directive underpinning the requirement

Entity Name	Business Process
Entity Description	"A business process is a sequence of linked activities that creates value by turning inputs into a more valuable output. This value creation can be performed by human participants or information and communications technology (ICT), or both".7 A BRM Business Sub function can be decomposed into multiple Business Processes. A Business Process will implement a Business Requirement and will contain a series of work events that can be either manual or automated. There will usually be more than one Business Process to each Business Requirement.
Relationships	BRM Sub function Business layer Business Requirements Service layer Service
Examples	1. Registration for a program 2. Payment process for a program 3. Reporting process
Attributes	Type	Description
Process Id	String	Unique id to represent the process
Description	String	Description of high level steps of the business process
Process Owner	String	Agency formally charged with ownership of a common process

3.4.3 Service layer

The Service layer describes the relationship between a Service entity and:

• AGA Service Reference Models
• Business layer Business Process
• Technical layer Technology Standard.

Figure 3.3: Service Layer
click on image to view larger size

Entity Name	SRM Service Domain
Entity Description	Used to classify the services, capabilities and processes. Service Domains are comprised of SRM Service Types.
Relationships	SRM Service Type
Examples	1. Customer services 2. Back office services
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned

Entity Name	SRM Service Type
Entity Description	Used to breakdown the SRM Service Domain through providing the business context for a specific SRM Service Component.
Relationships	SRM Service Component Service layer Service
Examples	1. Customer relationship management 2. Data management 3. Tracking & workflow
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	SRM Service Component
Entity Description	Used to classify a self-contained Business Process or Service with predetermined functionality that is exposed through a business or technical interface.
Relationships	SRM Service Type Service layer Component
Examples	1. Online help 2. Change management 3. Content authoring 4. Case Management
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	Service
Entity Description	A Service consists of people, processes and systems and may be delivered by a single agency or by multiple agencies. A Service aligns with the SRM Service Type and may be implemented by multiple Components. A Service is an abstract resource that represents one or more Capabilities. A Capability presents a coherent functionality from the point of view of agencies
Relationships	SRM Service Type Service Layer Component
Examples	1. Medicare Customer management 2. Medicare Human resources division 3. Standard Business Reporting
Entity Source	BRM Line of Business or government initiative
Attributes	Type	Description
Service provider	String	Agency providing the service
Service level agreement	String	Description of service level agreement for the service

Entity Name	Component
Entity Description	Logical building blocks of a service. Aligns with the SRM Service Component.
Relationships	SRM Service Component Service Layer Service TRM Technology Standard
Examples	1. Forms for registration 2. Authentication 3. Customer search 4. Cheque printing 5. Electronic Funds Transfer 6. Smart forms.
Entity Source	BRM Line of Business or government initiative
Attributes	Type	Description
Agency service register identification attributes can be used here if required.

3.4.4 Technical layer

The Technical Layer describes the relationship between the technical entities and:

• the AGA Technical Reference Model (TRM)
• the Service layer Component.

Figure 3.4: Technical Layer
click on image to view larger size

Entity Name	TRM Service Area
Entity Description	Used to classify the technology and standards that support the construction, exchange and delivery of Service Layer Components. The TRM Service Area may consist of multiple TRM Service Categories.
Relationships	TRM Service Category
Examples	1. Component framework 2. Service interface and integration
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	TRM Service Category
Entity Description	Used to classify lower level technologies and standards by the business or technology function they serve. A TRM Service Category will contain TRM Service Standards.
Relationships	TRM Service Standard
Examples	1. Security 2. Database/storage 3. Access channels
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	TRM Service Standard
Entity Description	Used to define the technologies and standards supporting a TRM Service Category.
Relationships	TRM Service Category Technical layer Technology Standard
Examples	1. Web server 2. Web browser 3. Server 4. Computer
Entity Source	AGA Reference Models
Attributes	Type	Description
Code	String	Unique identity code assigned to this instance in the AGA Reference Models

Entity Name	Technology Standard
Entity Description	Used to define the technologies, standards and specifications used by agencies in implementing a Service Layer Component. A Technical Standard aligns to the TRM Service Standard.
Relationships	TRM Service Standard Service layer Component
Examples	1. AGIMO policies and frameworks 2. international and Australian industry standards 3. browser technology 4. languages 5. document standards
Entity Source	AGA Reference Models
Attributes	Type	Description
Asset / Licence / Standard ID	String	Uniquely identifies the hardware equipment / software licence identifier / identifier (ID) of a particular Standard issued by a recognised standards body.

3.4.5 Data layer

This section is still being developed, and will be released in a future version of the AGA.

---

5. Please note the diagram is published in A3 for better readability
6. http://www.finance.gov.au/e-government/infrastructure/docs/Endorsed_Strategy_for_the_Transition_to_IPv6_for_Australian_Government_agencies.pdf
7. Defined by The Australian Government Business Process Interoperability Framework

---

Previous Page - Next Page

Contact for information on this page: AGA@finance.gov.au

---

Back to top