NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item

Information/Response

Date

12/15/2009

Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number>
e.g. Init1dbw1
(eventually linked to Use Cases)

Init3dbw7

Originator/Customer's Name:

Anand Basu                                                                                     

Originator/Customer's Company:

CBIIT Application Engineering

Summary of requirement pre-interview, by Reviewer:

Application developers covering a broad spectrum of disciplines need to be able to find data and services that can be integrated, without knowing much about the infrastructure.  It should be easy to use, Taverna and caB2B are too difficult/awkward to use.  A workflow authoring tool should leverage so that the end user (application developer and researcher) should not have easily use the infrastructure to create workflows without having to figure out how to integrate the data or services, the infrastructure should step them through it and just ask for things that are not already available - the infrastructure services and UIs, portals, need to go beyond just finding data or services based on search terms. Reuse of Platform  need to be able to reuse stored Platform Independent Models (PIMs) to create Platform Specific Models needs to be almost (PSM) - almost transparent to the end user (application developers) .  Like scratch.mit.edu, everything you need to know shoudl be easily accessible from the download page.  This includes click through installation and setup for using the infrastructure, easy access to getting started instructions, release notes, frequently asked questions specific to each supported platform (PC, MAC, Linux etc),  and links to submit trouble tickets or access the support desk.  Ideally, the UIs would be intuitive, drag and drop - if the data does not 'fit' into the service, the system should do the analysis in the background and explain what is needed in order for the service to accept the data, if there is an existing service that could be used to pre-process the data, the system should discover that service and present it to the end user.  If you have data that is of a particular type, the system could find the services that can take your data, then show you other services that take the result of the services you have executed.  For example, the workflow tool should help users author sensible workflows be recognizign things that are processign raw data as input to another higher level service and try to automatically organize a workflow based on the data the user has access to- the metadata should be compared and possible integration points served up. 
Everything needed to use the application should be available from the download, like Scratch from MIT (good example). 
Click through setup, instructions, release notes, faqs, links to support desk.  would lead the user through steps to fit data to the service, or services together at different levels (1,2,3,4) where the output from one level can be used as input to another level - such as a pre-processing step that is needed before inputting the data to another service.  Alternatively, the system could serve up data sources that can be used with a particular service, and note the services that might be interesting to run before or after the one you are looking at.  The system shoudl be able to find and reuse appropriate transformation services, and save the workflow for use/resue by the author or others.

Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room

Use case decomposition.

...

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).



Requirement Type (required)

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

                                                                                                

ConOp Initiative(s)
Requirements Analyst/Business Analyst

 

High Level Use Case Summary)
Requirements Analyst/Business Analyst

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).  

 

Use Case Linkage (required)
Business Analyst

Which use case(s) is this requirement linked to?  (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):

Conflicts / Dependencies(required)
Requirements Analyst/ Business Analyst

Are there any conflicts with other requirements / use cases? 

Yes OR No - If yes, what and why?

Next Step (required)
(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 table.

Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room