Page History

h2. *Instructions*

Follow the script instructions and record the information in the designated table cells. You may wish to make notes below the questions.

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/10/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>_ \\
e.g. Init1dbw1 \\
(eventually&nbsp;linked to Use Cases) | Otherdbw1\\ |
| *Originator/Customer's Name*: | Customer Liaison: Margaret Haber &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
| *Originator/Customer's Company*: | CDSIC / Margaret Haber\\ |
| *Stakeholder Community*: \\
Enter appropriate category of stakeholder from Primary Stakeholders:&nbsp;&nbsp;
* Software and Application designers and architects
* Software and Application engineers and developers
* Scientific and medical researchers
* Medical research protocol designers
* Clinical and scientific research data and metadata managers
* Clinicians
* Patients
* Medical research study participants
* Broader Stakeholders: caBIG® Community WS NIH projects and related commercial COTS vendors (caEHR, SDO's (HL7, CDISC); International Collaborators (e.g NCRI, cancerGrid, China), Government and regulatory bodies (FDA, CDC, ONC) \\
_[_(link to view SemConOps Stakeholders decription_|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Stakeholders#Stakeholders_Overview]__)._ | \\
SDO \\ |
| *Summary of requirement pre-interview, by Reviewer:* | <!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-alt:"Calisto MT"; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-alt:"Times New Roman"; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman";} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph 	{mso-style-priority:34; 	mso-style-unhide:no; 	mso-style-qformat:yes; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:0in; 	margin-left:.5in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman";} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	font-size:10.0pt; 	mso-ansi-font-size:10.0pt; 	mso-bidi-font-size:10.0pt;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;}  /* List Definitions */  @list l0 	{mso-list-id:1819495858; 	mso-list-type:hybrid; 	mso-list-template-ids:-426723560 1149649552 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 	{mso-level-start-at:12; 	mso-level-number-format:bullet; 	mso-level-text:-; 	mso-level-tab-stop:none; 	mso-level-number-position:left; 	text-indent:-.25in; 	font-family:"Calibri","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-bidi-font-family:"Times New Roman";} @list l0:level2 	{mso-level-tab-stop:1.0in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level3 	{mso-level-tab-stop:1.5in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level4 	{mso-level-tab-stop:2.0in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level5 	{mso-level-tab-stop:2.5in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level6 	{mso-level-tab-stop:3.0in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level7 	{mso-level-tab-stop:3.5in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level8 	{mso-level-tab-stop:4.0in; 	mso-level-number-position:left; 	text-indent:-.25in;} @list l0:level9 	{mso-level-tab-stop:4.5in; 	mso-level-number-position:left; 	text-indent:-.25in;} ol 	{margin-bottom:0in;} ul 	{margin-bottom:0in;} -->{color:#1f497d}NCI has stated to CDISC is that if they submit their requirements to us during our build, they would be incorporated as our requirements. With the caveats that:{color}\\
 \\
{color:#1f497d}\-{color}{color:#1f497d}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#1f497d}all requirements cannot be met in the first iteration, it will be a process{color}\\
{color:#1f497d}\-{color}{color:#1f497d}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#1f497d}due to the distributable nature of what we plan to build, we made no assumptions about hosting{color} \\
{color:#1f497d}\- &nbsp; &nbsp;&nbsp; there could be one to many terminology servers and repositories serving NCI, CDISC or others{color} |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Review and decompose into Use Case Templates for the attached documentation, schedule follow up through Margaret Haber \\ |

h2. Interview

|| Item || {color:#000000}Script / Question{color} \\ || {color:#000000}Information/Response{color} \\ ||
| 1 | {color:#000000}Hello, my name is NAME. I am calling you today because NCI and caBIG are{color} {color:#000000}working toward a new and improved version of the semantic infrastructure to better{color} {color:#000000}{*}support integration scenarios{*}{color}{color:#000000}.{color} \\  {color:#000000}Our{color} {color:#000000}first step was to organize requirements collected over the past year.&nbsp;{color}{color:#000000}Your organization has expressed a requirement/need for{color} {color:#000000}BRIEF STATEMENT OF USER&nbsp;REQUIREMENT.{color}&nbsp; {color:#000000}This has been identified as potentially a critical{color} {color:#000000}component to support application/data and service integration, and we need more information{color} {color:#000000}in order to enable us to meet&nbsp;this requirement.{color}\\  {color:#000000}{*}Do you have about 30 minutes to talk about this?*{color} \\ | {color:#000000}If yes, proceed. If no, note a good time to call back.{color} \\
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
| 2 | Do you have any&nbsp;solution integration needs? If so, what are they? Have you envisioned&nbsp;new ways of interacting with existing or new parts of the semantic&nbsp; infrastructure? \\
_(prompt to elicit changes/new ways of using the infrastructure)_ | Notes describing potential interactions \\ |
| 3 | Are there any business changes you are assuming we will be able to deal with?&nbsp; \\
_(prompt to elicit changes/new ways of using the infrastructure)_&nbsp; | Notes on anticipated business changes |
| 4 | {color:#000000}Are there any capabilities&nbsp;you are expecting to be available to support your needs?{color}&nbsp; \\
_(prompt to elicit expectations/dependencies)_ | {color:#000000}Notes that identify capabilities, tools,&nbsp;and/or services expected{color} \\ |
| 5 | Do you use any of the existing software/services? If so, what do you like or dislike about it? \\
(_if related to existing capability)_ | Yes OR No/ Notes that fully describe the requirement \\ |
| 6 | {color:#000000}If this requirement in met,&nbsp;what would be the benefits? If you do not have it, what would be the negative impact?{color}\\  {color:#000000}_(prompt to elicit benefits/value - will help to prioritize)_{color} | {color:#000000}Summary of perceived benefit or negative impact{color} |
| 7 | {color:#000000}If, for any reason, we were not able to create that solution, do you think there might be another way to solve this issue? Can you think of an alternative solution?{color}\\
_(prompt to elicit alternative solutions/workarounds)_ \\
_(to be prepared by the Requirement Analyst)_ | {color:#000000}Description of any other solution that customer can envision{color} |
| 8 | {color:#000000}Would you agree that we can summarize your requirement like this?{color}\\  {color:#000000}_(Summarize one requirement in 2-3 lines and read back to interviewee for confirmation.)_{color} | {color:#000000}Requirement statement accepted by interviewee{color} \\ |
| 9 | How important is this requirement to the interviewee? _Required: Customer Priority/Annotationrement Analyst_ \\
_(Provides concrete assessment of the relative importance for the requirements specification)_ | Select: \\
# Must have
# Should have
# Nice to have but not essential
# Other (describe) |
| 10 | On a scale from 1 to&nbsp;3 with 1 being "not satisfied" to&nbsp;3 "completely satisfied", how would you rate your overall satisfaction with the product if this requirement was met?&nbsp; _(Relative rating/ranking of how satisfied or dissatisfied interviewee would be if this requirement were met/not met)_ | Select: \\
# {color:#000000}Not satisfied{color}
# {color:#000000}Mostly satisfied{color}
# {color:#000000}Completely satisfied&nbsp;{color}
# {color:#000000}Other (describe){color} |
| 11 \\ | {color:#000000}Are there other requirements that you would like to share with us? I'd be more than happy to call you back another time, or if you have another 10 minutes, please share other issues you can think of.{color}\\
_(prompt to elicit any hidden - potentially higher priority requirements if they exist)_ \\ | (If yes, take notes to use in on a new page with this template; if time not available now, try to make appointment for another call.) |
| 12 \\ | Who else should we talk to in order to elicit more information about this&nbsp;need? | Name of contact(s) |
| | {color:#000000}{*}{_}For specific service enhancement or requirement from Forum entry:_{*}{color} | \\ |
| 13 | {color:#000000}Can you or someone else give me a step-by-step description of how you would describe the expected performance/behavior of the software in order for you to feel that your requirement is met?&nbsp;{color} \\
_(Required: Fit Criterion&nbsp;\- will help us create test cases and user acceptance criteria -_ _to be prepared by the Requirement Analyst)_ | Well defined measurable verifiable expectation |
| 14 | Forum Link: \\ | VKC or other forum where this requirement is discussed \\ |
| 15 | URLs (optional): \\ | See attachments to this page: \\ |
| 16 | References (optional): \\ | Links to articles, papers or presentations related to this requirement \\ |

h2. Post Interview - ongoing throughout development of use cases:

|| *Item* || *Description* || *Information*/Response ||
| {color:#000000}{*}Requirement Type (required)*{color} | Analyst's assessement of the&nbsp;most appropriate category/type of requirement (_no need to ask interviewee)_: \\
* *Functional:* Fundamental or essential to the product - describes what the product has to do or what processing is needed \\
* *Nonfunctional:* properties the functions must have such as performance, usability, training or documentation \\
** *Project constraint:* schedule or budget constraints \\
** *Design constraint:* impose restrictions on how the product must be designed, such as conformant to ISO 11179, utilizes 21090 or is able to work on a particular type of device \\
** *Project driver:* business-related forces such as descriptions of stakeholders or purpose of the product/project \\
** *Project issue:* conditions that will contribute to the success or failure of the project | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
| ConOp Initiative(s) \\
_Requirements Analyst/Business Analyst_ | * {color:#000000}Select&nbsp;most appropriate initiative: (click for descriptions)&nbsp;{color}
* [Initiative 1 - Distributed, federated metadata repositories and model repositories and operations|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init1_Repositories]
* [Initiative 2 - Automated generation of metadata from line-of-business artifacts|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init2_Automation]
* [Initiative 3 - Rules management and contracts support (behavioral semantics)|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init3_Rules]
* [Initiative 4 - Semantics support for W3C service oriented architecture resources|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init4_W3C]
* [Initiative 5 - HL7 CTS II/ OMG MIF compliant federated terminology services|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init5_Compliance]
* [Initiative 6 - Controlled biomedical terminology, ontology and metadata content|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init6_Controlled]
* [Initiative 7 - Assessment of semantic unification of compositional and derivational models|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init7_Assessment]
* [Other|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Init8_Other] | |
| {color:#000000}{*}Use Case Linkage (required)*{color} \\
_Business Analyst_ \\ | {color:#000000}Which use case(s) is this requirement linked to?&nbsp;{color} (should follow Use Case numbering scheme _<SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>_, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. | Use case Number(s): |
| {color:#000000}{*}Conflicts / Dependencies(required)*{color} \\
_Requirements Analyst/ Business Analyst_ | {color:#000000}Are there any conflicts with other requirements / use cases?&nbsp;{color} \\ | Yes OR No - If yes, what and why? |
| {color:#000000}{*}Next Step (required)*{color} \\
_(Requirement Analyst / Business Analyst)_ \\ | After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the [Master List|https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/SI_Conop_Initiatives_Requirements_Master_List] table. | Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |