 |
Page History
| Scrollbar | ||
|---|---|---|
|
...
| Page info |
|---|
...
|
Initial Analysis:
Item | Information/Response |
|---|---|
Date: | 01/26/2010 |
...
Requirement # unique id <SemConOps Initiative>.<analysts |
...
initials><requirement |
...
number> |
...
|
...
Init1dbw1 |
...
| Init3bes17 |
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 |
...
developers |
...
to |
...
find |
...
conformance |
...
profiles that standardardize semantic and functional descriptions for services |
...
XSD). |
...
The |
...
registry/repository |
...
should |
...
provide |
...
services |
...
that |
...
support |
...
search |
...
capabilities |
...
stated |
...
in |
...
requirement: |
...
|
...
should |
...
provide |
...
service |
...
that |
...
support |
...
registration |
...
capability |
...
stated |
...
in |
...
requirement: |
...
...
...
...
...
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 | ||
|---|---|---|
|
