{scrollbar:icons=false}

h1. {page-info:title}


h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/09/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>_ \\
e.g. Init1dbw1 \\
(eventually&nbsp;linked to Use Cases) | Init1bes7 |
| *Originator/Customer's Name*: | Sal Mungal&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*: | Duke University |
| *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 description_|Semantic Infrastructure Concept of Operations Stakeholders])._ | Software and Application designers and architects \\
Software and Application engineers and developers \\
Clinical and scientific research data and metadata managers \\ |
| *Summary of requirement pre-interview, by Reviewer:* | Actor: Information Specialist \\
Business Goal: To find/discover reusable metadata from knowledge/model repositories&nbsp;&nbsp; \\
An information specialist uses &nbsp;metadata browser (knowledge or model) &nbsp;that will return search results in a customizable table where user will be able to choose what components of metadata (e.g. DEC concepts and Value domains for CDEs, class names, datatypes) to display. |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Follow-up interview |

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} \\ | Yes. \\
&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)_ | Information specialist invokes a search/query using a metadata browser that interacts with knowledge or model repository). In return metadata browser returns a default table with the best hits. Information specialist should be able to customize the columns that will be presented in the search results (e.g. showing value domains, permissible values, superclasses, semantic annotations). |
| 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; | N/A |
| 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)_ | Customizable metadata search results page. \\ |
| 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. Browsers, SIW, Curation Tool, Admin Tool \\
\\
Not user friendly. Too many tools serving similar purposes. Certain functionalities are only available in some so you need to know all for effective use. Most functionalites can be combined under one tool.&nbsp; Rigid/static result pages. \\ |
| 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}Information Specialists should be able to discover/find the right/reusable data elements or model components using metadata search results. Customizable view makes it easy to find desired metadata faster in a single view.{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}Current;y this requirement can be met using different tools (e.g. curation tool). However this tool is not being used by many information specialists and does not serve modelers well.{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}A metadata browser (knowledge or model) &nbsp;that will return search results in a customizable table where user will be able to choose what components of metadata (e.g. DEC concepts and Value domains for CDEs, class names, datatypes) to display.{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)_ | \\
# Must have \\ |
| 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)_ | \\
\\  {color:#000000}3. Completely satisfied&nbsp;{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)_ \\ | No. |
| 12 \\ | Who else should we talk to in order to elicit more information about this&nbsp;need? | N/A |
| | {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)_ | User should be able to customize the columns displayed in search results returned by browsers. |
| 14 | Forum Link: \\ | [https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=40&t=152]\\ |
| 15 | URLs (optional): \\ | Links to pages or applications related to this requirement \\ |
| 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 assessment 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;Functional&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|Semantic Infrastructure Concept of Operations Initiative 1 Repositories]
* [Initiative 2 - Automated generation of metadata from line-of-business artifacts|Semantic Infrastructure Concept of Operations Initiative 2 Automation]
* [Initiative 3 - Rules management and contracts support (behavioral semantics)|Semantic Infrastructure Concept of Operations Initiative 3 Rules]
* [Initiative 4 - Semantics support for W3C service oriented architecture resources|Semantic Infrastructure Concept of Operations Initiative 4 W3C]
* [Initiative 5 - HL7 CTS II/ OMG MIF compliant federated terminology services|Semantic Infrastructure Concept of Operations Initiative 5 Compliance]
* [Initiative 6 - Controlled biomedical terminology, ontology and metadata content|Semantic Infrastructure Concept of Operations Initiative 6 Controlled]
* [Initiative 7 - Assessment of semantic unification of compositional and derivational models|Semantic Infrastructure Concept of Operations Initiative 7 Assessment]
* [Initiative 8 - Other|Semantic Infrastructure Concept of Operations Initiative 8 Other] | Initiative 1 |
| {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|Semantic Infrastructure Concept of Operations Initiatives - Requirements Master List] table. | Combine with Customizable Download; Develop Use Case Template (text) in Round&nbsp;4 \\
Possible draft list of use cases for the metadata browser needed to meet this requirement: \\
\- Formulate a metadata search criteria: This use case should be developed in combination with other requirements set. \\
\- Search metadata: This use case should be developed in combination with other requirements set. \\
\- View search results (metadata) in a "default" tabular&nbsp;presentation/display format: This use case should be developed in combination with other requirements set. \\
\- Customize the "default" tabular presentation/display&nbsp;of&nbsp;search results&nbsp;to capture different metadata components (before or after searching metadata; an alternative flow for search metadata use case) |
\\
{scrollbar:icons=false}