Software Pioneers 2002
DOI: 10.1007/978-3-642-59412-0_17
|View full text |Cite
|
Sign up to set email alerts
|

Entity-Relationship Modeling: Historical Events, Future Trends, and Lessons Learned

Abstract: Abstract. This paper describes the historial developments of the ER model from the 70's to recent years. It starts with a discussion of the motivations and the environmental factors in the early days. Then, the paper points out the role of the ER model in the Computer-Aided Software Engineering (CASE) movement in the late 80's and early 90's. It also describes the possibility of the role of author's Chinese culture heritage in the development of the ER model. In that context, the relationships between natural … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
24
0
8

Year Published

2004
2004
2024
2024

Publication Types

Select...
6
2
2

Relationship

0
10

Authors

Journals

citations
Cited by 52 publications
(32 citation statements)
references
References 11 publications
0
24
0
8
Order By: Relevance
“…One of the widely quoted advantages of the ER Model is its ability to communicate with end users [e.g. 6,10,17,33]. However field studies show that in practice, ER models are poorly understood by users, and in most cases are not developed with direct user involvement [21,22].…”
Section: The Entity Relationship (Er) Modelmentioning
confidence: 99%
“…One of the widely quoted advantages of the ER Model is its ability to communicate with end users [e.g. 6,10,17,33]. However field studies show that in practice, ER models are poorly understood by users, and in most cases are not developed with direct user involvement [21,22].…”
Section: The Entity Relationship (Er) Modelmentioning
confidence: 99%
“…The ER Model has undergone variety of changes and extensions [10] [11] from 60's to recent years. Schema diagrams were formalized in 1960's by Bachman [12].The Entity Relationship Model for conceptual data modelling was introduced by Chen [3] in 1976.The extended ER Diagram for logical design of relational databases is represented by Teorey et al [13] in 1986 where as mapping from extended EER models to the relational model is discussed by Lyngbaek and Vianu [14] in 1987, Markowitz and Shoshani [15] in 1992.Further numerous extensions for of its modelling capabilities have been proposed by Scheuermann et al [16] and Dos Santos et al [17] in 1979, Gogolla and Hohenstein [18] in 1991.The concept of generalization, specialization and aggregation introduced by Smith and Smith [19] in 1977 and expanded by Hammer and McLeod [20] in 1980.…”
Section: Related Workmentioning
confidence: 99%
“…A vast number of visual technologies have been applied in the business process modelling domain to capture graphical representations of the major processes, flows and data stores [11]. Examples include Entity-relationship models [19], Data Flow Diagrams [4], Aspect-oriented Modelling [2], Flowchart Models [17], Form Chart Approaches [8], Scenarios [10], Use Cases [6], Constraint Based Languages [11] and Integration Definition for Functional and workflow Modelling [21]. Despite their different visual approaches, most of these modelling technologies and their notations rely on the use of process flow or "workflow" structure to describe the business processes.…”
Section: Introductionmentioning
confidence: 99%