This document discusses database design concepts including: - Conceptual database design considers both operational use and data modeling requirements. - The database life cycle includes requirements analysis, conceptual design, physical design, implementation, and maintenance. - Transaction design must account for the types of transactions that will be run on the database and ensure all required information is included in the database schema.

1. 07/10/2023
Database Design, UML and
(Extended) Entity
Relationship Modeling
sli
de
1

2. 07/10/2023
In this Section…
 Topics Covered
 Database Design
Considerations
 UML and Database
Design
 ER Design and UML
 Related Topics
 ER Design
 Lectures 4 and 5
slide
2

3. 07/10/2023
Design Considerations
slide
3

4. 07/10/2023
Conceptual Design includes Operational Use
slide
4
Mini World
Requirements collection & analysis
Conceptual design
Data model design
Physical design
Database requirements
Conceptual
schema (in a high level data model)
Conceptual schema
(in the data model of a specific DBMS
Internal schema
(for the same DBMS)
DBMS
Independent
DBMS
specific
Data Definition Language Statements
Processing Requirements
Transaction Design
DBMS independent
Transaction Implementation

5. 07/10/2023
Database Application Life Cycle
slide
5
System Definition
Design
Implementation
Loading/Data Conversion
Application Conversion
Testing & Validation
Operation
Monitoring & Maintenance

6. 07/10/2023
Data model requirements
 Expressive
 Simple
 Minimal
 small number of basic concepts
that are distinct and non-
overlapping in meaning
 Diagrammatic
 Formal
 accurate & unambiguous
 CONFLICTING
REQUIREMENTS
Conceptual design
 Complete understanding
of database structure,
semantics, constraints,
relationships etc
 DBMS independent
 Stable description
 Database users and
application users views;
aids their understanding
 Communication with users
slide
6
Conceptual design & Data model requirements

7. 07/10/2023
Transaction Design
 Known transactions (applications) that will run on the
database
 Database schema must include all information required
by transactions
 Relative importance of transactions and expected rates
of invocation important for performance tuning
Identify input/output & functional behaviour: 3 categories
 1. Retrieval display/reports
2. Update insert new data/modify old
3. Mixed
 Transactions can be used to encapsulate integrity
constraints
slide
7

8. 07/10/2023
Transaction Design
 High level process specification technique
data flow diagrams, process modelling etc
 Detailed design using programming
techniques for loops, if statements etc
 Detailed design using set database
operations
 Eight basic operations for updates on EER
schema
 insert entity, modify, delete entity
 add, modify, remove relationship
 add and remove from class
 add and remove class
slide
8

9. 07/10/2023
Transaction environment
 Pre-defined canned transactions
 A free-for-all using SQL directly
 Chiefly On-Line Transaction Processing (OLTP)
 Chiefly Management Information System (MIS)
 Multi-user or single-user
 number of concurrent users—peaks, worst case, and average
 potential conflicts—locking, timestamps
 distributed transactions
 Integrity Checks
 as updates made in transactions
 batch run transaction
slide
9

10. 07/10/2023
On-Line Transactions
slide
10
ON-LINE
DECISION SUPPORT TRANSACTION PROCESSING
• Inquiry & Analysis • Real time Transactions
• Retrieval Intensive • Update Intensive
• Ad Hoc Queries • Pre-Defined Transactions
• Unpredictable Query
Complexity
• Transaction Throughput
• Data Integrity
• High Availability

11. 07/10/2023
Who is Using the Database?
 Users & Ease of Use
 Who is the target end-user
for queries and/or update
transactions
 User Interfaces
 graphical
 forms-based
 SQL
 reports generated
 menu-based
 Task analysis
 Work flows
 Views
Interfaces
 people
 software
 other databases
 hardware
 organisational
processes
slide
11

12. 07/10/2023
Housekeeping
 Backup & Archiving
 on-line or off-line backups
 size of backups
 incremental vs dump
 archiving strategy
 Security
 passwords
 permissions
 views
slide
12

13. 07/10/2023
Operational Considerations
Scope
 complete flexibility with ‘bells and whistles’
 kernel activities
Model choice
 hierarchical / network / relational / object-oriented
/object-relational
Software/Hardware
 Which database management system ?
 Configuration: e.g Unix server and PC front-ends?
slide
13

14. 07/10/2023
Choice of DBMS
Costs
1.Software acquisition
cost
2.Maintenance cost
3.Hardware acquisition
cost
4.Database creation &
conversion cost
5.Personnel cost
6.Training cost
7.Operating costs
 Data model depends
on:
 The structure and use
of the data
 Familiarity of the
system
 Available vendor
services
 communication software
 data entry software
 design and monitoring tools etc
slide
14

15. 07/10/2023
UML - (E)ER
slide
15

16. 07/10/2023
EER vs. UML Terminology
 UML Class Diagram
 Class
 Object
 Attribute
 Domain
 Structured Domain
 Operation
 Association
 Link
 Multiplicities
 EER Diagram
 Entity Type
 Entity
 Attribute
 Domain
 Composite Attribute
 ~ [Derived Attribute]
 Relationship Type
 Relationship Instance
 Cardinality &
Participation
slide
16

17. 07/10/2023
EER Diagram Overview
slide
17

18. 07/10/2023
EER to UML #1
slide
18

19. 07/10/2023
EER to UML #2
slide
19