Showing posts with label blog post 5. Show all posts
Showing posts with label blog post 5. Show all posts

Tuesday, February 13, 2018

Tran - Object-oriented Database


Object-oriented database (OODB) refers to a database model in which information is presented in the form of objects rather than data such as integers, strings or real numbers. The database is managed by object-oriented database management system (also known as OODBMS).
The interest in this type of database come from the needs of design support systems such as computer-aided software engineering, computer-aided manufacture or computer-aided design. These applications require databases that can handle complex data, and provide high performance dictated by interactive system.
In OODB, every entity is an object. While similar objects can be classified to classes and sub classes. An object has characteristic which are referred to as attributes. To be called an OODBMS, it must be a database management system, and an object-oriented system. Mandatory features of an object-oriented system are complex objects, object identity, encapsulation, classes, inheritance, overriding, extensibility and computational completeness.
The implementation of OODB is similar to relational database in the 70s. A primary feature of an OODBMS is that accessing objects in the database is done in a transparent manner such that interaction with persistent objects is no different from interacting with in-memory objects. This is very different from using a RDBMS in that there is no need to interact via a query sub-language like SQL. OODBMS were originally thought of to replace RDBMS because of their better fit with object-oriented programming languages. However, high switching cost, higher efficiency of RDBMS when dealing with simple data and relationship, the inclusion of object-oriented features in RDBMS to make them ORDBMS, and the emergence of object-relational mappers (ORMs) have made RDBMS successfully defend their dominance in the data center for server-side persistence

Sources:
Obasanjo, D. (n.d.). AN EXPLORATION OF OBJECT ORIENTED DATABASE MANAGEMENT SYSTEMS.
Kim, W., Nicolas, J. M., & Nishio, S. (1990). Deductive and object-oriented databases: proceedings of the First International Conference on Deductive and Object-Oriented Databases (DOOD89), Kyoto Research Park, Kyoto, Japan, 4-6 December, 1989.

Dung,

Do you think that object-oriented database will soon replace relational database? Since relational database management system has many drawbacks such as the expensive of setting up and maintaining the database system, fast increase in complexity of information. 

Marino,
I agree with you that one of the greatest benefit of OODB is that objects are stored by classes and sub classes which make it easier for navigation, also give the system a better concurrency control.


Shaden,
During my co-op with the construction unit of PWD, I had a chance to use a database developed by Oracle Project Management to keep track of issues or change orders with clients. Files can be accessed, downloaded and edited from anywhere by people who involved in the project. Use of database in design offices really saved lots of time and money for owner and contractors.  

Dee Dee Strohl - Blog 5


Uses of databases in design offices

What is a database?
A database is a computerized system that stores information that can be easily searched and selected. It is a collection of records that contain one or more fields (pieces of data) about some entity (object). This can be used in many applications; like libraries keeping track of available and checked out books, or a company who’s stored all employee information. There are a few types of databases that can be used: flat, hierarchical, network, and relational. Though Excel can and is used for a plenty of projects in design offices (and beyond), using a database is more capable with respect to large, complex projects that contain a lot of data or pieces. Databases are also attractive because several people can access and edit information at the same time.
From a design office perspective:
From an architectural or engineering firm perspective, using a database could be helpful in several applications. A database could be created to keep all client information and the projects associated with them. From working in an engineering firm, I’ve seen that different clients have specific requirements for building design and construction. Having a database to contain all the client information and specifications would be helpful. Especially because you can search for distinct words/requirements in the database easily. The database, and thus the information, can be accessed remotely and files are easily backed up to prevent losing work and edits.
From an owner perspective:
With databases, it’s easier for owners to share information with design firms and track progress. It makes finding documentation on both ends easier. Besides having access to a database for the design process, owners could create a database to use once the building is construction and in use. Information about the performance of the building systems, building automation, or life cycle could be track by looking at past and present data.
From a general perspective:
Because databases are becoming more and more used, the sharing of information has gotten easier. Different firms and people can share their projects or technologies with the world through them, making processes easier and more efficient. Even throughout college, databases have made it easier to research for classes and papers. This is particularly seen from the Drexel Libraries system, which allows you to search thousands of articles and journals with just a few keywords. It can also be helpful from a marketing perspective because everything is easily accessible.

Sources:
 “Architectural File Management Systems and Database,” Human Service Solutions. Accessed 2/11/18. https://www.hswsolutions.com/work/case-studies/architecture-file-management-database/
“Database Definition,” The Linux Information Project. Accessed 2/11/18. http://www.linfo.org/database.html
“How to Better Manage Your Project Data,” Archsmarter. Accessed 2/11/18. http://archsmarter.com/manage-project-data/

COMMENTS:
Isaac Quelly:
It’s awesome that you got to look at the GSI project and database in its early stages. I see why it’s important for every step of the design and build process to be tracked and added to the database and how it could be troublesome if changes are made without the correct procedure. Do you think the PWD has done anything to keep this issue from occurring in projects? Do you think the implementation of this technology will continue? I know when I worked at the city people were hesitant to take on new procedures.
Luciana Tangari:
Like you, I know nothing about object oriented databases (I honestly barely understand the types of databases as a whole). The analogy you added to your post was very helpful in gaining a better understanding of OODMS and relational databases. It’s interesting that OODMS can handle such complex data but makes it easier to access. I’m still not completely sure I understand OODMS, but your post helped me at least gain a bit of knowledge on the topic.
Dung Tran:
Thanks for giving me an understanding of what a relational database is. I ready in Luciana’s post about OODMS so it was nice to read about the other side of the coin. It’s interesting that in this type of database tables can be defined with constraints or algorithms but also don’t have to be. The images you included also made your (and Darwen’s) explanation easier to understand.

B5- Database

Database

I think data is the real asset of an organization. We will most likely interact heavily with databases during our professional career. Core database concepts and practices are extremely durable, and are likely to serve us for years to come. So, a collection of related data organized for easy storage and retrieval in electronic form will dramatically increase the efficiency of processing and understanding them. Almost any construction firm or other company in this field of appreciable complexity has information management requirements that are hard to satisfy without using a database. Since construction process always involve multiple companies working together from different aspects, the arrangement of database allows a number of different kinds of applications to work with the same set of data. Database can also ensure that the data must always meet certain conditions, such as ‘the span can’t be entered twice,’ regardless of the measurement manipulating it. We can also get the benefits of its security and concurrency. We can control who is authorized to manipulate what and govern what types of activities can take place at the same time. A database can also prevent data loss since it has the character of backup and disaster recovery. The most important thing is it can present different users with customized views of the same data. For example, each of your subcontractors will only have access to the data you want them to read. This can avoid wrangling and protect your trade secret in some degree.

I want to share an experience as the support of my above opinions. I was working for a small energy company for my first co-op cycle. Their duty is to re-design old structure's HVAC (heating, cooling and ventilating) system. I was involved in both field work and engineering design process. Their data managing techniques are relatively primary. They are collecting data from site investigation manually and I have to spend two hours per day for inputting them into computer. They do not process raw data before modeling or designing even though it is easy to be done on excel. I always need to convert units of the data for different design purpose. There are thousands of folders on their server and it always consumes a lot of time to find the proper one. These make their working efficiency lower than it should be. If they have a database that can perform all of the advantages as discussed in the first paragraph, their business will grow a lot faster and their work quality will increase a lot.
Comments:


Uses of databases in design offices
Shaden
We were doing the same topic. I am more focusing on database’s advantages while you made good efforts on illustrating the functions of database. You made a comparison between excel and database. This is really helpful to me since these two are having similar format and I sometimes confused about them.

SQL – What is it and why is it important?
Thomas
This is an informative and interesting post. I have only heard of database but I never know that there is a thing playing key roles interacting with elements in a database. I am taking a construction management course and I am taught to use Procore. It is an online software that the architect, engineer, GCs, owners can share and modify data. I think this platform is a good example of SQL. You can take a look of it if you are interested.

Object Oriented Database
Sherry
I like the graphs you used to help us to have a better understanding of object oriented databases. I have also read the original articles you listed in references. They are informative and helpful.

Monday, February 12, 2018

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.