Difference between revisions of "Template Page"

From Scube-casestudies
Jump to: navigation, search
 
Line 10: Line 10:
  
 
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
 
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
−
|+ Table BG1. Business Goal ALERT-BG1<br>
+
|+ Table BG1. Business Goal ID<br>
 
|-
 
|-
 
! Field  
 
! Field  
Line 16: Line 16:
 
|- style="background:#f0f0f0; color:black"
 
|- style="background:#f0f0f0; color:black"
 
! UniqueID  
 
! UniqueID  
−
| ALERT-BG1
+
| ID
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Short Name  
 
! Short Name  
−
| Enable efficient duplicates identification<br>
+
| <br>
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Type  
 
! Type  
Line 25: Line 25:
 
|- 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>
+
| <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>
+
| <br>
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Involved Stakeholders  
 
! Involved Stakeholders  
−
| Customer, Gatekeeper<br>
+
| <br>
−
|- style="background:white; color:black"
 
−
! Conflicts
 
−
| Poor detection could ruin the process.<br>
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Priority of accomplishment  
 
! Priority of accomplishment  
−
| Should have<br>
+
| <br>
 
|}
 
|}
  
Line 47: Line 44:
  
 
== Scenarios==
 
== Scenarios==
−
ALERT scenarios
+
The scenarios
  
  
 
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
 
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
−
|+ Table S1: Scenario ALERT-S1.1
+
|+ Table S1: Scenario ID
 
|-
 
|-
 
! Field  
 
! Field  
Line 57: Line 54:
 
|- style="background:#f0f0f0; color:black"
 
|- style="background:#f0f0f0; color:black"
 
! UniqueID  
 
! UniqueID  
−
| ALERT-S1.1
+
| ID
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Short Name  
 
! Short Name  
−
| Detect possible duplicate issues at creation<br>
+
| <br>
−
|- style="background:white; color:black"
 
−
! Brief Description
 
−
| The Customer (or developer) enters and describes an issue<br>
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Related To  
 
! Related To  
−
| ALERT-BG1<br>
+
| <br>
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Involved Actors  
 
! Involved Actors  
−
| Customer<br>
+
| <br>
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Detailed Operational Description  
 
! Detailed Operational Description  
−
| The Customer enters an issue. If a potential duplicate is spotted, he is asked to check it. A gatekeeper is notified of the new issue.<br>
+
| <br>
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Problems and Challenges  
 
! Problems and Challenges  
−
| Notify the Customer on time, so he can validate it's a duplicate.<br>Good quality detection.<br>
+
|<br>
−
|- style="background:white; color:black"
+
<br>
−
! Business Trigger
 
−
| Customer encounters an issue, and reports it. <br>
 
−
|- style="background:white; color:black"
 
−
! Preconditions
 
−
| An issue tracking system is installed, and ALERT is configured to retrieve information from it. <br>
 
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
−
! Priority
+
! Additional Material
−
| Should have <br>
+
| <br>
 
|}
 
|}

Latest revision as of 16:38, 6 June 2011

Description

Case study Description

Business Goals and Domain Assumptions

Business Goals and the Domain Assumptions for the current case study.

Business Goals

Table BG1. Business Goal ID
Field Description
UniqueID ID
Short Name
Type Business Goals.
Description
Rationale
Involved Stakeholders
Priority of accomplishment

Domain Analysis

Strategic Dependency Model and Context Diagram

Domain Model

Scenarios

The scenarios


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


Additional Material
Retrieved from "https://scube-casestudies.deib.polimi.it/index.php?title=Template_Page&oldid=29271"