Are you in High School, College, Masters, Bachelors or Ph.D and need someone to help in your homework? We offer quality research writing help, All our papers are original, 0% plagiarized & uniquely written by our dedicated Masters specialists. My Essay Services is an experienced service with over 9 years experience in research writing and over 83,000 essays over the years. You will receive a plagiarism check certificate that confirms originality for any essay you order with My Essay Services

Sample Essay On Database Management Systems

The dilemma for most organizations when deciding which type of database management system to use is normally a two-pronged one. The most used DBMS are the object-oriented database management system (OODBMS) and the relational database management system (RDBMS). In deciding which DBMS system best suits an organization, it is important to analyze what each data model entails.

In RDBMS, the database consists of relations, whereas OODBMS consists of classes (SABĂU). Therefore, a relational database will have a relation known as STUDENT, with tuples that contain information on each STUDENT. On the other hand, an object-oriented database will have a class referred to as STUDENT with objects that contain information on each student.

In a relational database, the properties of the tuple must be the primitive type e.g. string, real, integer, etc. however, in the object-oriented database, the components of the object could be complex e.g. sets, objects, tuples, etc.

Relational databases strive to ensure that the independence of the data is maintained from applications. It is structured to separate normalized data from processing and to allow the processing not to be entirely defined so that ad-hoc requirements can be accepted. In object-oriented databases, the primary objective lies in data encapsulation, which in essence means that the data and the method are stored together. And thus, whereas RDBMS prioritizes data independence, OODBMS places emphasis on class independence (SABĂU).
In the case of an electronic health record (EHR) system, the major functionalities that will be required of such a system include:

Data modeling technique
The definitive way in which the database describes data, the relationships between two or more data sets and the constraints on the data it houses.

Data persistence
This determines whether the data can be stored for longer time frames until the applications using it reaches its conclusion.

Data sharing
Which obviously examines the possibility of multiple users being able to access the data simultaneously

Reliability
The safety of the data in case of software or hardware malfunction.

Scalability
This is whereby large quantities of data can be manipulated using simple easy to use applications.

Security and safety
Ensures that the data cannot be accessed by unauthorized personnel and that the data is in tandem with set guidelines on consistency and correctness.

Distribution
The ease with which data can be transferred from one user to the other and the visibility of such a transfer (Gotseva and Nimrawi).

In comparison, Object-Oriented Database Management Systems (OODBMS) can utilize the merits of both the design and the implementation of the applications running it (Saxena and Pratap). It is also very agile in handling complex data and guarantees high performance. In the EHR set up, this would be the ideal DBMS to use because of these highlighted features. The medical set would need a system that has improved functionality that allows seamless user interphase that allows most personnel to be able to access information on the DB as well as being able to transfer this information from station to station as may be required from time to time. Most personnel in the health organization will mainly be concerned with the user-level applications and not the intricate programming lexicon that has been discussed in this article. The average user will need a system that can allow him to input information, store and retrieve this information whenever he wants it. The system should employ practical user interphases for easy functionality.

References

Gotseva, Daniela and Loie Naser Mahmud Nimrawi. "COMPARISON BETWEEN OBJECT RELATIONAL AND OBJECT ORIENTED DATABASES." DataBase Management Systems (2012): 291-293.
SABĂU, Gheorghe. "Comparison of RDBMS, OODBMS and ORDBMS." Revista Informatica Economică (2007): 83-85.
Saxena, Vipin and Ajay Pratap. "Performance Comparison between Relational and Object-Oriented Databases." International Journal of Computer Applications (0975 – 8887) (2013): 6-10.