![]() |
Page History
...
Item | Information/Response |
---|---|
Date: | 12/14/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> | Init1bes8 |
Originator/Customer's Name: | Hannes Hannes Niedner |
Originator/Customer's Company: | 5AM Solutions (previously UCSD Moores Cancer Center) |
Stakeholder Community:
|
|
Summary of requirement pre-interview, by Reviewer: | Currently CDEs are bound to an object class which hinders reuse for developers. Although this supports domain information modeling, where classes actually represent real life entities, it does not support non-domain information modeling (e.g. summary classes, report classes that combine many attributes from different domain classes). Supporting such non-domain modeling practices will improve semantic interoperability. and removing object class/DE dependency will be needed. |
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 |
...
Item | Description | Information/Response |
---|---|---|
Requirement Type (required) | Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):
|
|
ConOp Initiative(s) |
|
|
Use Case Linkage (required) | 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) | Are there any conflicts with other requirements / use cases? | Yes OR No - If yes, what and why? |
Next Step (required) | 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 |