2005
DOI: 10.1007/11431855_1
|View full text |Cite
|
Sign up to set email alerts
|

Conceptual Schema-Centric Development: A Grand Challenge for Information Systems Research

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
24
0

Year Published

2006
2006
2010
2010

Publication Types

Select...
6
3

Relationship

0
9

Authors

Journals

citations
Cited by 50 publications
(35 citation statements)
references
References 36 publications
0
24
0
Order By: Relevance
“…In fact, this has been identified as one of the key problems to be solved for achieving the goal of automating information systems building [13].…”
Section: Fig 1 Conceptual Schema About Employees and Their Categoriesmentioning
confidence: 99%
“…In fact, this has been identified as one of the key problems to be solved for achieving the goal of automating information systems building [13].…”
Section: Fig 1 Conceptual Schema About Employees and Their Categoriesmentioning
confidence: 99%
“…Therefore, if any change is found out after the implementation, designers must start the whole process from the early stages, thereby dramatically increasing the overall cost of data warehouse projects. As stated by Olivé [7], this main drawback comes from the little importance given to the informative function of the information system, that is, to the definition of queries at the conceptual level that must be provided to the users in order to satisfy their information needs. To overcome this drawback in the data warehouse scenario, multidimensional queries must be defined at the conceptual level.…”
Section: Introductionmentioning
confidence: 99%
“…Several authors claim that MDD improves the efficiency when developing a software system [17,18]. According to [19,20,21] the conceptual models that describe the system are eventually easier to specify, understand, and maintain that the underlying programming code; the complexity is addressed and solved in the problem domain without technological issues; and solutions are not tied to specific implementation technologies. In the context of DSL development, language requirements are formally described using models and DSL artifacts are generated from them [22].…”
Section: Motivationmentioning
confidence: 99%