They may either be provided as structured
English text and graphical UML diagrams or
by means of the formal language Z [Zintro].
[G.853.1] is a library of information elements
directly defined on the basis of the network
resource types in [G.852.2]. Information ele-
ments for specific management areas are pro-
duced using these as superclasses and defining
specializations with new requirements and ele-
ments.
By convention, new elements are provided with
the community prefix, in the example case,
iptom. Elements defined in [G.853.1] are either
left unprefixed or prefixed G.853.1. The Infor-
mation Viewpoint concepts are illustrated in
Figure 9.
The CPG role has no direct counterpart in
[G.853.1], so a new information object class,
iptomCTPG has been defined.
The relationships are provided with the relation-
ship name, the role names and the role cardinal-
ity. The arrows in Figure 9 point to the informa-
tion objects playing the various relationship
roles.
The Information Viewpoint is the ultimate
source for the definition of information elements
within the system. This is reflected by the
Parameter Matching clause in the Computational
Viewpoint which maps the input and output
parameters to the corresponding information
elements.
The syntax applied when defining elements in
the Information Viewpoint is illustrated by
examples in the following sub-sections.
3.2.2.1 Information Object: Topological Link
(example)
This information type is related to the following
enterprise entity:
Figure 8 Enterprise Viewpoint
- concepts
trail
role
LND
role
SN
role
TL
role
CPG
role
iptom_Caller
role
iptom_Provider
role
manipulate*NR**
ACTIONS with
policies
ACTIVITIES with policies
Community
Policy
Service
Contract
Network Resource (NR) roles
*: manipulate, i.e.,
- create, or
- delete, or
- modify, or
- associate, or
- dis-associate
**: NR (Network Resource), i.e.,
- layerNetworkDomain (LND), or
- subnetwork (SN), or
- topological link (TL), or
- connection point group (CPG), or
- trail
COMMUNITY iptom IP topology management
Community:A composition of Enterprise Objects formed to meet an objective.
Role:Part of the behavior of an Enterprise Object.
Policy:An Obligation, Permission, or Prohibition on an Action,
an Activity or the Community as a whole.
Service Contract:A consistent sub-set of the functionality of an imported community.: