Summary of Development Stages

This section lists the stages of the process model development methodology:

  • Table 81 Stage 1: Context Definition
  • Table 82 Stage 2: Process-Level Decomposition
  • Table 83 Stage 3: Enumeration of Events (per Process)
  • Table 84 Stage 4: State-Level Decomposition (per Process)
  • Table 85 Stage 5: STD Development (per Process)
  • Table 86 Stage 6: Specification of Process Actions (per Process)
  • Table 87 Stage 7: Initial State Designation (per Process)

Table 81: Stage 1: Context Definition

Step 1: Identify interdependent modules The modules with which the system communicates or shares information are determined and named.
Step 2: Select communication mechanisms with interdependent modules For each module identified in previous step, the nature of the dependency is examined and an appropriate communication mechanism is chosen.
Step 3: Develop diagram of system and interdependent modules The interdependent modules and the system of interest are placed in a diagram together with paths representing their interfaces. The interfaces are assigned names.

Table 82: Stage 2: Process-Level Decomposition

Step 1: Determine which process decomposition technique is applicable to the system The activities of the system are analyzed to determine appropriate ways of separating them into simpler sets of actions. Single processes may be used to represent an entire subsystem, or three other methods may be used: (1) dynamic creation of a variable number of processes; (2) cooperating, asynchronous processes; (3) hierarchical organization to spread complexity over multiple levels. These techniques may also be combined.
Step 2: If a multi-process implementation is chosen, identify the areas of responsibility assigned to each process Specific areas of the system’s activity that are assigned to each process are identified. Representative process names are assigned.
Step 3: For multi-process implementations, determine circumstances of process creation and which will be root A root process is selected among those defined earlier, based on property of permanent existence and role as event dispatcher. Conditions under which other processes are created are specified.

Table 83: Stage 3: Enumeration of Events (per Process)

Step 1: Define logical events of each process The activities of the system and the particular role of the process within the system, as well as interactions with other processes and modules are analyzed to determine the circumstances that require the process to be invoked. The occurrence of each such circumstance is given a name and classified as a logical event.
Step 2: Select event implementation methods For each logical event identified in the previous step, an appropriate event type is selected based on the source of the logical event and the type of data that is associated with it.

Table 84: Stage 4: State-Level Decomposition (per Process)

Step 1: Select states of the process Identify high-level modes of the process and assign names to them. These are the states of the process.
Step 2: Verify that the selected set of states match criteria States should respect the following:
- a state corresponds to particular sequences of events having occurred
- events are handled in a specific manner as a result of being located in a particular state
- selected states are mutually exclusive and complementary
- each state should represent a blocking point for the process

Table 85: Stage 5: STD Development (per Process)

Step 1: Determine feasible events of each state Each logical event defined in stage 3 is mapped against each state defined in stage 4; each state-event pair is categorized as infeasible, suppressed, or feasible. Feasible events are those that are expected to occur when the process is in the state of interest.
Step 2: Construct event-response table The process’ response to each feasible state-event pair is described in the form of a table; each row of the table specifies a state-event combination, an additional condition, and an action and state change that are performed if the condition is met.
Step 3: Define transitions Transitions are designed by combining conditions and events that allow transfer of control between the same pairs of states.
Step 4: Assemble STD The states defined in stage 4 are graphically placed in the Process Editor; transitions are created to link the states, and conditions are assigned according to the results of step 3.

Table 86: Stage 6: Specification of Process Actions (per Process)

Step 1: Review specification of the process’ logical actions for completeness The event-response table is revisited to ensure that the logical action specifications are complete.
Step 2: Place abstract specification of the logical actions within the STD Pseudo-code or macro statements representing these logical actions are placed within the STD. State enter and exit executives, and transition executives are used depending on basic rules:
- exit executives contain actions common to all outgoing transitions;
- enter executives contain actions common to all incoming transitions;
- transition executives contain actions associated subsets of outgoing/incoming transitions.
Step 3: Specify event suppression statements Macro statements are placed in each state’s enter executives to disable events classified as “suppressed” in stage 5. Statements are placed in each state’s exit executives to enable all events.
Step 4: Define or replace macros and pseudo-code Each macro or pseudo-code statement developed in stage 3 is replaced by or defined to be a series of executable statements, using general C language constructs and Kernel Procedures.

Table 87: Stage 7: Initial State Designation (per Process)

Step 1: Select initial state An initial state is selected based on the assumption that the process will be invoked once specifically for initialization purposes. A new forced state is created to act as initial state if one-time only initialization actions are required; otherwise one of the existing unforced states is selected as initial state based on the correct “default” or initial mode of the process.