This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Issues with SAIF Artifact Definition"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:SAIF Artifact Definition}}") |
|||
| Line 1: | Line 1: | ||
| − | + | <!-- [[Category:SAIF Artifact Definition]] --> | |
| − | [[Category:SAIF Artifact Definition]] | ||
[[:Category:SAIF Artifact Definition|Return to Artifact List]] | [[:Category:SAIF Artifact Definition|Return to Artifact List]] | ||
| − | + | =By Section= | |
| − | + | No problem with: | |
| − | + | *Some Artifact Name | |
| − | + | *SAIF Matrix Location | |
| + | ===NEW SECTION - '''specializes''' or '''restricts''' or '''includes''. another SAIF A D=== | ||
| + | We are going to end up with a '''MAINTENANCE NIGHTMARE''' if end up with individual SAIF Artifact Definitions for | ||
== Definition and Purpose == | == Definition and Purpose == | ||
| − | + | Issue: Are not "content" and "relationship" assertions an integral part of some definitions? | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Audience == | == Audience == | ||
| − | + | Suggest we need a common classification for audience types by both "community" of interest and "role" in defining or using HL7 specifications | |
| − | |||
| − | |||
| − | |||
== Applicability == | == Applicability == | ||
| − | + | How much does this differ from "SAIF Matrix Location"? | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Requirements == | == Requirements == | ||
| − | + | I fear we are have two issues here: | |
| − | + | #'''Traceability''' - How do I reference my relationships and content constraints back to specific requirements | |
| − | # | + | #: |
| − | # | + | #'''Redundancy''' - It is very difficult to state a "requirement" without simultaneously defining either a relationship or a constraint, yet we do NOT want to define these in two places. |
| − | |||
| − | |||
| − | |||
== Relationships and traceability == | == Relationships and traceability == | ||
Revision as of 14:47, 8 April 2011
Contents
- 1 By Section
- 1.1 NEW SECTION - specializes' or restricts or includes. another SAIF A D
- 1.2 Definition and Purpose
- 1.3 Audience
- 1.4 Applicability
- 1.5 Requirements
- 1.6 Relationships and traceability
- 1.7 Artifact Technology
- 1.8 Content Constraints
- 1.9 Content Guidelines
- 1.10 Publishing Representation(s)
- 1.11 Publishing Constraints
- 1.12 Tooling Considerations
- 1.13 Development Process Considerations
- 1.14 Issues
By Section
No problem with:
- Some Artifact Name
- SAIF Matrix Location
NEW SECTION - specializes' or restricts or includes. another SAIF A D
We are going to end up with a MAINTENANCE NIGHTMARE if end up with individual SAIF Artifact Definitions for
Definition and Purpose
Issue: Are not "content" and "relationship" assertions an integral part of some definitions?
Audience
Suggest we need a common classification for audience types by both "community" of interest and "role" in defining or using HL7 specifications
Applicability
How much does this differ from "SAIF Matrix Location"?
Requirements
I fear we are have two issues here:
- Traceability - How do I reference my relationships and content constraints back to specific requirements
- Redundancy - It is very difficult to state a "requirement" without simultaneously defining either a relationship or a constraint, yet we do NOT want to define these in two places.
Relationships and traceability
- Some relationship
- Rationale: Reason for relationship
- Some other relationship
- Rationale: Reason for other relationship
Artifact Technology
Text here
Rationale
- Some reason
- Some other reason
Alternatives
Some technology
- Some pro or con
- Some other pro or con
Content Constraints
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Content Guidelines
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Publishing Representation(s)
- Some text
- Rationale: Some rationale
- Some other text
- Rationale: Some other rationale
Publishing Constraints
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Tooling Considerations
- Nice-to-have|Required: Some feature
- Rationale: Some rationale
- Nice-to-have|Required: Some other feature
- Rationale: Some other rationale
Development Process Considerations
- Some text
- Rationale: Some rationale
- Some other text
- Rationale: Some other rationale
Issues
- Some issue
- Some other issue
