Difference between revisions of "Bug Resolution Case Study"

From Scube-casestudies
Jump to: navigation, search
(Created page with "==Description== Case study Description ==Business Goals and Domain Assumptions== Business Goals and the Domain Assumptions for the current case study. === Business Goals ==...")
 
Line 5: Line 5:
 
==Business Goals and Domain Assumptions==
 
==Business Goals and Domain Assumptions==
  
−
Business Goals and the Domain Assumptions for the current case study.  
+
Business Goals for the current case study.  
  
 
=== Business Goals ===
 
=== Business Goals ===
  
 
{| 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 ID<br>
+
|+ Table BG1. Business Goal BUG-BG1<br>
 
|-
 
|-
 
! Field  
 
! Field  
Line 16: Line 16:
 
|- style="background:#f0f0f0; color:black"
 
|- style="background:#f0f0f0; color:black"
 
! UniqueID  
 
! UniqueID  
−
| ID
+
| BUG-BG1
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Short Name  
 
! Short Name  
−
| <br>
+
| Enable efficient duplicates identification
 
|- 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  
−
| <br>
+
| Help developers and gatekeepers to manage issues. Developers should not work on duplicates, but instead access all duplicates 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.
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Rationale  
 
! Rationale  
−
| <br>
+
| Developers lose time with duplicates. Duplicate entries should instead help to get more complete information.
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Involved Stakeholders  
 
! Involved Stakeholders  
−
| <br>
+
| Customer, Gatekeeper
 +
|- style="background:white; color:black"
 +
! Conflicts
 +
| Poor detection could ruin the process.
 +
|- style="background:white; color:black"
 +
! Priority of accomplishment
 +
| Should have.
 +
|}
 +
 
 +
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
 +
|+ Table BG2. Business Goal BUG-BG2<br>
 +
|-
 +
! Field
 +
! Description
 +
|- style="background:#f0f0f0; color:black"
 +
! UniqueID
 +
| BUG-BG2
 +
|- style="background:white; color:black"
 +
! Short Name
 +
| Enable efficient issues resolution
 +
|- style="background:white; color:black"
 +
! Type
 +
| Business Goals.
 +
|- style="background:white; color:black"
 +
! Description
 +
| As much as possible relevant information should be provided in order to resolve an issue.
 +
|- style="background:white; color:black"
 +
! Rationale
 +
| The resolution of an issue requires an appropiate provision of relevant information, timely and content-based
 +
|- style="background:white; color:black"
 +
! Involved Stakeholders
 +
| Developer, Leader, Gatekeeper
 +
|- style="background:white; color:black"
 +
! Conflicts
 +
| None.
 +
|- style="background:white; color:black"
 +
! Priority of accomplishment
 +
| Must have.
 +
|}
 +
 
 +
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
 +
|+ Table BG3. Business Goal BUG-BG3<br>
 +
|-
 +
! Field
 +
! Description
 +
|- style="background:#f0f0f0; color:black"
 +
! UniqueID
 +
| BUG-BG3
 +
|- style="background:white; color:black"
 +
! Short Name
 +
| Reduce emails, increase relevance
 +
|- style="background:white; color:black"
 +
! Type
 +
| Business Goals.
 +
|- style="background:white; color:black"
 +
! Description
 +
| Developers get a lot of information by emails, and it begins difficult to select which one is relevant. ALERT should send only relevant information to developer. The notifications can be customized with custom rules, or be integrated in standard ALERT process.
 +
|- style="background:white; color:black"
 +
! Rationale
 +
| Developers get too many emails and would save time and do not miss important information, if they get relevant notifications.
 +
|- style="background:white; color:black"
 +
! Involved Stakeholders
 +
| Customer, Gatekeeper
 +
|- style="background:white; color:black"
 +
! Conflicts
 +
| Notifications need to be relevant.
 +
|- style="background:white; color:black"
 +
! Priority of accomplishment
 +
| Must have.
 +
|}
 +
 
 +
{| cellspacing="0" cellpadding="5" border="1" align="center" style="background:#cccc99;color:black;width:80%;"
 +
|+ Table BG4. Business Goal BUG-BG4<br>
 +
|-
 +
! Field
 +
! Description
 +
|- style="background:#f0f0f0; color:black"
 +
! UniqueID
 +
| BUG-BG4
 +
|- style="background:white; color:black"
 +
! Short Name
 +
| Accelerate issue distribution
 +
|- style="background:white; color:black"
 +
! Type
 +
| Business Goals.
 +
|- style="background:white; color:black"
 +
! Description
 +
| A new issue has been entered in the system and a developer and/or leader should be informed about the issue as soon as possible.
 +
It includes the situation that the sequence of interactions with the different information sources should be considered as a whole.
 +
It considers that the issue duplicates for this issue are resolved, i.e. this issue should not be considered as a duplicate issue.
 +
|- style="background:white; color:black"
 +
! Rationale
 +
| The information about a new issue should be spread over all relevant people (it might be only one) as soon as possible in order to create awareness about that issue, its consequences and urgency (for resolving).
 +
This approach decreases the information overloaded.
 +
|- style="background:white; color:black"
 +
! Involved Stakeholders
 +
| Developer, Leader
 +
|- style="background:white; color:black"
 +
! Conflicts
 +
| None
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
! Priority of accomplishment  
 
! Priority of accomplishment  
−
| <br>
+
| Must have.
 
|}
 
|}
  

Revision as of 09:16, 22 September 2011

Description

Case study Description

Business Goals and Domain Assumptions

Business Goals for the current case study.

Business Goals

Table BG1. Business Goal BUG-BG1
Field Description
UniqueID BUG-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 duplicates 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 lose 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.
Table BG2. Business Goal BUG-BG2
Field Description
UniqueID BUG-BG2
Short Name Enable efficient issues resolution
Type Business Goals.
Description As much as possible relevant information should be provided in order to resolve an issue.
Rationale The resolution of an issue requires an appropiate provision of relevant information, timely and content-based
Involved Stakeholders Developer, Leader, Gatekeeper
Conflicts None.
Priority of accomplishment Must have.
Table BG3. Business Goal BUG-BG3
Field Description
UniqueID BUG-BG3
Short Name Reduce emails, increase relevance
Type Business Goals.
Description Developers get a lot of information by emails, and it begins difficult to select which one is relevant. ALERT should send only relevant information to developer. The notifications can be customized with custom rules, or be integrated in standard ALERT process.
Rationale Developers get too many emails and would save time and do not miss important information, if they get relevant notifications.
Involved Stakeholders Customer, Gatekeeper
Conflicts Notifications need to be relevant.
Priority of accomplishment Must have.
Table BG4. Business Goal BUG-BG4
Field Description
UniqueID BUG-BG4
Short Name Accelerate issue distribution
Type Business Goals.
Description A new issue has been entered in the system and a developer and/or leader should be informed about the issue as soon as possible.

It includes the situation that the sequence of interactions with the different information sources should be considered as a whole. It considers that the issue duplicates for this issue are resolved, i.e. this issue should not be considered as a duplicate issue.

Rationale The information about a new issue should be spread over all relevant people (it might be only one) as soon as possible in order to create awareness about that issue, its consequences and urgency (for resolving).

This approach decreases the information overloaded.

Involved Stakeholders Developer, Leader
Conflicts None
Priority of accomplishment Must have.

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=Bug_Resolution_Case_Study&oldid=134713"