diff --git a/asciidoc/images/vol1-diagram-sdpi-req-types-model.svg b/asciidoc/images/vol1-diagram-sdpi-req-types-model.svg index 1edae44..96d9ada 100644 --- a/asciidoc/images/vol1-diagram-sdpi-req-types-model.svg +++ b/asciidoc/images/vol1-diagram-sdpi-req-types-model.svg @@ -1,18 +1,20 @@ + - - - - - + inkscape:current-layer="g78" /> + id="g78" + transform="translate(-103,-206.68896)"> + id="rect188" + width="1058.1488" + height="249.72777" + x="92.54628" + y="196.23524" /> 0..1 + transform="translate(421.917,383)" + id="text4">0..1 + id="rect6" /> Requirement + id="text8">Requirement Definition + id="text10">Definition satisfied + id="text12">satisfied by + id="text14">by + id="rect16" /> Use Case Feature + transform="translate(334.804,414)" + id="text18">Use Case Feature + id="rect20" /> Ref. Standard ICS + transform="translate(540.594,414)" + id="text22">Ref. Standard ICS + id="rect24" /> SES + transform="translate(810.145,415)" + id="text26">SES + id="rect28" /> Tech Feature + transform="translate(968.563,414)" + id="text30">Tech Feature + d="m 624.108,340.167 v 21.039 H 419.5 l 0.667,-0.666 v 27.039 h -1.334 v -27.706 h 204.609 l -0.667,0.667 v -20.373 z m -4.666,1.333 4,-8 4,8 z" + id="path32" /> + d="M 6.66667,-0.666667 H 27.7766 V 0.20147 L 27.1099,-0.465197 H 54.2198 V 0.868136 H 26.4433 V 0 l 0.6666,0.666667 H 6.66667 Z M 8,4 0,0 8,-4 Z" + transform="matrix(0,1,1,0,623.5,333.5)" + id="path34" /> + id="path36" /> + id="path38" /> “is a” + id="text40">“is a” 0..1 + transform="translate(628.972,383)" + id="text42">0..1 0..1 + transform="translate(832.913,383)" + id="text44">0..1 0..1 + transform="translate(1039.37,382)" + id="text46">0..1 + id="rect48" /> Requirement + id="text50">Requirement Usage + id="text52">Usage + id="path54" /> 1..* + id="text56">1..* 1..* + id="text58">1..* satisfies + id="text60">satisfies + id="path62" /> 0..* + id="text64">0..* requirement + id="text66">requirement group + id="text68">group + + IHE Profile + + 0..1 diff --git a/asciidoc/volume1/tf1-ch-a-requirements-interoperability.adoc b/asciidoc/volume1/tf1-ch-a-requirements-interoperability.adoc index 165f2c5..aeacea9 100644 --- a/asciidoc/volume1/tf1-ch-a-requirements-interoperability.adoc +++ b/asciidoc/volume1/tf1-ch-a-requirements-interoperability.adoc @@ -190,15 +190,16 @@ It should be further noted that though conformity testing aspects are beyond thi [#vol1_clause_sdpi_requirements_core_model] ==== SDPi Requirements Core Model -To formally integrate requirements in to this specification, the following requirements model provides the starting point: +To formally integrate requirements in to this specification, the following model details the core types of requirements that will be defined: [#vol1_figure_appendix_a_sdpi_requirements_core_model] -.SDPi Requirements - Core Model +.SDPi Requirement Categories - Core Model image::../images/vol1-diagram-sdpi-req-types-model.svg[align=center] -This model identifies a set of requirement "types" that are formalized in the specification. -Each type is a source of requirements that are explicitly identified and formalized with appropriate metadata. +This model identifies the set of requirement "types" that are utilized in the specification. + +Each type defines a unique class of requirements that build upon a foundational specification that may be specialized with additional metata to better capture the unique source and role of each specification. [%autowidth] [cols="^1,4,^1,^1"] @@ -218,7 +219,12 @@ Each type is a source of requirements that are explicitly identified and formali | Usage | Requirement utilized in a specific use context that provides for its satisfaction. | sdpi_requirement_usage -| +| + +| IHE Profile +| Each IHE profile specification has a set of requirements that must be captured. For example, Actor X in Profile Y requires support for Transaction A + B + C. +| sdpi_requirement_ihe_profile +| | Use Case Feature | A functional "feature" requirement based on clinical use case scenarios. @@ -231,12 +237,12 @@ Each type is a source of requirements that are explicitly identified and formali | | SES -| +| Non-technical requirements related to Safety, Effectiveness, and Security are captured in these blocks. These are especially relevant to mapping ISO/IEEE 11073-1070x Participant Key Purposes standard requirements to elements within the SDPi specification. | sdpi_requirement_ses | See SES Section <> | Tech Feature -| +| Technology focused requirements result from the use of a particular implementation approach. For example, use of TLS 1.3 may also result in the need to address related technical capabilities. | sdpi_requirement_tech_feature | |=== diff --git a/sources/vol1-diagram-sdpi-req-types-model.pptx b/sources/vol1-diagram-sdpi-req-types-model.pptx index 2e9a0e1..e45fe7c 100644 Binary files a/sources/vol1-diagram-sdpi-req-types-model.pptx and b/sources/vol1-diagram-sdpi-req-types-model.pptx differ