Difference between revisions of "Template Page"

From Scube-casestudies
Jump to: navigation, search
Line 9: Line 9:
 
=== Business Goals ===
 
=== Business Goals ===
  
{| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
+
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
|+ Table BG1. Business Goal ID
+
|+ Table BG1. Business Goal ALERT-BG1<br>
!Field !! Description
+
|-
 
+
! Field  
 +
! Description
 
|- style="background:#f0f0f0; color:black"
 
|- style="background:#f0f0f0; color:black"
! UniqueID
+
! UniqueID  
||ID
+
| ALERT-BG1
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Short Name
+
! Short Name  
|  
+
| Enable efficient duplicates identification<br>
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Type
+
! Type  
 
| Business Goals.
 
| Business Goals.
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Description
+
! 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.<br>
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Rationale
+
! Rationale  
|  
+
| Developers loose time with duplicates. Duplicate entries should instead help to get more complete information.<br>
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Involved Stakeholders
+
! Involved Stakeholders  
|  
+
| Customer, Gatekeeper<br>
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Conflicts
+
! Conflicts  
|
+
| Poor detection could ruin the process.<br>
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Supporting Material
+
! Supporting Material  
|  
+
| <br>
 
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
! Priority of accomplishment
+
! Priority of accomplishment  
|  
+
| Should have<br>
 
|}
 
|}
  

Revision as of 16:11, 6 June 2011

Description

Case study Description

Business Goals and Domain Assumptions

business goals and the domain assumptions

Business Goals

Table BG1. Business Goal ALERT-BG1
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.
Supporting Material
Priority of accomplishment Should have

Domain Assumptions

the tables containing the domain assumptions

Table DA1. Assumption ID
Field Description
UniqueID ID
Short Name
Type Domain assumption
Description
Rationale
Involved Stakeholders
Conflicts
Supporting Material
Priority of accomplishment

Domain Analysis

Strategic Dependency Model and Context Diagram

Domain Model

Scenarios

the list of the scenarios


Table S1: Scenario ID
Field Description
UniqueID ID
Short Name
Related To
Involved Actors
Detailed Operational Description
Problems and Challenges
Additional Material