Showing posts with label attributes. Show all posts
Showing posts with label attributes. Show all posts

Tuesday, February 9, 2016

B5 - Group C - Sean Coffey - Object Oriented Databases

Object Oriented Databases


Before researching object oriented databases, I did not know what object oriented databases were and was not aware how they were extensively used for to enable BIM software. Object oriented databases simply put are databases made up of complex objects that are defined by simple data and algorithm attributes. These attributes can be edited and modified manually and automatically.


Differences from Other Databases


Object oriented databases are unlike traditional databases in some important ways. They contain simple and complex attributes while more traditional databases like relational databases only contain simple data. The simpler databases store data in tables that are often reference other tables to return useful information.


Advantages & Disadvantages
Object oriented databases have their advantages and disadvantages over other less complex and traditional databases. Some of the advantages include their programmability to act more intelligently and automatically than other databases. This is accomplished with the embed code and algorithms. This code and how the database interacts with other databases makes object oriented databases more complex and due to the increased complexity they are harder to maintain and edit. On the other hand, if object oriented databases are setup properly they require less maintenance, while more traditional databases require regular maintenance. Also object oriented databases are work better when implemented to communicate and interact with other databases.


BIM’s Use of Object Oriented Databases


One of the best ways to use object oriented databases is when programing CAD and BIM software. Autodesk leverages the advantages of object oriented databases to make the intelligent programs such as Revit. Object oriented databases are fundamental to how Revit acts parametrically. An example of how this database type is implemented in Revit is to create families that are intelligent and modifiable. Revit families are defined by simple and complex properties or attributes. Example simple attributes are the dimensions of a door. They can be quickly and easily modified by user to customize the door to match the actual door that will be installed into the real life building. While a complex attribute would be how the door interacts while placing the door on walls with different widths. The frame for the door has to have an intelligent algorithm that determines how the door will automatically modify its width to match the wall width. The use of object oriented databases makes Revit seemingly simple, work intelligently and nearly flawlessly.


References



http://www.comptechdoc.org/independent/database/basicdb/dataobject.html

Comments

Mohammed Alqallaf
http://ae-510-ay15-16.blogspot.com/2016/02/b5-mohammed-alqallaf-group-e.html

Bridget Frasca
http://ae-510-ay15-16.blogspot.com/2016/02/b5-group-d-frasca-uses-of-databases-in.html?showComment=1455059965158#c2225312694583606569

Monday, February 8, 2016

B5: Janet Tran Group A

  Relational Database Theory
   
In 1970 a mathematician Edgar F. Codd, published the concept that would allow people to access information from databases without having to know how they are structured. Common relational database software are Microsoft Access and Oracle. 

To understand the basic concepts there are a few key terms to identify. A database can be defined as one that contains one or more tables of information. The rows within a table are referred to as records and the columns are referred to as fields or attributes. A relational database requires two or more related tables. Sometimes in order to increase efficiency and reduce error normalizing data is required. This involves dividing information into multiple tables that are organized differently so that there is not redundant information. Primary keys are values within a field that are composed of all unique values. For instance if a table has fields: student identification number, age, and degree. The primary key in this case is student identification number because there is not repeated value, each student has a unique identification number. When normalizing data the tables are structured as either parent, child, or orphan. When two tables have an unequal relationship, the independent one is referred to as the parent and the dependent one is the called the child. However, if there a record within the child table that does not appear in the parent table, that record is called an orphan. The number of records in one table that can be related to the records of another is table is identified as cardinality

The major advantage and use of relational models is its uniformity. All value stored in a table is organized to comply with the same structure. That is each record (row) are formatted the exact same. However, the fields can be unique to each primary key. Additionally, data is only stored once and allows for more efficient storage of information. It also allows for better security since data can be organized into multiple tables. This separation allows one to limit access to certain tables.

Works Cited
[1] http://www-03.ibm.com/ibm/history/ibm100/us/en/icons/reldb/
[2]http://webs.wofford.edu/whisnantdm/Courses/CS101/PDF/Database/Relational_database_concepts.pdf


Student Comments
Comment on Schroeder's post
Comment on Redus' post