Australian Government Architecture Reference Models Version 3.0

More documents

Recommendations

Info

298 Term Definition SQL-92 [top] SQL is a database sublanguage that is used for accessing relational databases. The proper pronunciation is ‘ess cue ell’, and not ‘sequel’ as is commonly heard. SQL-92 was designed to be a standard for relational database management systems (RDBMSs) developed by the ANSI X3H2 committee. SQL-92 does not address objects in any way. Nevertheless, SQL- 92 forms the basis for JDBC and other specifications. Depending on the source, ‘SQL’ stands for SQL Query Language (recursive expansion) or Structured Query Language. SRM [top] See Service Reference Model. Standardisation Area [top] The three aspects of data that the DRM addresses, namely Data Description, Data Context and Data Sharing. The DRM’s standardisation areas provide a foundation for agency data architecture initiatives to put forth requirements that can result in increased compatibility between agency data architectures. (DRM usage) Structured Data Object [top] Structured Data (Resource) [top] Australian Government Architecture Reference Models Version 3.0 An entity within a data store. These entities, in turn, contain attributes that describe the object. Such objects rely on the structure and relationships defined in the data store to assign their meaning. Databases are examples of collections of structured data objects. (DRM usage) Data described via the E-R (Entity-Relationship) or class model, such as logical data models and XML documents. Structured data is organised in well-defined semantic ‘chunks’ called entities. (DRM usage) Subject Area [top] A topic of interest shared within a community. The full list of subject areas of interest to a community form the context for that community. A super type is a subject area that spans multiple COIs. (DRM usage) Supplier [top] An entity (person or organisation) that supplies data to a Consumer. Note that the Supplier may or may not be the original producer of the data. For this reason the name ‘Producer’ was not used. (DRM usage) Synonym [top] A word or term having exactly or very nearly the same meaning as another word or term. (ANSI/NISO Z39.19-200x) Synonym Ring [top] A group of terms that are considered equivalent for the purposes of retrieval. (ANSI/NISO Z39.19-200x) Target Architecture [top] The set of products that portrays the future or end-state enterprise, generally captured in the organisation’s strategic thinking and plans; commonly referred to as the ‘To-Be’ architecture. Taxonomy [top] A collection of controlled vocabulary terms organised into a hierarchical structure. Each term in a taxonomy is in one or more parent/child (broader/narrower) relationships to other terms in the taxonomy. There can be different types of parent/child relationships in a taxonomy (e.g. whole/part, genus/species, type/instance), but good practice limits all parent-child relationships to a single parent to be of the same type. Some taxonomies allow poly-hierarchy, which means that a term can have multiple parents and, although the term appears in multiple places, it is the same term. If the parent term has children in one place in a taxonomy, then it has the same children in every other place where it appears. (ANSI/NISO Z39.19-200x)
Term Definition Technical Reference Model (TRM) [top] A component-driven, technical framework used to categorise the standards, specifications and technologies that support and enable the delivery of service components and capabilities. The TRM provides a foundation to categorise the standards, specifications and technologies to support the construction, delivery and exchange of business and application components (Service Components) that may be used and leveraged in a Component-Based or Service-Oriented Architecture. The TRM unifies existing Agency TRMs and E-Gov guidance by providing a foundation to advance the re-use of technology and component services from a government-wide perspective. Service areas include: Service Access and Delivery, Service Platform and Infrastructure, Component Framework, and Service Interface and Integration (http://www.finance.gov.au/egovernment/index.html). Term [top] One or more words designating a concept. (ANSI/NISO Z39.19-200x) Term Record A collection of information associated with a term in a controlled vocabulary, including the history of the term, its relationships to other terms and, optionally, authorities for the term. (ANSI/NISO Z39.19-200x) Thesaurus [top] A networked collection of controlled vocabulary terms. A thesaurus uses equivalence (synonym), hierarchical (broader/narrower) and associative relationships. The expressiveness of the associative relationships in a thesaurus varies and can be as simple as ‘related to term’, as in ‘term A is related to term B’. (ANSI/NISO Z39.19-200x) Topic [top] A category within a Taxonomy. A Topic is the central concept for applying context to data. For example, an agency may have a Taxonomy that represents its organisational structure. In such a Taxonomy, each role in the organisational structure (e.g. CIO) represents a Topic. Topic is often synonymous with Node. (DRM usage) Top Term [top] The broadest term in a controlled vocabulary hierarchy. (ANSI/NISO Z39.19- 200x) Transaction [top] An exchange of information between two or more services (or an entity and a service) in the performance of an operation or function. (DRM usage) Transactional Database [top] A database that support transactions. A database transaction is a unit of interaction with a database management or similar system that is treated in a coherent and reliable way independent of other transactions that must be either entirely completed or aborted. Tree Structure [top] A controlled vocabulary display format in which the complete hierarchy of terms is shown. Each term is assigned a tree number or line number which leads from the alphabetical display to the hierarchical one; the latter is also known as systematic display or classified display. (ANSI/NISO Z39.19-200x) TRM [top] See Technical Reference Model. Unified Modeling Language (UML) [top] A non-proprietary, object modelling and specification language. As a graphical notation, UML can be used for modelling hardware (engineering systems) and is commonly used for business process modelling, systems engineering modelling, software engineering and representing organisational structure. UML was designed to be used to specify, visualise, construct and document Australian Government Architecture Reference Models Version 3.0 299
Page 3 and 4:
Copyright Notice This work is copyr
Page 5 and 6:
This page is intentionally blank Au
Page 7 and 8:
6 Service Reference Model .........
Page 9 and 10:
Figure 4-26: Tasks measurement bran
Page 11 and 12:
Page 13 and 14:
1.1 Audience This document is targe
Page 15 and 16:
systems and process frameworks, suc
Page 17 and 18:
At an agency level, these business
Page 19 and 20:
� bridging data architectures. Th
Page 21 and 22:
Page 23 and 24:
LAYER DESCRIPTION Service Describes
Page 25 and 26:
3.4 Metamodel elements by layer 3.4
Page 27 and 28:
Attributes Type Description Code St
Page 29 and 30:
3.4.3 Service layer The Service lay
Page 31 and 32:
Entity Name Service Entity Descript
Page 33 and 34:
Entity Name TRM Service Area Entity
Page 35 and 36:
Page 37 and 38:
Figure 4-1: The PRM Classification
Page 39 and 40:
Figure 4-2: Linking the PRM to the
Page 41 and 42:
Figure 4-5: Combining the TRM and t
Page 43 and 44:
4.1.4.2 The Outcome Process Model F
Page 45 and 46:
The PRM is structured in a way that
Page 47 and 48:
4.1.4.5 Other References Australian
Page 49 and 50:
The PRM is able to: � support pla
Page 51 and 52:
4.1.5.3 Indirect Benefits The indir
Page 53 and 54:
Level 4 Measurement groupings Level
Page 55 and 56:
4.3.1 Program outcomes The followin
Page 57 and 58:
Subtype Measures of effects that in
Page 59 and 60:
Measurement Area Measures of effect
Page 61 and 62:
4.4.1 Product consumption 2101 Time
Page 63 and 64:
4.4.2 Service delivery 2201 Availab
Page 65 and 66:
Measurement Area Rationale Defined
Page 67 and 68:
3 OUTPUTS 31 Products 32 Services 3
Page 69 and 70:
Page 71 and 72:
4.6 Work domain ‘Work’ is the g
Page 73 and 74:
Page 75 and 76:
4.6.2 Ad hoc tasks 4201 Task effici
Page 77 and 78:
Understanding the performance relat
Page 79 and 80:
[4305] Process Reliability [4306] P
Page 81 and 82:
4.7 Inputs domain It could be argue
Page 83 and 84:
Page 85 and 86:
4.7.2 Data and information In the i
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
4.7.5 Money 55 Money 5501 Costs (mo
Page 97 and 98:
First order Second order Higher ord
Page 99 and 100:
Measurement Indicator Rationale Cur
Page 101 and 102:
4.9.2 Example 2: OPM used in operat
Page 103 and 104:
Page 105 and 106:
BRM Business Area 1 Contains lines
Page 107 and 108:
[109] Employment [10901] Human Reso
Page 109 and 110:
5.3 Services for Citizens Business
Page 111 and 112:
Business Sub Function Defines the s
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
5.3.9 [109] Employment A Employment
Page 123 and 124:
Page 125 and 126:
5.3.12 [1012] Immigration A Immigra
Page 127 and 128:
5.3.14 [1014] International Relatio
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
5.3.17 [1017] Natural Resources A N
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
5.3.24 [1024] Trade A Trade involve
Page 143 and 144:
Page 145 and 146:
5.4.1 [201] Credit and Insurance F
Page 147 and 148:
Page 149 and 150:
5.5 Services Support Business Area
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
5.6.1 [401] Administrative Manageme
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Example 1: Financial Assistance to
Page 165 and 166:
6 Service Reference Model 6.1 Intro
Page 167 and 168:
6.3 Customer Services Domain The Cu
Page 169 and 170:
6.3.2 [1002] Customer Preferences C
Page 171 and 172:
6.4.2 [1102] Routing and Scheduling
Page 173 and 174:
6.5.1 [1201] Management of Process
Page 175 and 176:
6.5.4 [1204] Supply Chain Managemen
Page 177 and 178:
6.6.2 [1302] Document Management Ca
Page 179 and 180:
6.7 Business Analytical Services Do
Page 181 and 182:
6.7.3 [1403] Knowledge Discovery Ca
Page 183 and 184:
6.8.1 [1501] Data Management Capabi
Page 185 and 186:
6.8.4 [1504] Assets/Materials Manag
Page 187 and 188:
6.9 Support Services Domain The Sup
Page 189 and 190:
6.9.2 [1602] Collaboration Capabili
Page 191 and 192:
6.9.6 [1606] Forms Management Capab
Page 193 and 194:
7 Data Reference Model 7.1 Introduc
Page 195 and 196:
7.4 DRM Implementation Framework Th
Page 197 and 198:
Standardisation Area Description Da
Page 199 and 200:
The DRM abstract model is an archit
Page 201 and 202:
7.7 Data Context Standardisation Ar
Page 203 and 204:
7.7.2 Guidance 7.7.2.1 The COI, its
Page 205 and 206:
� Though cardinality is not expre
Page 207 and 208:
Term Definition Other AGA Reference
Page 209 and 210:
Figure 7-8: US DOI DRM Classificati
Page 211 and 212:
section, as well as through the cat
Page 213 and 214:
The following are definitions for e
Page 215 and 216:
Term Definition Document (human rea
Page 217 and 218:
Concept Attribute Description Examp
Page 219 and 220:
Page 221 and 222:
Figure 7-13: US FEA BRM Logical Dat
Page 223 and 224:
While it may have been physical evi
Page 225 and 226:
Based upon this analysis, the archi
Page 227 and 228:
architect should plan to provide th
Page 229 and 230:
Term Definition Exchange Package An
Page 231 and 232:
7.9 DRM Abstract Model This section
Page 233 and 234:
The table below summarises each of
Page 235 and 236:
Term Definition Digital Data Resour
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
The following are definitions for e
Page 243 and 244:
The table below provides attributes
Page 245 and 246:
Supplier A Supplier is an entity (p
Page 247 and 248:
Page 249 and 250: 8.2 Structure Organised in a hierar
Page 251 and 252: 8.3.1 [3001] Access Channels Access
Page 253 and 254: 8.3.2 [3002] Delivery Channels Deli
Page 255 and 256: Service Standards Defined by Exampl
Page 257 and 258: Service Standards Defined by Exampl
Page 259 and 260: 8.4 Service Platform and Infrastruc
Page 261 and 262: 8.4.2 [3102] Delivery Servers Deliv
Page 263 and 264: Service Standards Defines Examples
Page 265 and 266: 8.4.5 [3105] Hardware/Infrastructur
Page 269 and 270: 8.5 Component Framework Service Are
Page 273 and 274: 8.5.3 [3203] Business Logic Busines
Page 275 and 276: 8.5.5 [3205] Data Management Data m
Page 277 and 278: 8.6 Service Interface and Integrati
Page 281 and 282: 8.6.3 [3303] Interface Interface de
Page 283 and 284: Term Definition Australian Governme
Page 285 and 286: Term Definition Business Service [t
Page 287 and 288: Term Definition Context [top] As re
Page 289 and 290: Term Definition Data Element Regist
Page 291 and 292: Term Definition Digital Rights Mana
Page 293 and 294: Term Definition Exchange Package [t
Page 295 and 296: Term Definition Management Context
Page 297 and 298: Term Definition Preferred Term [top
Page 299: Term Definition Semantic Web [top]
Page 303 and 304: Term Definition eXtensible Markup L
show all

Australian Government Architecture Reference Models Version 3.0

Create successful ePaper yourself

Delete template?

Save as template?