Difference between revisions of "Template Page"
From Scube-casestudies
(→Business Goals and Domain Assumptions) |
(→Domain Assumptions) |
||
Line 38: | Line 38: | ||
! Priority of accomplishment | ! Priority of accomplishment | ||
| Should have<br> | | Should have<br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
Revision as of 16:19, 6 June 2011
Contents
Description
Case study Description
Business Goals and Domain Assumptions
Business Goals and the Domain Assumptions for the current case study.
Business Goals
Field | Description |
---|---|
UniqueID | ALERT-BG1 |
Short Name | Enable efficient duplicates identification |
Type | Business Goals. |
Description | Help developers and gatekeepers to manage issues. Developers should not work on duplicates, but instead access all duplicated issue entries to get more description on the issue. Gatekeepers should be notified of possible duplicates. Customers should be notified when their entry is a possible duplicate. |
Rationale | Developers loose time with duplicates. Duplicate entries should instead help to get more complete information. |
Involved Stakeholders | Customer, Gatekeeper |
Conflicts | Poor detection could ruin the process. |
Priority of accomplishment | Should have |
Domain Analysis
Strategic Dependency Model and Context Diagram
Domain Model
Scenarios
the list of the scenarios
Field | Description |
---|---|
UniqueID | ID |
Short Name | |
Related To | |
Involved Actors | |
Detailed Operational Description | |
Problems and Challenges | |
Additional Material |
|