Business Rules and Data Models

Insert Name

Insert Course

Insert Date

Business Rules and Data Models Big organizations like universities, colleges, banking and hospitals with large amount of data require a software that is able to organize the data and in the database. Therefore the primary use of a database management system is its ability to collect data, store and transmute it into informative information that can help business make decisions. In order to make this possible, a database must be able to reduce data redundancy, inconsistency, upsurge security features, reliability and allow concurrent access of the data and improve accuracy and accuracy. The most important purpose of such a database is to provide automated methods that are able to develop, store and retrieve data more efficiently (Chapman, 2014). There are several drawbacks that are associated with the use of conventional file systems. This is because of the fact that most of such databases applications are developed on top of an existing file system. For this reason, the following problems are expected. To begin with, is redundancy; it is a situation where a lot of file formats together with duplicate information is found in different files (Gillenson, 2005). Accessing such data is difficult and the duplication of data in a file system may sometimes require a new program to be written. Another problem associated with conventional file systems is the difficult in file isolation. This is due to the multiple files and formats in the system that makes it difficult to isolate files from each other (Chapman, 2014). There is also the issue of integrity which is evident in case there is need to add a new control in the file or change the existing control in the file. According to Science, sometimes file system may fail due to electricity interruptions or other problems such as atomicity can also lead to inconsistence data (2006). An entity is any physically recognizable; it can be a person, a location, an employee, a car, a chair or anything tangible. Similarly, an entity can be defined as an object with conceptual presence. In must be available and tangible in reality. Examples of entities in the development of a college database that is to be used to maintaining information on students and the courses they have taken together with the respective teachers for each course include the college itself, the department, the department and the student. The database should be able to store and provide more data on students, such as the date the student was admitted and the date he or she is scheduled to complete, the department which the student belonged and the current year of study. Attributes are those properties that illustrate the entity (Gillenson, 2005). The give a better explanation of an entity in terms of exact details such as, the name of the student or teacher, the age of the student, the year of study, the address, the name number and name of the course the student has taken and the exact year the student is expected to leave college. According to Lightstone & Nadeau business rule is a statement that obliges and at the same time describes features of a business (2006). The main purpose of business rules is to form the business structure and also control the business behavior. Gillenson describes business rules to be atomic in nature with no any other category in that manner (2005). One of the best examples of business rule is marriage. The same case is evident in most business organizations in that, a manager must have a description of the kind of employee to marry and at what expense. Therefore, business rules are there to define the entities, attributes and show the relationship between them together with constrains. Such rules are there to guide employees focus on the objectives of the organizations and implement the necessary actions in the business environment (Science, 2012). The conceptual model in this kind of database is the ability to store information about every student in the college. In such a conceptual model, the most important features of the attributes that are able to enhance definition and revelation of entities involved. A good conceptual model does not need inventory of the entire population in the model, or rather; it should have some recognizing concepts to complete the system automatically (Gillenson, 2005). On the other hand, a physical model of database refers a single rational model instantiated in a specific product of database management in the specific system. It describes implementation specifics which can part of a particular product and database arrangement criteria. It usually involves the construction of index which determines the alternative key, physical storage and the controls (Science, 2012).

References
Chapman, R. J. (2014). The Rules of Project Risk Management: Implementation Guidelines for Major Projects. Scott, Foreman.
Gillenson, M. L. (2005). Fundamentals of Database Management Systems. Hoboken, NJ: Wiley.
Lightstone, S., & Nadeau, T. (2006). Database Modeling & Design: Logical Design. Amsterdam: Elsevier.
Science, A. I. (2012). Conceptual, Logical, Physical Models. Retrieved from www.aisintl.com: http://www.aisintl.com/case/CDM-PDM.html.

.