The Halpin Approach
Approaches to building sustainable database systems differ depending on the structure of such systems and the main goals to achieve. The Halpin approach implies utilizing a conceptual framework aimed at searching for informational needs (Halpin & Morgan, 2008). This model, as a rule, implies the first-cut design and is aimed at covering the needs of numerous users. One of the key objectives of this approach is to show how the entire individual organization functions to provide an adequate storage engine (Halpin & Morgan, 2008). This technique is also referred to as a conceptual scheme.
The Relational Approach
The relational approach, in turn, is a framework to adapt a database design to a real-world environment. According to Syverson and Murach (2016), “the job of the designer is to analyze the real-world system and then map it onto a relational database system” (p. 305). Tying to the specific needs of the organization forms the basis for working on such a structure. In the relative approach, the relationships between database parts are based on creating conditions for the input of each element by correlating it with the current conditions and needs of the system.
The Main Differences
The main differences between these approaches are in the environments that determine how databases are built. For the Halpin approach, the conceptual model involves creating a general framework that enables the organization to work. The relational approach, in turn, is environment-dependent and is not a generic technique to build a database but rather a method to tailor the required tasks to the needs of a particular environment. These distinctions should be considered when planning an appropriate database design for certain needs.
References
Halpin, T., & Morgan, T. (2008). Information modeling and relational databases (2nd ed.). Morgan Kaufmann.
Syverson, B., & Murach, J. (2016). Murach’s SQL server 2016 for developers. Mike Murach & Associates.