Difference between revisions of "Template Page"

From Scube-casestudies
Jump to: navigation, search
(Business Goals and Domain Assumptions)
(Domain Assumptions)
Line 38: Line 38:
 
! Priority of accomplishment  
 
! Priority of accomplishment  
 
| Should have<br>
 
| Should have<br>
|}
 
 
=== Domain Assumptions ===
 
 
the tables containing the domain assumptions
 
 
{| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
 
|+ Table DA1. Assumption ID
 
!Field !! Description
 
 
|- style="background:#f0f0f0; color:black"
 
! UniqueID
 
| |ID
 
 
|- style="background:white; color:black"
 
! Short Name
 
|
 
 
|- style="background:white; color:black"
 
! Type
 
| Domain assumption
 
 
|- style="background:white; color:black"
 
! Description
 
|
 
 
|- style="background:white; color:black"
 
! Rationale
 
|
 
 
|- style="background:white; color:black"
 
! Involved Stakeholders
 
|
 
 
|- style="background:white; color:black"
 
! Conflicts
 
|
 
 
|- style="background:white; color:black"
 
! Supporting Material
 
|
 
 
|- style="background:white; color:black"
 
! Priority of accomplishment
 
|
 
 
|}
 
|}
  

Revision as of 16:19, 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 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.
Priority of accomplishment Should have

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