This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Functional Requirement Artifact Definition"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:SAIF Artifact Definition}}") |
|||
| Line 3: | Line 3: | ||
[[:Category:SAIF Artifact Definition|Return to Artifact List]] | [[:Category:SAIF Artifact Definition|Return to Artifact List]] | ||
| − | = | + | =Functional Requirement= |
<!-- Artifact names should be descriptive and short. They may change as we further refine the methodology --> | <!-- Artifact names should be descriptive and short. They may change as we further refine the methodology --> | ||
Latest revision as of 17:02, 10 June 2011
Contents
- 1 Functional Requirement
- 1.1 Definition and Purpose
- 1.2 SAIF Matrix Location
- 1.3 Prior Methodology Correspondence
- 1.4 Audience
- 1.5 Applicability
- 1.6 Requirements, Relationships and Content
- 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 Artifact Exchange and Version Management
- 1.15 Authoring and Maintenance Tools
- 1.16 Governance Process Considerations
- 1.17 Issues
Functional Requirement
Definition and Purpose
Put text here
SAIF Matrix Location
Row(s)
- Conceptual (CIM)
- Logical (PIM)
- Implementable (PSM)
Column(s)
- Enterprise/Business
- Information
- Computational
- Engineering
- Technical
Prior Methodology Correspondence
Audience
Health Care Community Audiences:
- General public
- Health care practitioners
- Health system administrators
- Health care policy makers
Health Care Information Technology (IT) Audiences:
- Standards developers and standards development organizations
- System designers and architects
- System purchasers
- Programmers/implementers
- System vendor management
- Education/Research
Applicability
Text
Rationale: More text
Requirements, Relationships and Content
- Some requirement
- RationaleSome reason
- Some other requirement
- RationaleSome other reason
Relationships and traceability
- Some relationship
- Rationale: Reason for relationship
- Some other relationship
- Rationale: Reason for other relationship
Artifact types that may or must relate to this artifact types:
- Many-related Artifact Type
- Another Many-related Artifact Type
Content
- Content element name - Brief Description
- Another content element name - Brief Description
- Sub-element name - Brief Description
- Another content element name - Brief Description
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
Artifact Exchange and Version Management
Authoring and Maintenance Tools
Governance Process Considerations
- Governance Process name - Some process description
- Rationale: Some rationale
- Another Governance Process name - Process description
- Rationale: Some other rationale
Issues
- Some issue
- Some other issue
