EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-4
Task 2.2: Identify the Characteristics of Your Objects
Task 2.2: Identify the Characteristics of Your Objects
1. Define the names of each of your objects.
Every object must be addressable within the network; that is, the object must have
a name. A name is necessary because the object must be accessible separately
from other objects in the subsystem. Both program and human interfaces should
be able to determine the existence and name of any object. For requirements and
possible name formats, see Underlying Philosophy of Standard Events on
page 9-10.
2. Define the possible states of each of your objects.
The behavior of an object can be completely represented by its states and the
transition between these states.
a. Define the states that describe the normal behavior of each object.
Every object undergoes a set of states that defines the way it normally
behaves and carries out its functions. The nature of these states is defined by
the object. For example:

Up, down, and suspended are states usually associated with the behavior
of a terminal

Disconnected, connecting, connected, disconnecting, restart, reset, and so
on are states usually associated with a network connection
b. Define states that describe system conditions which cause your object to be in
a state—other than available and unavailable—that:

Could persist for a long time so an operator should take notice

Needs operator action to change

Transient faults could be detected in

Could let usage levels of the object severely degrade subsystem
performance
For example, if your object is a network connection that could take longer than
expected to connect, define a new state in addition to the connecting state to
indicate this condition. Section 9, Standard Events lists the set of conditions to
consider to make your objects more manageable.
3. Determine the management data needed to manage your objects.
Design management data to use the asynchronous management interfaces and
the command and control interfaces.
Task 2.3: Identify the State Transitions of Your Objects
A state transition diagram defines the behavior of an object. To construct the diagram: