The State Modeler is a UML-compliant application that allows you to model the life cycle of an instance — that is, for each instance of a given concept, you can define which states it will pass through and how it will transition from state to state based on rules that apply.Each state model begins with a start state and ends with one or more end states. Between the start and end states may be simple, composite, and concurrent states connected by transitions. Figure 9 displays a simple state model that classifies orders based on their dollar values:Figure 9 Simple State ModelFor a slightly more complex example, consider another Order concept. When a customer places an order, BusinessEvents receives a simple event and creates a new instance of the Order concept. Through the life of the Order instance, it will pass through a credit-check state, an inventory-check state, a fulfillment state, and so on until the customer has received and paid for the order. As these order activities happen in the real world, BusinessEvents receives new events, correlates the events to the existing instance, modifies one or more values within the instance, and changes the state of the instance. Figure 10 illustrates this order process:Figure 10 Modeling an Order ProcessBusinessEvents ships with a simple state model example, which you can open and examine. It also includes a document with instructions for creating the example yourself. This will help to familiarize you with the BusinessEvents State Modeler. This and other examples are stored in the BE_HOME/examples directory.At runtime, the transitions are used in the rule session as state machine rules, and the concept states are stored as properties of the concept.
Copyright © TIBCO Software Inc. All Rights Reserved.