NIH | National Cancer Institute | NCI Wiki  

Initial Analysis:

Item

Information/Response

Date

01/08/2010

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

Init3bes14

Originator/Customer's Name:

Frank Hartel, John Koisch, Paul Boyes
                                                                                 

Originator/Customer's Company:

NCI, Guidewire Architecture, Guidewire Architecture

Summary of requirement initial analysis, by Reviewer: (as unambiguously as possible, describe who (List of Actors) is interacting with the system, what the business goal is and how the system might support the actor's ability to acheive their goal)

This analysis is based on a document that describes conformance profiles (also attached)

historical link: https://wiki.nci.nih.gov/download/attachments/24255154/Conformance+Profiles.doc

Prior to interview with John Koish and Paul Boyes, the requirement statement was not available.
Arch WS Presentation on SAIF and ECCF: Pankaj Agarwal
"Traceability and semantic consistency from BRIDG and the LS-DAM to implemented services are critical to semantic conformance. Therefore, the semantic infrastructure must support automated or assisted verification of semantic consistency"

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 with John Koisch and Paul Boyes to identify higher level requirements to support conformance profiles.

Interview

Item

Script / Question

Information/Response

1

Hello, my name is NAME. I am calling you today because NCI and caBIG are working toward a new and improved version of the semantic infrastructure to better support integration scenarios .
Our first step was to organize requirements collected over the past year.  Your organization has expressed a requirement/need for BRIEF STATEMENT OF USER REQUIREMENT.  This has been identified as potentially a critical component to support application/data and service integration, and we need more information in order to enable us to meet this requirement.
Do you have about 30 minutes to talk about this?

Yes.
                                                                                                                    

2

What do you do? What are your goals for the next year?  Why are you doing this?

Develop conformance profiles to standardize the semantic and functional descriptions of services. Conformance Profiles are a mechanism used to constrain/group broader service capabilities/features to meet specific functional needs identified within a domain or locality. This increases interoperability and lessens the number of variations of implementations of services, and also provides clarity to potential service consumers.

3

In interacting with the caBIG infrastructure, do you have any solution integration needs? If so, what are they? Have you envisioned new ways of interacting with existing or new parts of the semantic  infrastructure?
(prompt to elicit changes/new ways of using the infrastructure)

Conformance profiles is a new concept to caBIG and important to support ECCF (e.g. developers will provide conformance assertions for profiles) 

So  the new infrastructure should:
- Store conformance profiles in a repository/registry
- Provide/define a computable/electronic format for Conformance Profiles
- Provide tooling supporting to browse/search Conformance Profiles
- Provide tooling supporting to create/register Conformance Profiles
- Provide mechanisms to transform Conformance Profiles to artifacts helping service development (e.g. WSDL)
- Provide mechanisms to test conformance of a service description (e.g. WSDL)  or information model to a conformance profile (functional and semantic profiles respectively) 

4

Are there any business changes you are assuming we will be able to deal with? 
(prompt to elicit changes/new ways of using the infrastructure) 

---

5

Are there any capabilities you are expecting to be available to support your needs? 
(prompt to elicit expectations/dependencies)

A repository/registry to store conformance profiles.
An electronic format for conformance profiles.
A browser (tool) to support discovery (search) and creating/registering creating conformance profiles.
A tool (could be part of browser) to transform profiles to artifacts helping service development (e.g. functional profiles to WSDL)
A tool to test conformance of a service description (e.g. WSDL)  or information model to a conformance profile

6

Do you use any of the existing software/services? If so, what do you like or dislike about it?
(if related to existing capability)

Not for related purposes.

7

If this requirement is met, what would be the benefits? If you do not have it, what would be the negative impact?
(prompt to elicit benefits/value - will help to prioritize)

It will help to standardize the semantic and functional descriptions of services. Consequently support interoperability among services.

8

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?
(prompt to elicit alternative solutions/workarounds)
(to be prepared by the Requirement Analyst)

No.

9

Would you agree that we can summarize your requirement like this?
(Summarize one requirement in 2-3 lines and read back to interviewee for confirmation.)

 The new infrastructure should:
- Store conformance profiles in a repository/registry
- Provide/define a computable/electronic format for Conformance Profiles
- Provide tooling supporting to browse/search Conformance Profiles
- Provide tooling supporting to create/register Conformance Profiles
- Provide mechanisms to transform Conformance Profiles to artifacts helping service development (e.g. WSDL)
- Provide mechanisms to test conformance of a service description (e.g. WSDL)  or information model to a conformance profile (functional and semantic profiles respectively) 

10

How important is this requirement to the interviewee? Required: Customer Priority/Annotationrement Analyst
(Provides concrete assessment of the relative importance for the requirements specification)

 

  1. Must have

11

On a scale from 1 to 3 with 1 being "not satisfied" to 3 "completely satisfied", how would you rate your overall satisfaction with the product if this requirement was met?  (Relative rating/ranking of how satisfied or dissatisfied interviewee would be if this requirement were met/not met)


 3.  Completely satisfied

12

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.
(prompt to elicit any hidden - potentially higher priority requirements if they exist)

No.

13

Who else should we talk to in order to elicit more information about this need?

---

 

For specific service enhancement or requirement from Forum entry:

---

14

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? 
(Required: Fit Criterion - will help us create test cases and user acceptance criteria - to be prepared by the Requirement Analyst)

This will depend on individual requirement. This requirement should further decomposed beofre identifying these steps.

15

Forum Link:

---

16

URLs (optional):

historical link: https://wiki.nci.nih.gov/download/attachments/24255154/Conformance+Profiles.doc]

17

References (optional):

Links to articles, papers or presentations related to this requirement

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


Software and Application designers and architects
Software and Application engineers and developers

Requirement Type (required)

Analyst's assessment 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/Nonfunctional

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.

Decompose this requirement and conduct follow-up interviews with John Koisch and Paul Boyes to develop use cases for distinct requirements:
- Store conformance profiles in a repository/registry
- Provide/define a computable/electronic format for Conformance Profiles
- Provide tooling support to browse/search Conformance Profiles
- Provide tooling support to create Conformance Profiles
- Provide mechanisms to transform Conformance Profiles to platform specific artifacts(e.g. WSDL)
- Provide mechanism to test conformance of a programming (e.g. WSDL)  or modeling artifactto a  profile

  • No labels