![]() |
Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Instructions
...
Pre Interview:
Item | Information/Response |
---|---|
Date: | 12/17/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> | Init1pm2 |
Originator/Customer's Name: | Bilal Elahi (mailto: elahib@mail.nih.gov): forum posting |
Originator/Customer's Company: | Unknown |
Stakeholder Community:
| Broader Stakeholders (caBIG Community) |
Summary of requirement pre-interview, by Reviewer: | An additional web interface to the metadata repository is needed that will present metadata content to Cancer Researchers in a manner that does not require background knowledge on metadata structure, semantics, or the standards that underlie the metadata repository (e.g. ISO11179). The browser would envision an alphabetically organized or categorically organized structure that provides metadata information in a simple, easy to understand manner but also provides access to the linkages that underlie the metadata. |
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 Template (requirements gathering has already been performed and documented - see attachments) |
Post Interview - ongoing throughout development of use cases:
...
Item
...
Description
...
Information/Response
...
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
- Project constraint: schedule or budget constraints
...
...
ConOp Initiative(s)
Requirements Analyst/Business Analyst
...
- Select most appropriate initiative: (click for descriptions)
- Initiative 1 - Distributed, federated metadata repositories and model repositories and operations
- Initiative 2 - Automated generation of metadata from line-of-business artifacts
- Initiative 3 - Rules management and contracts support (behavioral semantics)
- Initiative 4 - Semantics support for W3C service oriented architecture resources
- Initiative 5 - HL7 CTS II/ OMG MIF compliant federated terminology services
- Initiative 6 - Controlled biomedical terminology, ontology and metadata content
- Initiative 7 - Assessment of semantic unification of compositional and derivational models
- Initiative 8 - Other
...
...
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?
Scrollbar | ||
---|---|---|
|
...
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.
...