Page History

page-info

:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/23/2009

 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>

_ \\
e.g. Init1dbw1

 \\
(eventually linked to Use Cases) | Init1bes9 |
| *Originator/Customer's Name*:

 | Tommie Curtis

 and  Brian Davis \\
                                                                                    |
| *Originator/Customer's Company*:

 | SAIC and

 BAH |
| *Summary of requirement pre-interview, by Reviewer:

* | Business goal: Ability to develop forms with persistence layers

 \\
Actor: Metadata Specialist (Form Author)

 \\
A metadata specialist will use a dynamic form develoment tool that allows the form designer to interact with the MDR /Models/Rules

 repository to  create new forms that are compatible with existing content. \\
\\
This requirement includes the following 4 use cases: \\
(1) collection of standardized data utilizing reusable data elements \\
(2) defining the form structure \\
(3) defining the form behavior \\
(4) generating the data persistence models to support the form. \\
\\
The tool should interact with a repository (or multiple repositories) that stores: \\
\\
\- Data Element-centric metadata including the abstract concept (CDE) with its associated value domain (e.g. in Knowledge Repository). Data elements should be able to be used regardless of their source (a form based CDE or model based CDE that became available through model load to Knowledge Repository). \\
\\
\- Form metadata including the definition of the form structure including sections, order and their relationships. And also the form behavior including value set constraints, skip logic, repetition and optionality \\
\\
\- Persistence metadata including the contextually defined and constrained instance of use of an abstract concept in a data persistence model,  and the binding of form structural elements to persistence model elements in a given context of use \\ |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Development of detailed use cases \\ |

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

|| *Item* || *Description* || *Information*/Response ||
| *Stakeholder Community*: | Enter appropriate category of stakeholder from Primary Stakeholders:  
* 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]__)._ \\ | \\
\\
Clinical and scientific research data and metadata managers \\
*OR* \\
*Metadata Specialist*: having a deep understanding of semantics and syntactic, assists Cancer Researchers and Information Technologists on modeling and managing metadata 
* *Forms Author*: constructs data collection forms based on a library of common data elements
* *Metadata Curator*: works hands-on with Cancer Researchers and Information Technologists to model and manage their metadata |
| {color:#000000}{*}Requirement Type (required)*{color} | Analyst's assessement of the 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 |                 *Functional*                           |
| ConOp Initiative(s) \\
_Requirements Analyst/Business Analyst_ | * {color:#000000}Select most appropriate initiative: (click for descriptions) {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] | --- |
| {color:#000000}{*}High Level Use Case Summary)*{color} \\
_Requirements Analyst/Business Analyst_ \\ | {color:#000000}Please write a short descriptive narrative use case; the steps or activities in this use case are usually the things the user wants to accomplish with the system (user/actor's goals).  {color} | \--\- |
| {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. | Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
\\
{scrollbar:icons=false}