Entities, attributes and instances
A data model lists the nouns a system keeps data about. Each noun is an entity, an attribute or an instance.
Your screen in the online enlistment system shows your name and ID number, then your courses. Each course has a code, a title, units, a section and a room such as SOM 407. You search for another course and press Enlist.
Choose entity, attribute or instance for each term. An explanation appears after each answer.
More detail
How to tell them apart
Entity: a person, place, object, event or concept the organization keeps data about. It has many examples, and each one can be told apart from the others.
Attribute: a property of an entity. It describes nothing on its own and only makes sense when it is attached to an entity.
Instance: one example of an entity, stored as a row of data. You store instances, and you do not draw a box for each one.
Room: attribute or entity?
If a room is only a name such as SOM 407, it is an attribute of the class. If the school also records its capacity or whether it has a projector, or lists everything scheduled in one room, Room is an entity of its own.
Student and Course are easy to spot. Enlistment is easy to miss, because it is an event: a student signing up for a course. It has a date, a status and a grade, and none of those belong to the student or the course alone. So the pairing is an entity.
You can now sort things into entities, attributes and instances.
More detail
This rule decides what your tables look like. When two entities need facts that describe the pairing between them, the pairing gets a table of its own. Relationships shows how that table is built.