Tag: DataJournal

Class 3

This is based on the 8/5/19 Dat602 Class.

Relational model is the most common model around the world. Around 95% of models are of this type, recently some other types of model have come about, these have problem which is why they haven’t over taken Relational Models. Breaking down this information allows us to better understand why we use relationship models.

For our project we will use story board almost as a stand in for Conceptual Model.

Aggregate Model and Network model are No-SQL model and require a relational model to work.

Normally a set is not ordered, but aggregate models have information dumped into the system and join it together, it’s a way of access data and run it, which is why they use this, not good for places where there will be a lot of changes to the date.

Network model takes relationships to the extreme because everything has a possible like to another piece of data.

This information is important to understanding how exactly how relationship model work which is the model we will use.

In a relation ship model if you create references to other element like with a network model each element gain a reference to the other. This is what foreign keys are.

Relational model have sets of data which are all logically related and putting into a ‘table’.

We are creating a simple program which access a data base constantly we will go with relational models as that is the industry standard.

We may use any logical math with in SQL which will be helpful as there are many basic mathematical function which we might need with in our project such as order a high score chart.

Cod is the creator of the relational model.

After the creation of relational model IBM was the first company to adopted the model.

Chris Date worked out how to normalize the database model and allowing them to be fix if they are broken. He also worked for IBM and worked with Cod on the Relationship model.

The point is that each data value only has to be stored once allowing us to avoid update error where only one has to be updated.

Data independence, this is the concept that we can create a database which is independent from the program that we are creating so we can re-use it with another program.

SQL is a very user friendly language which allow the use to select and edit specific part of a database if the column in the database is specified then they don’t have to be ordered otherwise they will be place in the order they are entered.

Some functions of SQL are aggravating columns together this is useful for things such as making composite key or to joining names together for user names.

Project Ideas

This entry is based on the 6/5/19 Dat602 Class.

In this class, we have learnt what we need to do to complete the required project.

We have learnt this so we can start working on and planning our project.

We have gained this knowledge by getting into groups and explaining the assessment to the rest of the class.

For this project we will be creating a simplistic project, where multiple players can access a game and interact with each other.

The entire project has to be saved to a database created with mySQL.

We have limited time to complete this project, so we need to build a simple game.

Because we are constantly updating a database, this will slow down the program. We need to think about the latency between different players. I believe it would be a good idea to focus on a board game style project, to be able to work around latency.

Some of my ideas for games include a simplified version of “Pokemon Master Trainer”, a Multiplayer game based on “Nine Men’s Morris, a multi-laned version of “The Royal Game of Ur” or a simplified version of “Stratego”, where players have to protect a flag from other players.

I have chosen to select the multiplayer version of Nine Men’s Morris, as games such as Pokemon Master Trainer are too complex and The Royal Game of Ur is too abstract to adapt to a fun multiplayer game.

Here are the rules for the my game:


Strategic Hot Fairy’s

The goal is to have a score that is a certain amount larger than the other players’ scores. Each player takes turns adding or moving their piece on the board. When a piece is moved, the player gains a point. If a piece can’t move or has a piece on either side, that piece’s player loses half their total points and their piece is removed from the board. If the player’s piece was caught between two pieces, those two pieces’ controllers each gain half the point that the other player lost.