This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "SAIF Behavioral Framework"

From HL7Wiki
Jump to navigation Jump to search
m
m
Line 3: Line 3:
 
'''SAIF Behavioral Framework '''
 
'''SAIF Behavioral Framework '''
  
Enterprise Conformance and Compliance Framework
+
[[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 specification stacks, such as the Services-Aware Interoperability Framework (SAIF) Enterprise Conformance and Compliance Framework (ECCF).  
 
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 specification stacks, such as the Services-Aware Interoperability Framework (SAIF) Enterprise Conformance and Compliance Framework (ECCF).  

Revision as of 16:53, 22 March 2010

SAIF Behavioral Framework

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 specification stacks, such as the Services-Aware Interoperability Framework (SAIF) Enterprise Conformance and Compliance Framework (ECCF).

Tony Julian