Page History
Wiki Markup |
---|
{scrollbar:icons=false}
h1. { |
Page info |
---|
...
|
Initial Analysis:
Item | Information/Response |
---|---|
Date: | 01/26/2010 |
...
Requirement # unique id <SemConOps Initiative>.<analysts |
...
initials><requirement |
...
number> |
...
|
...
Init1dbw1 |
...
| Init3bes18 |
Originator/Customer's |
...
Name |
...
: |
...
John |
...
Koisch, |
...
Paul Boyes |
Originator/Customer's |
...
Company |
...
: |
...
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 requirement is based on an interview documented at: |
...
|
...
To |
...
allow |
...
creation |
...
of |
...
conformance profiles that standardardize semantic and functional descriptions for services | |
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. |
Wiki Markup |
---|
profiles that standardardize semantic and functional descriptions for services \\
\\
Actor: Information Technologist \\
\\
An information specialist would like to create/register a new conformance profile using an editor. The editor interacts with a conformance profile registry or repository that stores conformance profiles. \\
The editor should guide developers to be able to develop well-formed conformance profiles. The editor should allow development of new conformance profiles from existing ones (e.g. copy an existing profile and extend). \\
The editor should be able to register a conformance profile in the registry/repository. \\ |
| *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} |