Monday, February 12, 2018

B5 - Object-oriented databases


Databases are simply a compendium of information that are more easily accessed by organizing it into comprehensible packages or categories that can be related to keys throughout the system.  There are myriad types of models used for this process and some of the common logical data models can be seen below:

  • Hierarchical database model.
  • Network model.
  • Relational model.
  • Entity–relationship model. Enhanced entity–relationship model.
  • Object model.
  • Document model.
  • Entity–attribute–value model.
  • Star schema
A large extent of these utilize tables to store information and much of it works like a digital ladder, especially hierarchical based ones.  To examine the object-oriented approach, this concept allows for a more direct, and therefore faster retrieval of the data requested.  This task is completed by associating the elements with a particular language or often a visual graphic.  The required parameters for this are: class of data, extensibility, inheritance, and persistence.  These are general guidelines of all database management systems (DBMS's) though the object oriented method allows for a more user-friendly process and interface, while also allowing the necessary maintenance and upgrading of the system to be feasible for the programmers.


Comments:


Luciana,

I found the point of superimposing the OODB approach onto relational schema very interesting and would like to see how this is done.  I'm sure the original integration may be challenging, but the idea of updating a system with a new type of DBMS is an exciting one considering how much time it would save compared to creating a new one all-together.


Jianfeng,

You brought up some very good points on the collection of data, though I think much of databases are the organization and eventual use of said data.  There are numerous methods for this, of course, as are there for the collection as you have mentioned.


Chris,

I agree that databases are useful for all of the purposes listed above.  I think it would be very beneficial for not only the construction side of things, but for the design world as well if the paths for databases were simplified enough to be easily understood yet had the breadth needed for numerous request types.  For example, if someone within a firm wants to look up a similar detail for a previous job they had and re-purpose a model of special component then it can sometimes be a virtual nightmare to find exactly where it is if you are lacking the exact job information.  Using DBMS's such as object oriented databases they could potentially assign particular objects to category for easier retrieval based on what they know such as the type of room the model would be in, or perhaps its general specifications.  

 

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.