This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Requirements-Dynamic Model"

From HL7Wiki
Jump to navigation Jump to search
Line 83: Line 83:
 
| '''Requirement'''  
 
| '''Requirement'''  
 
| An interaction binds one trigger event, one payload model, one control act wrapper, one transport wrapper, a sending application role, a receiving application role, and one or more receiver responsibilities. Note that the identification of artifacts is by identifier.
 
| An interaction binds one trigger event, one payload model, one control act wrapper, one transport wrapper, a sending application role, a receiving application role, and one or more receiver responsibilities. Note that the identification of artifacts is by identifier.
 
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  
Line 96: Line 95:
 
| '''Future Requirement'''  
 
| '''Future Requirement'''  
 
| Communicate conformance of receiver responsibilities.  It is necessary to know which receiver responsibilities must happen (mandatory), should happen (required), may happen (optional), and must not happen (usually based on a previous elaboration of a receiver responsibility).  
 
| Communicate conformance of receiver responsibilities.  It is necessary to know which receiver responsibilities must happen (mandatory), should happen (required), may happen (optional), and must not happen (usually based on a previous elaboration of a receiver responsibility).  
 
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  

Revision as of 20:20, 19 October 2009