Relational Database Theory - Deutsch - B5

Before diving directly into what "Relational Database Theory" is I think it is first important to fully comprehend how a database is defined, along with how Big Data is defined. 

In general, a database can be defined as any collection or storage of information that is valuable, organized, searchable and applicable. In other words, it allows for management of files and their records which can be searched, grouped, rearranged and cross-referenced to facilitate easy retrieval for its users. Databases can be organized in any number of ways that are most applicable for what is being structured. A new technique that is being used more commonly as of late, is combining separate databases into larger entities which are now defined as "data warehouses". This is done mostly to help assist in pattern recognition which just reinforces how important databases and data sources are. 

Next, there is Big Data. According to Cringely, "Big Data" can be defined as "the accumulation and analysis of information to extract meaning." Even though this definition is quite broad, I like how far it allows us to delve into how much data we use and rely on without even knowing or realizing that we do so. I feel as though Big Data is similar to the "data warehouses" I mentioned earlier. In the past, storage of data and the capability to analyze that data was expensive and not done as often. Ever since individual computers became a normalized thing, data collection and storage has become much easier and cheaper to keep records of. Big Data is important because it aids in predicting events, the safety of groups or individuals, problem solving and connecting seemingly unrelated events that would have never otherwise been noticed. 

BIM is similar to Big Data and data warehouses in the way that it is also its own "environment". What I mean is that we treat it like data warehouses when we combine separate Autodesk programs in order to complete a project and use them as cross references, as our guest speaker last week, Derek, had mentioned he does often. It is also used as Big Data in the way that it keeps and stores all information in an organized and applicable way that allows its files to be easily accessed and managed by all those who require it to do so. 

This takes me to Relational Database theory. As stated by Darwin "Relational database theory is built around the concept of a relation" which is meant to be taken from a mathematical standpoint so that any number of things can be more easily related. What is important to remember when thinking of this definition is that relationships between multiple characteristics or objects are relational and not exactly "equal to" and this can be shown most easily by using a table, or most specifically the tables given by Darwin himself:

This table does not depict a relation

This table does depict a relation

What is of utmost importance to note however, is that although the second picture does demonstrate relational data, it does not matter what order the columns and rows are shown in. This data in these tables shown can then be searched. When a this relational data is searched, it is called a "query". To output specific information, constraints dictated by the inputted "query statement" will be applied and this will produce the desired data. Microsoft makes a program named Access Database which allows you to set up your own relational tables and query it at the end. It can be done using any desired informational fields, whether large or small.
 Although I had never thought too much about databases until this term, this is now the second time I have come across it since we just used Microsoft Access in my AE T580 class to teach ourselves how to relate specific data we came up with ourselves in a simple way. As explained by Darwin the order in which we defined our relationships did not matter when we ran a query. Seeing this fact in action helped me understand relational database theory much better. 

Sources:

https://dvikan.no/ntnu-studentserver/kompendier/an-introduction-to-relational-database-theory.pdf

https://www.evernote.com/pub/aengineer/ae-510#st=p&n=b751f481-0f42-4f45-a51b-a77127a94351&t=ec0a31ef-f3b4-42b8-b58d-6ed4124da841

https://www.britannica.com/technology/database


Comments:

Dung Tran - 
I really like how you approach the main topic of relational databases by first defining databases in general. I did something similar in my post. I also think you did an exceptional job in explaining how the the math side of relational data, or the relational algebra, connects to the overall concept. I did not get the chance to check out Codd's research paper but it seems to be very helpful in understanding this broad and complicated theory.

Chris Thatch - 

I agree that databases are of utmost importance within the construction field, especially within the management aspect of things. I know that a lot more companies are making a bigger effort in going paperless in more recent years which would be very helpful when it comes to contributing to the databases already in existence. While this is more efficient, offices have found themselves actually using more paper. I wonder why this is, do you have any input? Also, could you define what RS Means is in a bit more detail? I have never heard of it but it seems to be quite important.

Jianfeng Xiao - 

Reading your post is very interesting. I like the examples you give that connect ways in which we use data readily available to us now through new technologies that make prior methods of achieving the same tasks obsolete. Data is such a useful tool when it comes to design because it allows for us to take what we know and apply it in smarter ways, hence smarter buildings and environments also! I will have to check out the articles you cited.