Professional Documents
Culture Documents
JAN2021 Seminar 5
REA Data Modelling
Seminar 5: Learning Outcomes
• Understanding databases
• This provides an efficient way to store data, as you can enter data
once, then reference it from elsewhere in the database.
User
Application:
Database:
Interface and
Business Logic Data storage
Systems Design & Development Process
Implementa-
System Conceptual Physical Operation &
tion &
Analysis Design Design Maintenance
Conversion
Systems Design & Development Process
1. Systems Analysis
– Initial planning to determine the need for and feasibility of
developing a new system
– Judgments about the proposal’s technological and economic
feasibility
– Identify user information needs
– Define the scope of the proposed new system
– Gather information about the expected number of users and
transaction volumes to make preliminary decisions about hardware
and software requirements
2. Conceptual Design
– Developing the different schemas for the new system at the
conceptual, external, and internal levels
The System Analysis Process
3. Physical Design
– Translating the internal-level schema into the actual database
structures that will be implemented in the new system
– New applications are developed
• Data models:
– Data flow diagrams
– Flow charts
– Entity-relationship diagrams
Entity-Relationship Diagram (ERD)
• Components of an ERD
– Entities: corresponds to tables
– Attributes: corresponds to fields of a table
– Relationships: represents links between tables
Sale Customer
The REA Data Modeling Framework
Identify the Resources, Events and Agents for a customer paying cash
to the cashier for a book that he is purchasing.
Example
Relationship:
• A Sale Record is linked to only one Customer Record
• A Customer Record is linked to minimum zero or many Sale Record
• Field: Not stated – but could be product number, customer ID, address
etc.
Sale Customer
Cardinalities
Developing a REA Diagram
Step 1:
Identify the events about which management wants to collect
information
Step 2:
Identify the resources affected by the events and the agents who
participated
Step 3:
Determine the cardinalities between the relationships
Cardinalities
13
Three Types of Relationships
• One-to-One:
• One-to-Many:
• Many-to-Many:
REA Model – Revenue Cycle
TakeOrder Employee
Inventory
Customer
Sale
Employee
1. For the diagram below, (a) what is the Resource, Event and Agent, and
(b) describe the business rule:
Submits Sales
Machine Customer
Order
Class Activity 5.2: Cardinalities & Business Rule
2. For the diagram below, (a) what is the Resource, Event and Agent, and
(b) describe the business rule:
3. For the diagram below, (a) what is the Resource, Event and Agent, and
(b) describe the business rule:
Pay Supplier
Cheque Supplier
Invoice
Purchasing
Officer
Class Activity 5.2: Cardinalities & Business Rule
4. For the diagram below, (a) what is the Resource, Event and Agent, and
(b) describe the business rule:
Sales Person
Class Activity 5.2: Cardinalities & Business Rule
5. For the diagram below, (a) what is the Resource, Event and Agent, and
(b) describe the business rule:
Return of
Inventory Defective Customer
Inventory
Performs stock
Storekeeper
count
Class Activity 5.3: Case Study
a) Data flow
b) Flowchart
c) Entity-relationship
d) REA
Quiz
a) resource; agents
b) agent; resources
c) transaction; entities
d) resource; relationships.
Quiz
4. Which of the following is not one of the rules in creating an REA data
model?
a) 0 or 1
b) 0 or N
c) 1 or N
a) zero or one
b) one or many
c) zero or many
a) 1:1
b) 0:1
c) 0:N
d) 1:N
Quiz
a) relevant events
b) agents involved
c) resources affected
d) relationship cardinalities.
End of Seminar 5