Integrating ERD and UML Concepts when Teaching Data Modeling

In this paper, we describe a teaching approach that evolved from our experience teaching in both the traditional database and systems analysis classes as well as a number of semesters spent team-teaching an object-oriented systems development course. Fundamentally, we argue that existing knowledge of structured systems development can and should inform our teaching processes when teaching object-oriented systems development techniques. We draw from an anecdotal industry example provided by one of our former students to illustrate the value of this approach given our perception that there is a need in practice today to easily shift from structured to object-oriented thinking.

[1]  Monica J. Garfield,et al.  The AMCIS 2003 Panels of IS Education-II: The Chicken and the Egg Debate: Positioning Database Content in the Information Systems Curriculum , 2004, Commun. Assoc. Inf. Syst..

[2]  Jeffrey A. Hoffer,et al.  An Examination of Procedural and Object‐oriented Systems Analysis Methods: Does Prior Experience Help or Hinder Performance?* , 1999 .

[3]  Anthony C. Bloesch,et al.  Data Modeling in UML and ORM: A Comparison , 1999, J. Database Manag..

[4]  Stéphane Bressan,et al.  Introduction to Database Systems , 2005 .

[5]  H. James Nelson,et al.  Old dogs and new tricks , 2002, CACM.

[6]  Peretz Shoval,et al.  Entity-Relationship and Object-Oriented Data Modeling-an Experimental Comparison of Design Quality , 1997, Data Knowl. Eng..

[7]  Sridhar P. Nerur,et al.  Revolution or Evolution: A Comparison of Object-Oriented and Structured Systems Development Methods , 2001, MIS Q..

[8]  George Wright,et al.  The Difficulties of Learning Object-Oriented Analysis and Design: An Exploratory Study , 2002, J. Comput. Inf. Syst..

[9]  C. J. Date.  An introduction to database systems (7. ed.) , 1999 .

[10]  Fred R. McFadden,et al.  Modern database management (4th ed.) , 1994 .

[11]  Cherri M. Pancake,et al.  The promise and the cost of object technology: a five-year forecast , 1995, CACM.

[12]  Kangde Yao,et al.  A Brief Guide to the Standard Object Modelling Language , 2000 .

[13]  Mary Beth Rosson,et al.  The Cognitive Consequences of Object-Oriented Design , 1990, Hum. Comput. Interact..

[14]  Peter P. Chen.  The Entity-Relationship Model: Towards a unified view of Data , 1976 .

[15]  Peter P. Chen.  The entity-relationship model: toward a unified view of data , 1975, VLDB '75.

[16]  Kent L. Beck,et al.  A laboratory for teaching object oriented thinking , 1989, OOPSLA '89.

[17]  H. James Nelson,et al.  Exploring the Difficulties of Learning Object-Oriented Techniques , 1997, J. Manag. Inf. Syst..

[18]  Bill C. Hardgrave,et al.  Object-oriented methods: current practices and attitudes , 1999, J. Syst. Softw..

[19]  Kendall Scott,et al.  UML distilled - a brief guide to the Standard Object Modeling Language (2. ed.) , 2000, notThenot Addison-Wesley object technology series.

[20]  Peretz Shoval,et al.  ADISSA: architectural design of information systems based on structured analysis , 1988, Inf. Syst..

[21]  Hirotaka Sakai.  Entity-Relationship Approach to Logical Database Design , 1983, ER.

[22]  Robert M. Curtice,et al.  The entity-relationship approach to logical database design , 1991 .

[23]  Heikki Topi,et al.  Modern Database Management , 1999 .

[24]  Peretz Shoval,et al.  FOOM: Functional and Object-Oriented Analysis and Design of Information Systems: An Integrated Methodology , 2001, J. Database Manag..