Australian Government Architecture Reference Models Version 3.0

architect should plan to provide these services for the transactional, authoring and document repository
quadrants.
� Notification Services: automatically alerts another service or an end user of changes to the content of a
repository in accordance with a predetermined policy or profile. The architect should plan to provide
these services for the transactional, authoring and document repository quadrants.
7.8.2 Guidance
As stated in the Overview, once the Data Context and the Data Description standardisation areas for a COI have
been defined, the COI should then plan and implement common capabilities to enable information to be
accessed and exchanged.
Enterprise architects and data architects supporting COIs may use the following table as a guide to plan
implementation of data exchange and access services for each data asset under management within the COI.
Data Sharing Service Requirements Matrix Table
Supplier Service Requirement Consumer
Data Asset Identifier (see
abstract model below)
Data Exchange Service Type
(e.g. Extract, Transform, Load)
―(populate as needed) ― ―
Data Asset Identifier Access Service Type (e.g.
Context Awareness)
―(populate as needed) ― ―
Data Asset Identifier
Access Services typically support many
consumers. Generally, there is no need
to populate these cells.
Once the architect has populated this matrix, he or she has a clear understanding of the types of data access
and exchange services that they should provide to support a COI’s information sharing requirements. Once these
requirements are captured, the architect may use the Data Sharing section of the DRM abstract model to fully
document the data access and the exchange services required to support the COI.
7.8.3 Data Sharing Section of the DRM Abstract Model
The Data Sharing section of the DRM abstract model covers two primary aspects of data sharing:
� Data Exchange: fixed, recurring transactions between parties, such as the regular exchange of
environmental testing data among federal, state and local entities. These exchanges, as described
above, are implemented with data exchange services.
� Data Access: requests for data services, such as a query of a Data Asset 35. These requests, as
described above, are supported by Data Access Services.
The Data Sharing standardisation area is supported by the Data Description and Data Context standardisation
areas in the following ways:
� Data Description: uniform definition of Exchange Packages and Query Points supports the capability to
effectively share them within and between COIs.
� Data Context: categorisation of Exchange Packages and Query Points supports their discovery and
their subsequent use in data access and data exchange.
35 The term ‘data asset’ is synonymous with ‘data source’. It is described within the Data Context section.
Australian Government Architecture Reference Models Version 3.0
225