2. To add to your talk about email, which is an easy example of unstructured data. Our hectic inboxes might be arranged by date, time or size. But would it would also be arranged by exact subject and content, with no deviation or spread if it were truly fully structured. That would most likely be impractical, since people do not usually speak specifically about just one subject, even if it is in a focused emails.
3. I want to add to the excel information that you shared with the class. Spreadsheets would be considered structured data, they are easily scanned for information because it is properly arranged in a relational database system. The problem that unstructured data presents is due to size, most business interactions require a huge investment of resources to sift through and extract the necessary elements.
4. An Entity Relationship Diagram is a snapshot of data structures. An Entity Relationship Diagram shows entities or tables in a database and relationships between tables within that database. For a good database design it is pretty much essential to have an Entity Relationship Diagram. There are three basic elements in an Entity Relationship Diagram;
1. Entities are the "things" for which we want to store information. An entity can be a person, place, thing or event.
2. Attributes are the data we want to collect for an entity.
3. Relationships describe the relations between the entities.
5. It is a database design tool that offers a graphical picture if you will of database tables, the columns in tables and the relationships between those tables. With a neat organization of tables, table columns and flexible representation of cardinalities, ERD is extremely helpful in modeling databases that have a large amount of tables and with complex relationships in between. A