Australian Government Architecture Reference Models Version 3.0

58
4.4 Usage domain
Usage is the mechanism by which the outputs produced by a business initiative realise the outcomes of the
initiative. Without some form of usage by a customer, the outputs of government programs, projects and
processes will be unable to realise any form of benefit for an agency.
Some projects and processes are quite large and produce intermediate outputs that are consumed in the
delivery of a much larger output. While the intermediate outputs have value, they are not measured within the
Usage domain because they are not intended to realise an outcome in their own right. Only those outputs that
are intended to directly contribute to the realisation of an outcome are measured within the Usage domain.
Australian Government Architecture Reference Models Version 3.0
2 USAGE
21 Product consumption 22 Service delivery
2101 Timeliness (product)
A - delivery
2102 Accessibility (product)
A – Access cost
B – Access time
C – Access effort
2103 Consumption (product)
A – Cost
B – Supply
C - Demand
2104 Coverage (product)
A - Geographic
2105 Effectiveness (product)
A – Customer impact
B – customer satisfaction
C – Product quality
2201 Availability (service)
A – Service capacity
B – Service utilisation
C – Service demand
2202 Coverage (service)
A – Demographic
B – Geographic
C - Temporal
2203 Effectiveness (service)
A – Customer impact
B – Customer satisfaction
C – Service quality
2204 Accessibility (service)
A – Access cost
B – Access time
C – Access effort
2205 Timeliness and responsiveness (service)
A – Inquiries and requests
B - Delivery
Figure 4-17: Usage domain
The requirements that specify the composition and function of the outputs of a project, process or program may
include specifications of performance-related characteristics for the output, known as ‘non-functional
requirements’. While those requirements can be partially measured as an attribute of the output within the
Outputs domain, it is only by measuring the actual performance of the output within the Usage domain that a
requirement can be assessed as being met or not. Furthermore, any requirements that have a dimension of
operation and time, such as hours of availability for a service, can only be measured within the Usage domain.
Some forms of usage, which may or may not be measurable, are:
� the one-off consumption of a product
� the sustained usage of infrastructure
� the accessing of a service or information
� acknowledgment of an accomplishment (binary state in the customer)
� adjustment of behaviour.