×
Menu
Index

OV-6c: Operational Event-Trace Description

 
The steps below walk the user through populating data in Collector for an OV-6c: Operational Event-Trace Description sequence diagram. This how-to topic presumes a novice-level knowledge of Architex and the Collector module. These steps can be completed by a user with write access to the module and architecture.
 
An OV-6c describes a time-ordered (or sequential) scenario or situation. It can be used in conjunction with an OV-6b: State Transition Description to expand further upon an initial operational concept.
 
It may be helpful to sketch out the overall scenario or sequence (on a whiteboard or paper) before entering data into Collector.
Nodes and elements that should be populated at the end of this process:
Node
Element
Views Also Used In
Operational Event Trace
Name
 
Node
Name
OV-2, OV-3, OV-5b
Operational Message
Name
 
Operational Exchange Item
Name
OV-2, OV-3
Operational Exchange
Operational Exchange Item
Operational Event Trace
Case (optional)
Sequence
Source Node
Target Node
Operational Message
OV-2, OV-3
 
(Screenshots are from the SAR EA Example architecture, provided with most data services.)
1. Load the desired architecture (based on the UPDM 2.1 Framework) in Collector.
 
2. To capture the scenario name, select the Operational Event Trace node in the Outlook Bar. Enter the name of the scenario in the Name element. (If the node is empty, click the Add button in the Ribbon Bar.)
 
3. Next, we need to document the scenario performers. These performers can be organizations, units, groups, roles, or posts, and are captured in the Node node, a general repository for all task performers. Select that node now. Add any new performers to the Name element.
 
4. The messages that are sent from one node to another are captured in the Operational Message node. Select it, and add any new messages to the Name element.
 
5. The items exchanged at each step are identified in the Operational Exchange Item node. Select it, and add any new items to the Name element.
 
6. All of these elements come together in the Operational Exchange node. It may be easier to define the steps first in Excel, and then either paste into the table or select from the drop-down menus in Collector.)
6a. Select the scenario name in the Operational Event Trace element. You will need to use this name for every step in the sequence.
 
6b. Type in the sequence number for each step in the Sequence element. (NOTE: If you leave this node and later return to it, your sequence numbers may not be displayed in sequential order, as shown in the screenshot.)
 
6c. For each step, select the start and end nodes in the Source Node and Target Node elements, respectively. The start and end point can be the same node.
 
6d. In the Operational Message element, select the message that is passed between the two nodes.
 
6e. Finally, select the item exchanged during the step in the Operational Exchange Item element.
 
7. In the Reporter module, select a previously designed OV-6c report and generate it. If the resulting flow is not correct, then return to Collector and make any necessary changes.
© 2019 Exostrategies, Inc.