This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SAIF Behavioral Framework"
Jump to navigation
Jump to search
m |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
'''SAIF Behavioral Framework ''' | '''SAIF Behavioral Framework ''' | ||
[[SAIF_main_page | Back to SAIF main page]] | [[SAIF_main_page | Back to SAIF main page]] | ||
| − | The Behavioral Framework (BF) provides a set of constructs for defining the behavioral semantics of specifications, which enableWorking Interoperability. As a result, the focus of the BF is accountability – a description of “who does what when.” Accountability describes the perspective of the various technology components that are involved in a particular instance or scenario designed to achieve Working Interoperability. The BF is technology-neutral and, therefore, can be used within model-driven | + | The Behavioral Framework (BF) provides a set of constructs for defining the behavioral semantics of specifications, which enableWorking Interoperability. As a result, the focus of the BF is accountability – a description of “who does what when.” [[Accountability-SAIF | Accountability]] describes the perspective of the various technology components that are involved in a particular instance or scenario designed to achieve [[Working Interoperability (WI)-SAIF | Working Interoperability (WI)]]. The BF is technology-neutral and, therefore, can be used within model-driven [[Specification stack-SAIF | Specification stack]]s, such as the [[SAIF_main_page | Services-Aware Interoperability Framework (SAIF)]] [[SAIF_ECCF | Enterprise Conformance and Compliance Framework ( ECCF)]]. |
| − | [[Category: | + | |
| + | [[Category:SAIF Glossary]] | ||
[[User:ajulian | Tony Julian]] | [[User:ajulian | Tony Julian]] | ||
Latest revision as of 15:41, 21 April 2011
SAIF Behavioral Framework
The Behavioral Framework (BF) provides a set of constructs for defining the behavioral semantics of specifications, which enableWorking Interoperability. As a result, the focus of the BF is accountability – a description of “who does what when.” Accountability describes the perspective of the various technology components that are involved in a particular instance or scenario designed to achieve Working Interoperability (WI). The BF is technology-neutral and, therefore, can be used within model-driven Specification stacks, such as the Services-Aware Interoperability Framework (SAIF) Enterprise Conformance and Compliance Framework ( ECCF).
