A State Model formalizes the behavior of each active object on the Information Model. Passive objects, those with no behavior, are not modeled. An object's State Model shows the different stages an object can be in during its lifecycle and the events that cause it to change from one stage, or state, to another. The analyst is responsible for figuring out the behavior of individual objects and synchronizing that behavior with all other active objects in the system. The State Models produced using this methodology are inherently concurrent.
Ada designers appreciate that their tasking model is reflected in the analysis.
Very little, if any, additional tasking design must be done. Following this analysis phase, the team will deliver any modifications to the prior phase, a State Model for each active object, and event lists for each active object detailing event sources, destinations, and associated data. In theory, now is the time to consider topics such as programming languages, support libraries, reusable component libraries, and the target platform. In practice, most teams understand much about those items earlier in the process. One should not allow such knowledge to interfere with the analysis.