A database is a platform that is used to store information of different entities in information technology. It is mainly used by institutions that deal with information of other entities and it is important that they store them for long term purposes. Examples of institutions that may use database include Schools, colleges, hospitals and humanitarian organization (Ming-quan, 2008). In every database, they need information about a specific factor and this is defined as an entity. The main entities found in an institution such as a college is age, place of residence, national identification number, and full names.
An entity will act as a general guide on how data should be stored. The importance of entities is that they keep the database organized, and easily understandable. The main purpose of age is to understand the age group that is mainly found in each level of the students. It helps to understand the culture that will mainly be seen at a certain level. Place of residence will help know where to go in case of emergencies. National identification number helps when it comes to accountability with the nation. In a case of any breaking of the law by any of the people involved with the institution, it is the schools responsibility to ensure that they can account for their identifications. Names help in differentiating the people in the institution through a precise specification (Ming-quan, 2008).
Delegate your assignment to our experts and they will do the rest.
Business rules are guidelines used to ensure that business is done efficiently and accordingly. The database uses these business rules to help come up with an easy to read the database. The rules can also be used by data management system to ensure that the database is well maintained. There are three types features that help implement the rules and can impact the structure of the database. They include Constraints which are the restrictions on the number of or type of data inserted in a column. Stored procedures are the steps required to insert or gain information from a database and triggers is the notification of a change in a database. They all affect the structure of a database because any change of implementation done of these features affects the database (Ram & Khatri, 2005).
A conceptual model of the database is known to be the simplest and easy to read. The entities are mainly named according to the business need. Entities of a college will include the full names, national identification number, names of the guardian, contacts of both the student and the guardians and the course being done. The needs are the guiding factor in the modelling of the database. Conceptual is used by many institutions due to its ease of using it and understanding the information that is put in it (Ram & Khatri, 2005).
A physical model of a database is known to be detailed and the type of information used is specific. It is mainly used as a guide in a data management system though it is advisable that one understands the type of data management system they have before considering the physical model. Many of the institutions that use this type of model are hospital since they tend to deal with precise information without any mistakes. The physical model is very precise on the type of data its stores. The data is expected to be very specific (Ram & Khatri, 2005).
In conclusion, it is important to understand the nature of business in order to come up with its database. It is through the understanding that a model is decided on. A model will help understand the type of entities that will simplify the type of data in the database. The structure will be affected by all these factors and also the rules implemented. Rules implementation will be determined by the features used in the database.
References
Ming-quan, F. A. N. (2008). Reflection on Construction of a College Database with Characteristics [J]. Journal of Dali University , 1 , 019.
Ram, S., & Khatri, V. (2005). A comprehensive framework for modeling set-based business rules during conceptual database design. Information Systems , 30 (2), 89-118.
