Page History

...

Behavioral Models

In the context of this paper, behavioral dynamic models capture the behavior of services. the SI 2.0 Roadmap -- and in compliance with the CBIIT implementation of the SAIF Behavior Framework with defines behavior as ""A collection of interactions with a set of constraints on when they can occur in a given Working Interoperability/business process context", the "behavioral models" that will be managed by the SI 2.0 collectively specify the behavioral semantics of services at the <<interface>> and <<not>> at the <<implementation>> level.  Behavior of services provides an unambiguous definition of the service constraints, capabilities, dependencies and interactions. The metadata and grammar required to realize service behavior is called behavioral semantics. Behavioral semantics provide a mechanism for better service discovery and enforcing the constraints at design and runtime.

Dynamic models include but are not limited to:

...

model semantics -- as defined in a CBIIT-defined but SAIF-compliant behavioral meta-model -- will collectively define the behavioral meta-data -- using a number of technologies still being explored including UML profiles, OWL, RDP, and Rules Engines (e.g. Jess) -- the meta-data necessary to support automated (or at least semi-automated) work flow composition using as-yet-unspecified user-friendly tools to provide various contextual inputs for a given work flow including known pre- or post-conditions, input data sources, desired data operations, etc.

Content

Content includes all unstructured text and other forms of content that make up a service specification. Examples include storyboards and scope. Content is an integral part of service specification, and content is leveraged across the enterprise for documentation and communications. Content includes:

...