Class 2 | Week 6 | DAT601

Today we have received out project that will carry out until the end of the term, Todd has created his own scenario for us to produce database designs from, this concept carries some ambiguity with it but I get the feeling that the point of this is that most business situations can be ambiguous. After some review of the brief I have identified the overall structure of this database, there are still many wrinkles to iron out in terms of the relationships but this should prove a doable process once the core data the database needs to store is layed out in a plain format.

Considering the two week break we have ahead of us I want to get the bulk of milestone one completed in order to have the flexibility of editing my work as required in the final week before it is due.

Interesting concept for a project brief, should be fun.

Comments

Post a Comment

Popular posts from this blog

Class 2 | Week 9 | DAT601

Today's lesson pertains to more SQL language beginning with the GROUP by clauses, little examples are being shown on the projector for us, these kind of physical examples are a lot easier to digest than writing on the whiteboard. Group by must appear after the FROM and WHERE clauses, GROUP by groups rows into subgroups based on values of columns or expressions. Todd's example is used to group columns together to show a sum of total sales for a specific region. Another example of a group by rollup which is described as a niche function which caused some debate in class as to what it actually does. GROUP BY GROUPING SETS is used to allow multiple group-by clauses to operate in a single statement, GROUP BY GROUPING SETS is equivalent to the 'union' of two or more GROUP BY operation in the same result set. Next topic is Views within SQL, which is used to present the information data in a different point of view. This can simplify the access to specific information w...
Read more

Class 2 | Week 2 | DAT601

Image
Beginning this weeks second class Todd has provided an example document for our milestone one and is walking through it to help us understand the different types of tables he desires. Upon learning that this milestone is about 15 pages max I am feeling comfortable. After this he has continued with last weeks power point and explaining more conceptual database concepts in depth, including but not limited to: cardinality, weak vs strong entities, multiplicity constraints and so on. Below is some pictures from my teams brainstorming over our teams conceptual design done earlier today, nothing perfect but getting together to do this ignited some interesting conversation and I felt like we made progress in the end. Below are my class notes for today Cardinality     cardinality is the count of entities within the relationship Participation     specifies minimum number of relationship instances each entity can participate in     this is cal...
Read more

Class 1 | Week 14 | DAT601

Today's lesson pertained to an explanation of the Milestone three steps to get everyone on the same page before Todd started into a talk about database file structures and the different structures they may take. The following discussion resulted in a lot of in-depth information regarding storage sizes that is ideally relevant to the estimation of database storage size task we have to complete within milestone 3. The rest of the class has been assigned to milestone 3 work.
Read more