Page History
...
Item | Information/Response |
---|---|
Date: | 01/26/2010 |
Requirement # unique id <SemConOps Initiative>.<analysts initials><requirement number> | Init1bes17 |
Originator/Customer's Name: | John Koisch, Paul Boyes, Baris Suzek Boyes |
Originator/Customer's Company: | Guidewire Architecture, Guidewire Architecture , Georgetown University |
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: |
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. |
...
Item | Description | Information/Response |
---|---|---|
Stakeholder Community: | Enter appropriate category of stakeholder from Primary Stakeholders:
| |
Requirement Type (required) | Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):
|
|
ConOp Initiative(s) |
|
|
High Level Use Case Summary) | Please write a short descriptive narrative use case; the steps or activities in this use case are usually the things the user wants to accomplish with the system (user/actor's goals). |
|
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 |