Blog

Data Modelling Case Study / Example: EPANET (cont.) (#14)

By |2016-12-22T20:38:57+11:00November 3rd, 2016|EPANET, Newsletter|

This post looks further at EPANET as an example of data modelling. The EPANET water supply distribution modelling software is freely available for download with some example networks. A tutorial can also introduce new users to its use and help with understanding. There is no need for you to install this software or follow the [...]

Data Modelling Case Study / Example: EPANET (#13)

By |2017-02-10T10:54:41+11:00October 27th, 2016|EPANET, Newsletter|

Let’s look at another simple example of data modelling. EPANET is a public domain software package which models water distribution systems.  Written by the Water Supply and Water Resources Division of the US Environment Protection Agency (EPA), it is available as either an interactive network editing program, or a toolkit that allows the analysis engine [...]

Good and bad modelling (#12)

By |2018-04-09T17:22:48+10:00October 21st, 2016|Modelling principles, Newsletter|

We have now looked at the background of data modelling and where it all began. Clay tablets, lists, books and now databases. But behind all of these is the need to model the data in a way that makes it easy to use. In this way, data modelling is both a simple and complex area [...]

Data Modelling Connection Types – Summary (#11)

By |2017-09-11T21:21:43+10:00October 13th, 2016|Newsletter|

We have reviewed data modelling connection types over the past several weeks (see Connections) and seen that a few simple names can describe different types of connections in a general way: One-to-one (mandatory or optional). One-to-many (see One-to-many-relationships). Many-to-one. Many-to-many (see Many-to-many relationships). […]

Many-to-many relationships (#10)

By |2018-04-09T17:25:59+10:00October 6th, 2016|Newsletter|

A many-to-many relationship is also best shown by example. One author can write many books – this is a one-to-many relationship. However, one book can also have many authors. Putting these two facts together, we see a many-to-many relationship. Two “one-to-many” relationships in opposite directions. Since this is not always easy to understand, let’s look [...]

Optional one-to-one relationships (#8)

By |2018-03-26T12:39:02+11:00September 22nd, 2016|Newsletter|

Optional one-to-one relationships Optional one-to-one relationship are more common than mandatory one-to-one relationships, both in life and in data modelling. Sometimes an object may be optionally connected to at least one other object. One example is a car, which may be registered or licensed for use on the road or it may be allowed to [...]

Connections (#6-7)

By |2018-03-26T14:02:50+11:00September 16th, 2016|Newsletter|

Types of connections Connections are the most important and difficult things in modelling. Objects only rarely exist with no connections to other objects. The saying “No man is an island”[1] expresses this with regard to people, and other objects are just the same. […]

Simple Data Modelling Example – Table Columns (#5)

By |2017-11-22T14:12:33+11:00September 1st, 2016|Newsletter|

In this article we continue our simple data modelling example.  We have named our database table, and now we need columns to store the information about each pot. Naming columns is another minefield, just like naming tables. All sorts of logic can be applied to avoid naming conflicts and ensure consistency. We will ignore this [...]

Go to Top