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

Difference between revisions of "Template:SAIF Generic IM Tooling"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "<noinclude><span style="color:#0000FF">Generic Tooling Considerations content for SAIF Information models.<br/>          <b>Only the ...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
<noinclude><span style="color:#0000FF">Generic Tooling Considerations content for SAIF Information models.<br/>
 
<noinclude><span style="color:#0000FF">Generic Tooling Considerations content for SAIF Information models.<br/>
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>Only the content appearing below in <span style="color:#000000">black font</span> will appear in the inclusion.</b><br/>  
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>Only the content appearing below in <span style="color:#000000">black font</span> will appear in the inclusion.</b><br/>  
These elements are intended to appear under the following section:</span>
+
These elements are intended to appear under the following section:
 +
 
 +
[[:Category:SAIF Artifact Definition|goto to SAIF artifact definitions]]</span>
 
== <span style="color:#0000FF"> Tooling Considerations </span>==
 
== <span style="color:#0000FF"> Tooling Considerations </span>==
 
</noinclude>
 
</noinclude>
 
<!-- What tooling features are required or "nice to have" to allow successful development, publication or other use of the artifact? -->
 
<!-- What tooling features are required or "nice to have" to allow successful development, publication or other use of the artifact? -->
# Nice-to-have|Required: Some feature
+
The following defines the ideal tool for use in creating these artifacts.  The rationale for these elements is expressed in the [[#Rationale|"Rationale" sub-section]] of the [[#Artifact Technology|"Artifact Technology" section]] above.
## <i>Rationale</i>: Some rationale
+
===Ideal model creation tool for this artifact===
# Nice-to-have|Required: Some other feature
+
Would be a UML Modeling tool that has been customized to:
## <i>Rationale</i>: Some other rationale
+
# Capture and represent the HL7-defined properties that are applicable to this model
 +
#:
 +
# Able to "read" and "write" the content in MIF format
 +
## Including the graphic layout of the model
 +
#:
 +
#Able to define and document:
 +
##Entry Points
 +
##:
 +
##Common model (CMET) references
 +
##:
 +
##Other model references, and
 +
##:
 +
##"Stub" classes
 +
#:
 +
# Able to enforce derivation constraints on the model using the [[Reference Information Model Artifact Definition|RIM]] and [[Vocabulary Model Artifact Definition|Vocabulary Model]] (from MIF files) to configure these constraints dynamically
 +
#:
 +
#Able to configure the tool user interface using the [[Reference Information Model Artifact Definition|RIM]], [[Vocabulary Model Artifact Definition|Vocabulary Model]] and [[Interface Model Artifact Definition|Interface Model]] (CMET file), provided as MIF files) to provide selections that are proper constraints and/or content from, these key derivation sources.
 +
#:
 +
#Able to represent the graphic expressing on model classes using the HL7 [[Static Model BNF Grammar]]

Latest revision as of 18:00, 10 April 2011

Generic Tooling Considerations content for SAIF Information models.
         Only the content appearing below in black font will appear in the inclusion.
These elements are intended to appear under the following section:

goto to SAIF artifact definitions

Tooling Considerations

The following defines the ideal tool for use in creating these artifacts. The rationale for these elements is expressed in the "Rationale" sub-section of the "Artifact Technology" section above.

Ideal model creation tool for this artifact

Would be a UML Modeling tool that has been customized to:

  1. Capture and represent the HL7-defined properties that are applicable to this model
  2. Able to "read" and "write" the content in MIF format
    1. Including the graphic layout of the model
  3. Able to define and document:
    1. Entry Points
    2. Common model (CMET) references
    3. Other model references, and
    4. "Stub" classes
  4. Able to enforce derivation constraints on the model using the RIM and Vocabulary Model (from MIF files) to configure these constraints dynamically
  5. Able to configure the tool user interface using the RIM, Vocabulary Model and Interface Model (CMET file), provided as MIF files) to provide selections that are proper constraints and/or content from, these key derivation sources.
  6. Able to represent the graphic expressing on model classes using the HL7 Static Model BNF Grammar