Showing posts with label Week 6. Show all posts
Showing posts with label Week 6. Show all posts

Tuesday, February 9, 2016

B5: Group C - Mridul Chulet


In simple definition object oriented databases are databases that stores their contents as objects. Furthermore, they support the modelling and creation of data stored as objects. As the name suggests, the fundamental feature of Object oriented databases is allowing the definition of items, which are not the same as expected database objects [1]. Objects, in an object oriented database, reference the capacity to add to an object, then characterize and name it. The object can then be referenced, or called later, as a unit without getting into its complexities [2]. The same can be noticed in objects used in object-oriented programming . 

For example, a car engineer is a perfect example for Object oriented database. An engine is made up of several components: the main cylinder block, the exhaust system, intake manifold, etc [3]. But, when all of these components are combined altogether they form an engine. Similarly, when writing a program one can characterize a several segments, for instance, a vertical line intersecting a perpendicular horizontal line while both lines have a graded measurement [3]. This object can then later transformed into a diagram or a graph. 

There are several advantages of using object oriented database. First, it assures the system will enjoy longer life with small maintenance costs. The main reason for the long longevity is its behavior can be reused and implemented into new behaviors. Second, it allows real-world modeling. Objects are organized into classes of objects and there objects are associated with behaviors. The result is a model which is based on objects, rather than on data. Lastly, it provides improved reliability and flexibility than the existing systems because new behaviors can be built from the exciting objects [1]. As far the disadvantages are concerned, there are not much. The main disadvantage of object oriented database is that it is yet to be accepted by major companies and is not a technology [1].   

In conclusion, object oriented database approach will be really helpful when programming and processing tasks for intelligent building. One of the main reasons is the seamless integration of operating systems and AI expert system shells which in turn makes is easier to share data or software components or products.

References:
1)    http://ecomputernotes.com/database-system/adv-database/object-oriented-database-oodb
2)    http://searchoracle.techtarget.com/definition/object-oriented-database-management-system
3)    https://www.techopedia.com/definition/8639/object-oriented-database
    
 Comments:
 
Hamad Al-Hajri,
I really enjoyed reading your post and how you separately wrote of brief description of uses of databases in construction firms. All the statements you wrote are correct and make sense. I really like how databases are good estimators of wealth, construction time, track materials and performance. It will not only help save time, but it will also help check for errors or avoid any mistakes. But, object oriented approach is yet to be accepted by the major firms. Overall your post was concise and provided with helpful information.



Hatim Amiji,

        Great post. I had no idea about SQL and its importance before reading your post. I completely agree with your view point towards SQL. I feel like SQL helps to define relational databases models easily and helps to explicitly define the relationships. This will make it easier for architects and engineers to extract data and use the data from AutoCad or REVIT databases. Overall, I really enjoyed reading your article and it was very informative.



Derek Zaccheo - B5 - Group A

Relational database is a database system where the information is stored as a relational model of data. This means that you can store and retrieve data without knowing all the back end coding for the data. This method was created by E. F. Codd back in 1970 and has been widely used to this day. To further simplify relational databases. If you have a table with two columns in it and you wanted to change the one of those columns then it would delete the entire table without a relational database. With a relational database it would store those columns as two separate tables and then will allow you to manipulate columns individually without having to delete the whole table. Structured Query Language or SQL is the language used in most relational databases. SQL became the standard language to use back in 1986 and was developed in the 70's by Donald Chamberlin and Raymond Boyce.

The relational database is built in two different stages, the logical data model is created first and then the physical data model is created afterwards. The logical data model allows you to create a layout for the design of the entire database itself. The physical data model creates the data tables themselves and the columns and rows. These databases use key terms to define the tables. Entity is information that is needed from the real world and the information topic that you want to store data on. The attribute is used to detail information about a certain entity instance or some information that you want to track. A primary key is used to identify certain entities which means that every entity will have a different primary key. A primary key can be one attribute or it can contain several depending on what the user wishes and the values in the primary key have to have a value in them they can never be blank. Before relational databases they used tab delimited files. These differed from relational databases because every entry is separated by certain characters. This causes each entry to contain many pieces of information in it.

References:
https://en.wikipedia.org/wiki/Relational_database
https://en.wikipedia.org/wiki/SQL
http://www.dummies.com/how-to/content/knowing-just-enough-about-relational-databases.html
http://computer.howstuffworks.com/question599.htm

Comments:
Comment on Gary Reiff's post
Comment on Rebecca's post