As ELI's system's manager it has been brought to my attention that a design development of a DBMS is necessary to create so department managers such as purchasing, operations, marketing, and personnel may be convinced DBMS is ideal. Designing a database follows a general rule of stage analysis in:
Classification of information
Relationship between information
Transactions among data entities
Rules of identity
There are two stages in creating a database design: data and functional model. The data model is the actual data and how it is managed. The functional model decides how data is supposed to be accessed, processed, and queried. In order to design the data model, the following steps have to be followed, (taken from the Information Technology Services page of the University of Austin) (2004):
Identification of data objects and relationships: this is the analytical stage and data entities are given meaning through the flow of information in the system.
Drafting initial Entity-Relationship diagram with entities and relationships: the relationships between various data entities are established and documented using an Entity-Relationship diagram.
Refining the Entity-Relationship diagram: Entity-Relationship diagram is further refined by removing ambiguities and repetitions
Add key attributes to the diagram: from the former step, the Entity-Relationship diagram is enhanced along with incorporating key attributes of data entities (class diagrams).
Adding non-key attributes: non-key attributes are extras and may also be repeated in various entities.
Diagramming Generalization Hierarchies: a diagram is generalized with hierarchies in terms of security and data relativity is set.
Validating the model through normalization: database is normalized to reduce discrepancies and when in motion between data entities.
Adding business and integrity rules to the Model: database becomes more than a collection of data.
The process of normalization in a database is...