Bug Resolution Case Study
From Scube-casestudies
Contents
Description
Case study Description
Business Goals and Domain Assumptions
Business Goals for the current case study.
Business Goals
| 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. |
| 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. |
| 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. |
| 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
| Field | Description |
|---|---|
| UniqueID | ID |
| Short Name | |
| Related To | |
| Involved Actors | |
| Detailed Operational Description | |
| Problems and Challenges |
|
| Additional Material | |
