Page History
Wiki Markup |
---|
{scrollbar:icons=false}
h1. { |
Scrollbar | ||
---|---|---|
|
page-info |
...
Initial Analysis:
...
Item
...
Information/Response
...
Date:Â
:title} h2. Initial Analysis: || Item || Information/Response || | {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 01/26/2010 |
...
| | {color:#000000}{*}Requirement # unique id{*}{color} _<SemConOps Initiative>.<analysts initials><requirement number> |
...
_ \\ e.g. Init1dbw1 |
...
Init3bes17
\\ (eventually linked to Use Cases) | Init3bes17 | | *Originator/Customer's Name*: |
...
| John Koisch, |
...
Paul Boyes | | *Originator/Customer's Company*: |
...
| Guidewire Architecture, Guidewire |
...
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)
...
Architecture | | *Summary of requirement initial analysis, by Reviewer:* (as unambiguously as possible, describe who ([List of Actors|https://wiki.nci.nih.gov/x/ewtyAQ]) 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 requirement is based on an interview documented at: \\ [https://wiki.nci.nih.gov/x/shpyAQ |
...
] \\ \\ Business ;goal: To allow developers to find conformance |
...
profiles that standardardize semantic and functional descriptions for services \\ \\ Actor: Information Technologist \\ \\ An information specialist would like to develop a service that conforms to an existing conformance profile. The conformance profiles are stored in a registry or repository in a structured/computable electronic format (e.g. XSD). The registry/repository should provide services that support search capabilities stated in requirement: |
...
\\ \\ [Init3bes16 - Conformance Profile Browser|Init3bes16 - Conformance Profile Browser] \\ \\ The registry/repository should provide service that support registration capability stated in requirement: |
...
\\ [Init3bes18 - Conformance Profile Editor|Init3bes18 - Conformance Profile Editor] | | *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 an architect for further detailing the requirement for use case development. John Koisch and/or Paul Boyes can be contacted for appropriate contact. |
...
|
\\
{scrollbar:icons=false} |