An approach to engineering the requirements of data warehouses

Prakash, Naveen; Gosain, Anjana

doi:10.1007/s00766-007-0057-x

Cited by 57 publications

(63 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We model [Pra08] the notion of 'conditions that call for decisions' through the concept of a goal. We view a goal as an aim or objective that is to be met.…”

Section: The Goal-decision-information (Gdi) Modelmentioning

confidence: 99%

“…The Requirements engineering view [Pra08] suggests that goals 'guide decisions'. So, we naturally get the second concept of the GDI model, that of a Decision.…”

Section: The Goal-decision-information (Gdi) Modelmentioning

confidence: 99%

“…In this paper, we will show that the Goal-Decision-Information or GDI approach [Pra04,Pra08] when supported by appropriate information elicitation technique promote a direct relationship between DW information contents and the decisions of interest. We propose four elicitation techniques, Ends analysis, Means analysis, Outcome Feedback analysis, and Critical Success Factor analysis.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Towards Better Fitting Data Warehouse Systems

Prakash¹,

Prakash²,

Sharma³

2009

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract. In order to produce data warehouse systems that reflect organizational decisional needs, development should be rooted in the goals and decisions of organizations. The goal-decision-information model and associated information elicitation techniques for decision making are presented. There are four main techniques, Ends analysis, Means analysis, Critical Success Factor analysis, and Outcome Feedback analysis. Using these, the requirements engineer is able to elicit the required information as well as the sub decisions of a given decision. The elicitation techniques are then applied to these sub decisions. The elicitation process ends when all decisions/sub decisions have been thus processed. A comparison of this approach is made with data base driven and ER driven development approaches to data warehouse development to show that it produces systems that fit well with decisional requirements.

show abstract

“…We model [Pra08] the notion of 'conditions that call for decisions' through the concept of a goal. We view a goal as an aim or objective that is to be met.…”

Section: The Goal-decision-information (Gdi) Modelmentioning

confidence: 99%

“…The Requirements engineering view [Pra08] suggests that goals 'guide decisions'. So, we naturally get the second concept of the GDI model, that of a Decision.…”

Section: The Goal-decision-information (Gdi) Modelmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Towards Better Fitting Data Warehouse Systems

Prakash¹,

Prakash²,

Sharma³

2009

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

show abstract

“…The role of Requirements engineering in developing Data Warehouses has been investigated only in the last decade or so [6][7][8][9][10][11][12][13]. Today, there is a body of opinion that uses goal oriented techniques [10,11,13,15,16] for determining data warehouse structure.…”

Section: Introductionmentioning

confidence: 99%

“…Today, there is a body of opinion that uses goal oriented techniques [10,11,13,15,16] for determining data warehouse structure. One goal-oriented approach [10,11,13] is based on the notion of the GoalDecision-Information diagram. This approach postulates that the decision making capacity is determined by organizational goals.…”

Section: Introductionmentioning

confidence: 99%

Decisions and Decision Requirements for Data Warehouse Systems

Prakash¹,

Prakash

Gupta

2011

Progress in Pattern Recognition, Image Analysis, Computer Vision, and Applications

Self Cite

View full text Add to dashboard Cite

Abstract.We develop the notion of a decision requirement as the pair where 'information' is that required by the decision maker to assess if the 'decision' is to be taken or not. It is shown that there are two kinds of decisions, imperative and managerial. The former are decisions about which transactional service out of a choice of transactional services is to be provided. Managerial decisions determine what infrastructure out of a set of possibilities is to be put in place. It is shown that a decision is the reason why a functionality of an information system is invoked. The notion of decision requirement is clarified through a decisional requirement meta model. This is supported by a decision and information meta model.

show abstract

Handling the Information Backlog for Data Warehouse Development

Prakash

2019

Lecture Notes in Computer Science

View full text Add to dashboard Cite

An approach to engineering the requirements of data warehouses

Cited by 57 publications

References 16 publications

Towards Better Fitting Data Warehouse Systems

Towards Better Fitting Data Warehouse Systems

Decisions and Decision Requirements for Data Warehouse Systems

Handling the Information Backlog for Data Warehouse Development

Contact Info

Product

Resources

About