 |
Page History
| Scrollbar | ||
|---|---|---|
|
...
| Page info |
|---|
...
|
Initial Analysis:
Item | Information/Response |
|---|---|
Date: | 01/26/2010 |
...
Requirement # unique id <SemConOps Initiative>.<analysts |
...
initials><requirement |
...
number> |
...
|
...
Init1dbw1 |
...
| Init3bes19 |
Originator/Customer's |
...
Name |
...
: |
...
John |
...
Koisch, |
...
Paul |
...
Boyes, |
...
Linda Schmandt |
Originator/Customer's |
...
Company |
...
: |
...
Guidewire |
...
Architecture, |
...
Guidewire |
...
Architecture, |
...
University |
...
of |
...
Pittsburgh | |
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: |
...
|
...
WSDL) |
...
to a |
...
conformance |
...
profile. |
...
|
...
tool |
...
that |
...
takes |
...
the |
...
implementation |
...
artifact |
...
(e.g. |
...
WSDL) |
...
and confromance |
...
profile |
...
of |
...
interest |
...
as |
...
inputs |
...
and |
...
generates |
...
a |
...
report |
...
on |
...
deviations/overlaps. |
...
|
...
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 |
...
and |
...
a |
...
reviewer |
...
for |
...
further |
...
detailing |
...
the |
...
requirement |
...
for |
...
use |
...
case |
...
development. |
...
John |
...
Koisch |
...
and/or |
...
Paul |
...
Boyes |
...
can |
...
be |
...
contacted |
...
for |
...
architect. |
...
Linda |
...
Schmant, |
...
leading |
...
SAEFE/ |
...
ECCF small |
...
group, |
...
can be |
...
contacted |
...
as |
...
a |
...
reviewer. |
...
| Scrollbar | ||
|---|---|---|
|
