Course 1

DFo 1-1
Course Goals

- Describe the purpose of a relational database

- Key business requirements
- Use data modeling to architect a relational database
- Develop an erd to model data
- Use Oracle SQL Developer Data Modeler to build ERDs
- Create a physical model from a logical model (ERD)
- Write execute and save SQL statements in OAE

Course Strategy

- Instructor led-training
- Project-driven curriculum
- Industry-recognized certefication

DFo 1-2
Data versus Information

- Data: collected facts about a topic or item

- Information: the result of combining, comparing and performing calculations on data

Database definition

- Centralized and structured set of data stored on a computer system

- Retrieving, adding, modifying and deleting data when required
- Retrieved data into useful information

Relational Database

- Stores information in tables with rows and columns

- A table is a collection of records
- A row is called a record or instance
- A column is referred to as a field or attribute

Database Management System

- Software that controls the storage, organization and retrieval of data

- Elements: Memory and Storage Management, Data Dictionary, Query Language

Transformation in computing

- Mainframe Computing; Desktop Computing; Client/Server Computing; Grid Computing;

Cloud Computing;
DFo 1-3
Database development Process

Conceptual Data Modeling Strategy and Analysis

Database Design Design
Database Build Build
Database

Types of Database Models

1. Flat File Model

- A single table
- In plain-text form, each line holds only one record
- The fields in the record are seperated with delimiters

2. Hierarchial Model
- Organized in a tree-like structure
- Data stored as records that are connected to one another through links
- Record  a collection of fields; corresponds to a row in the relational database model

3. Network Model
- Can be regarded as a flexible way of representing objects and their relationships
- Compromised of a collection of records connected through links
- Each record is a collection of fields, contains only one value

4. Object-Oriented Model
- A entity is modeled as an object
- Every object has a state and behaviour
- Is through sharing access
- Object to only one class as an instance of that class
- You can derive a new class from an existing class

5. Relational Model
- Represented as a collection of tables
- Each column respresents attributed
- Each row instances
- Each table the visual representation of columns and rows
- Every table has a field that uniquely indetifies row
- The order of rows and columns is not important
- Every row is unique
- Each field can contain only one value
- Table names must be unique
- Column names must be unique
DFo 1-4
Importance of business rules

- Business rules:
o Allow the developer to understand the relationship
o Help you understand the standardization procedure that an organization follows when
handling huge data
o Simple and easy
o Kept up-to-date
- Business rules are used to understand business processes and the nature, role and scope of
data
- Help you categorize and design database tables
- Business rules are provided
o Manager, Policy makers, documentation and operation manuals, organizational
procedures and standards, interview with end users
- Not all business rules can be modeled in a database

Course 2

DFo 2-1

Advantages and Disadvantages of a Flat File Database

- Advantages Disadvantages
Easy to understand less security
Easy to implement data inconsistency
Easy to extract information data redundancy
All records stored in one place cumbersome sharing of info
Simple sorting and filtering of reports slow for huge db
Less hardware and software requirements

Relational Databases

- Presents infomations in tables with rows and columns

- Each column represents a particular type of information, each row lists one record
- The tables are related by using a common field
- A unique field called a key is used to identify each record in a relational database
- Advantages:
Less redundancy
Avoidance of inconsistency
Efficiency
Data integrity
Confidentiality

DFo 2-2

Conceptual Model

- Captures the functional and informational needs of a business

 - Based on current needs, but may reflect future needs
- Addresses the needs of a business, but not its implememtation
- Indetifies:
important entities
relationships
- Does not specify:
attributes
unique indentifiers

Logical Model

- All entities and relationships

- Called ERM
- Illustrated in ERD
- Specifies all attributes and UIDs for each entity
- Determines attribute optionality, relationship optionality and cardinality

Physical Model

- An extension to a logical data model

- Describes how the objects should be implemented
- Shows all table structures, including columns, PK and FK

Steps to create a Physical Data Model

- Model entities as tables

- Model relationships as foreign keys
- Model attributes as columns
- Modify the physical data model based on physical constraints and requirements

Conceptual and Physical Models

- The art of planning, developing, and communicating produces a desired outcome

- Data modeling is the process of capturing the important concepts and rules that shape a
business and depicting them visually in a diagram
- This diagram becomes the blueprint for designing the physical thing
- The client's dream (conceptual model) becomes a physical reality (physical model)

DFo 2-3

Entity

- Info that must be tracked

- Name fort hings that you can list

Entities and Instances

- Entities contains instances

- An entity instance is a single occurrence of an entity

Attributes

- Describe entities and are the specific information that must be known
- Single valued property detail of an entity
Attribute Characteristics

- Are shown within the entity box on the ERD

- Names are singular and mixed case or lowercase
- Should not include the entity´s name
- Mandatory (nulls are not allowed) *
- Optional (nulls allowed) o
- Volatile are unstable attributes (qe dmth ndryshon si psh mosha)
- Nonvolatile are stable attributes (nuk ndryshojne si psh data e lindjes)
- Single or atomic attributes cannot be divided into subparts
- Composite attributes can be divided into smaller subparts
- Single-valued can have a single value at e paticular time (students last name)
- Multi-valued can have more than one value at one time (address)

Barker Notation

Rules for drawing entities

- An entity represented as a round-cornered rectangle

- Must be named and must be placed inside the entity in the upper-left corner
- Should be in uppercase form, singular form

Rules for attributes

- Must be written so everyone can understand them
- The first letter uppercase, others lowercase
- A symbol representing the type of attribute should be placed next to each attribute

Rules for relationships

- Between max of two entities
- Can exist on the same entity
- Has two perspectives
- Both perspectives must be labeled

Bachman Notation

- Entity, Attributes, Relationship lines