TERMINOLOGIES, DATA
NAMES AND DEFINITION
CLASSIFICATION OF
ATTRIBUTES
Nicole Carlet
LEARNING OBJECTIVES
At the end of the session, you will be able to:
1. Define the different terminologies in Data Manipulation Using Database
Management System Graphical User
2. Relate the different terms and basic concept in Unit 1 when it comes to
Graphical User Interface
3. Identifying the rules in giving Data Names and definitions
4. Differentiate the different classifications of attributes
Database vs. Relational Databases
Database: A database can be one, stand-alone table that can contain many
fields of information. This is the simplest, yet least powerful type of
database and is often referred to as a “flat” database.
Relational Databases: Many tables that are linked through common fields
and can ensure greater accuracy and less input of data. Relational
databases increase flexibility of data and allow ease of collecting and
maintaining historical data.
Database vs. Relational Databases
Relationships: Relational databases are databases in which common fields
of information join tables. The relationships are one-to-one and one-to-
many relationships. A one-to-one relationship ensures that one record in
one table has a (and only one) matching record in another table. One-to-
Many relationships allow one record in one table and many records in
another table.
Database vs. Relational Databases
Database Objects: Many Database management Systems (DBMS), such as
MS Access (which by the way we’ll be using as our DBMS for this course),
contain objects. These objects generally are: tables, queries, forms, and
reports. These objects provide functionality and power to your database
information. However, access is not appropriate for large databases, but is
terrific for small and medium size databases with limited users.
Database vs. Relational Databases
Table (Entity Type) - A table contains or holds the data. Tables can limit
the types of data in fields and can assist in integrity and accuracy of data.
Generally, tables do not perform calculations and are simply data collectors
for input or other means of acquiring data. Fields comprise the records,
records comprise the tables, and tables comprise the database.
Database vs. Relational Databases
RECORD - A record is a collection of fields for an item you are tracking. For
example, a record consists of all the fields for a person if you are tracking
associates in a company. In addition, a record is a single row which
consists of multiple fields.
Database vs. Relational Databases
Attribute (Fields)
- are the different characteristics (attributes) within a Table. Tables usually
contain multiple fields. A field is the lowest level of data in a database.
Fields consist of information about the item you are tracking. For example,
if you are tracking people or human resource data some of the fields you
would want to include would be First Name, Last Name, Social Security
Number, and so on.
- It is a defined property of an entity. In the school example an attribute of
student (which is an entity) might be name or student ID. Attributes are the
same thing as fields in a flat file database. It is (often corresponds to a field
in a table).
Data Names and Definitions
Data objects must be named and defined before they can be used
unmistakably in a model of organizational data.
Data Names
• Relate to business, not technical characteristics.
- Customer, Student is a good name but File01, Bit07 are not good
names.
• Be meaningful, must be to the point
• Be unique from the name used for every other distinct data objects.
- HomeAddress versus CampusAddress
Data Names
• Readable so that the name is structured as the concept would most
naturally be said
- GradePointAverage is a good name compared to
AverageGradeRelative to A.
• Composed of words taken from an approved list
- Each organization often chooses a vocabulary from which significant
words in data names must be chosen. (maximum is preferred, never
upper limit, ceiling or highest)
Data Names
• Repeatable meaning that different people or the same person at
different times should develop exactly or almost the same name.
- The birth date of a student would be StudentBirthDate and the birth
date of an employee would be EmployeeBirthDate.
Classifications of attributes
Entities are represented by means of their properties, called attributes.
Attributes are characteristics of an entity. An entity may have many
attributes. For each attribute, there is set permitted values called domain.
Data Domain refers to all the valid values which a data element (column)
may contain.
Atomic vs. Composite Attribute
Atomic Attribute: An attribute that cannot be divided into smaller
independent attribute is known as atomic attribute. For example, assume
Student is an entity and its attributes are Student No, Name, Age, Address and
Phone no. Here the age (attribute) of student (entity) cannot further be divided.
In this example age is atomic attribute.
Composite Attribute: An attribute that can be divided into smaller
independent attribute is known as composite attribute. For example, the
address (attribute) of student (entity) can be further be divided into House no,
city and so on. In this example address is composite attribute.
Single-Valued vs. Multi-Valued Attribute
Single-Valued Attribute: An attribute that has only single value for an
entity is known as single-valued attribute. For example, the age (attribute) of
student (entity) can have only one value. Here, age is single valued attribute.
Multi-Valued Attribute: An attribute that can have multiple values for an
entity is known as multi-valued attribute. For example, the Phone no
(attribute) of student (entity) can have multiple value because a student may
have many phone numbers. Here, Phone no is multi valued attribute.
Stored vs. Derived Attribute
Stored Attribute: An attribute that cannot be derived from another attribute
is known as stored attribute. For example, birth date cannot derive from age
of student.
Derived Attribute: An attribute that can be derived from another attribute
is known as derived attribute. For example, age can be derived from birth
date of student.
Stored vs. Derived Attribute
Null Valued Attribute: An attribute which has not any value for an entity is
known as null valued attribute. For example, there may be chance when a
student has no phone no. In that case, phone no is called null valued attributes.
Key Attribute: An attribute that has unique value of each entity is known as
key attribute. For example, every student has unique student no. Here, student
no. is key attribute.
THANK YOU FOR
LISTENING!
