Invoicing was quickly added as a use case, but it started to prove difficult because of data quality issues (yes, already back then; customers are a difficult bunch).
Integration started to become an issue, which proved to be a heavy concern, because the early database systems were mostly used as point solutions for the domain applications. However, the vision of enterprise israel whatsapp number data databases led to the triumph of SQL over network and indexed (ISAM/VSAM databases), because of the perceived flexibility of normalized databases over too-physical datamodels in older DBMSs.
In the seventies the so-called “DIKW Pyramid” started to appear everywhere:
Longlivetheux, CC BY-SA 4.0/Wikimedia Commons
The enterprise modeling visions also entered the code layers leading to object-oriented models (UML, OO) as well as OODBMS, which, however, failed to enter the mainline paths.
Construction and implementation of information systems was based on disciplines such as planning, governance, methods, involvement of business experts, and some technology (relational modeling, OO, etc.).
However, during the ’80s and ’90s, a realization spread itself around that these “siloes” were too difficult and too costly. New technologies such as mini-computers and personal computers, as well as OLAP and data warehousing, were thrown on the table to provide some relief for real business requirements.