|
Trac-Car Business
Models
The
Trac-Car UML Business Models provide an architecture
framework for a head
start on delivery of integration of applications, connected with
existing
technology.
The
Customer Interaction Domain describes the processes involved in the
commercial interaction between buyer, the customer and the selling
organisation.
It
describes the contact channels, the identification of the customer,
products sold and delivered, and the billing process.
Customer
The
Customer Domain Model represents the customer.
The
system collects customer profile information that enables
identification. Customer identity is a key aspect.
The
customer profile attributes are modelled as classes, as their may be a
one-to-many relationship between the customer and the
attribute.
For example, the customer may have more than one address, drivers
licence. An effectivedatetime is to be recorded at the time
of
collection of the information. This comprises a start dart, and if
applicable, an end date.
Contact
The
Contact Domain Model represents the information and functions entailed
in the processing of customer requests for Call Centre
products.
The
capability to parse the incoming requests to a queue structure, and to
assign operators to those queues through workflow role definition.
The
request processing begins with a customer contact from three main
channels
- Web
requests
-
Email/fax/post requests
-
Telephone requests
Customer
contacts are parsed as requests, and the contents of the request
determine the appropriate request queue.
Identity
The
Identity Domain Model provides the Identity of a Party. A
Party
is generally identified once, and for subsequent verifications,
authentication mechanisms can be applied, e.g. security tokens, userid
and password.
Identity
can beapplied to all stakeholders accessing internal or
external
systems. The parties may be customers, authorities, staff and
consultants.
|
Billing
The
Billing Domain Model describes the capability to make charges
for
products and services, and to aggregate invoices to a customer
account.
Customer transactions are
comprised of billing items, that may be associated with a usage charge.
Products
The
Products Domain Model models the capability to allow marketing
personnel to update prices for products and product bundles on a
campaign basis.
It provides
the basis for marketing products
and services is an offer to customers. The products capability is to
provide self-service for marketing.
Organisation
The
Organisation Domain Model describes the physical locations for a
business, and the people and the organisation of roles involved in the
enterprise, including people, job and business roles, and
workgroups.
It also
describes the contact details for organisation personnel.
Assets
The
Asset Domain Model describes the management and maintenance of physical
assets, such as plant and equipment, asset identification by means of
asset tags, and recording information about the state of the assets.
Routine
and ad hoc maintenance of equipment is managed by maintenance schedules
for maintenance crews, linked to specific work requests.
Geospatial
The
Geospatial Domain Model describes the mapping of objects related to a
particular theme. A theme, e.g. electricity substations, is
represented by a Layer. The layer may contain a number of
features that are represented graphically on a map at a particular
latitude and longitude.
Vehicles
The
Vehicles Domain Model describes the management of vehicles, drivers,
rosters, and the recording of vehicle journeys from GPS observations.
Reporting
The
Reporting Domain Model describes the data sources that provide input
into the report, and the parameter name value pairs engaged in the
filtering of reporting data and content.
|
|
