DATABASE MODELING
Naga Deekshith Baireddy
10000126405
CMP 553 B
Moses Niwe

Abstract
This article seeks to explain what database modeling is and how important it is for any organizations to create a custom model that will meet its requirements. The document therefore analyses the database model types and compares the different types that can be implemented. The factors looked at are the security features each applies and how much effort is needed to design and generate a suitable database for the organization. Issues relating to the cost of designing and generating an appropriate database will also be looked into. Finally the paper also assesses the pros and cons of every model type for the sake of arriving at the best model to be applied by the specific institution.
Introduction
Database modeling is a process used by organizations to determine and examine data demands needed to support the business processes within the range of corresponding information systems. This therefore lets the entire information technology professionals to simplify the database’s design and maintenance by enabling you to picture the needs and fix specific design issues. A database model is therefore described as the entire process from where a company identifies its needs about how it will store its information, designing and generating the database to the point where it will be used by the organization. Essentially, this is how the data will be captured, stored, retrieved and used by the organization. (Smith & Fingar, 2003)
List of the data-base Model types:
With the ever growing company needs by many companies to design and maintain perfect and secure database files that will be used by the organization to all the related records and even overrunning data, there emerged the need to come up with professional models of databases maintenance methods that will directly and automatically link file by creating relationships amongst the files. Discussed in this document are the different types of models. They include:
(i) Hierarchical Model
Here, record types are connected in a treelike structure. Perfect examples include students in a school might be grouped under a record detailing the subjects they take. There is a vertical kind of hierarchy of the main data and related data portions. This kind of database structure shows that records can contain information that will be continuously repeated, which is normally contained in the related data portions or segment. It ensures that it gathers a majority of the instances of the particular records together as a single type of record. The record types resemble the tables depicted in the any of the relational database model, alongside the particular records that are the equal of the rows. The hierarchical model uses Parent-Child Relationships to create links between these record types, which amounts to a 1: N mapping between record types. This is generally achieved by the use of trees, like the theories that are used in the relational database models. A perfect example is where a school institution may store data or information on a student, e.g. name, admission number, and subject department and performance index. (Krämer & Wegner, 1997)
The school can also store information about a student's parents, e.g. First Name, Last Name and workplace. The student and the parents information automatically result into a hierarchy given the data for the student is a representation of the parents’ data represents the parent or main segment. If a student has a one, it will definitely result in a one parent segment that has an association with the student data segment. In this hierarchical kind of database the parent-child relationship is 1 to several. This restricts a child segment to having only one parent segment. (Brodie, 1984)
(ii) Network Model
This entails the creation of arbitrary linkages of record types. An example is where students’ records might be linked on one hand to students’ departments and on the