Using Design Patterns to Teach Conceptual Entity Relationship (ER) Data Modelling

Relational databases are core to the development of information systems. Designing and presenting a quality conceptual Entity Relationship (ER) data schema to model the entities, attributes and relationships in such a database is equally important. Context and assumptions play an important role in the construction of these schemas. University students have limited real-world experience and typically struggle with the construction of database schemas. Case studies are used to provide students with functional details and context. Patterns are considered useful to transfer best practices and expert knowledge from experts to novice users. This paper proposes the use of patterns to teach ER data modelling to second year Systems Analysis and Design (SAD) students. An example ER pattern for a Point-of-Sales (POS) system is proposed with one possible context adjustment. Assumptions, functional requirements and business rules form part of the proposed pattern to explain the different contexts in which the pattern could be applied as well as the effect that these context adjustments will have on the ER data model. Guidelines are given to assist lectures with using the pattern to teach their students conceptual ER data modelling.