Management", Thomas Connolly and Carolyn Begg,. 1. Database ... Adopted
from "Database Systems: A Practical Approach to Design, Implementation, and.
Database System Development Lifecycle (11 stages) 1. Database planning Mission statement Mission objectives
2. System definition System boundary User views
3. Requirements collection and analysis User views and data types User’s requirement specification System specification Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
1
Database System Development Lifecycle 4. Database design Conceptual design
ERD + DD
Local design
DB schema
Physical design
Base relation, files, indexes, integrity constraints, security measures, …
5. DBMS selection (optional) Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
2
Database System Development Lifecycle 6. Application design
Interface …
7. Prototyping (optional) 8. Implementation 9. Data conversion and loading 10. Testing 11. Operational maintenance Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
3
1. Database Planning 1.1 Mission statement
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
4
1. Database Planning 1.2 Mission objectives 1
2
3 4 Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
5
2. System definition 2.1 System boundary In this project
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
6
2. System definition 2.2 User views
data that can be accessed by each user
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
7
3. Requirements collection and analysis 3.1 User views and data types
Branch view
Staff view
(combining 2 users)
(combining 2 users)
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
8
3. Requirements collection and analysis 3.2 User’s requirement specification [In appendix A] •
Describe in detail the data to be held in DB & –
•
e.g. In Branch view: branch number, address, tel #, manager, date manager assume job, monthly bonus, …
Describe how the data is to be used – – –
e.g. in transaction requirements insert, update, delete, query e.g., list the details of branch in a given city,
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
9
3. Requirements collection and analysis 3.3 System specification •
Describe any feature to be included in DB system such as performance & security req. – – – – –
Initial DB size, 2,000 staff, 100 branches, average 20, max 40 staff in each branch, DB growth rate, approx. 50 new properties, 200 new owners added per months, Searches, approx. 10 search/day for details of a branch, Searches, approx. 20 search/day for details of staff at a branch, Centralized DB or networked system, Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
10
3. Requirements collection and analysis 3.3 System specification (con’t) •
Describe any feature to be included in DB system such as performance & security req. – – – –
Performance, less than 1 second response time, off peak (5 second, peak) Security, password protected, Backup and recovery, backup daily at 12 am, Legal issue, personal data governed by law.
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
11
4. Database design • Three phases of database design: – Conceptual database design • ERD, DD
– Logical database design • DB schemas
– Physical database design • Base relations, files, indexes, integrity constraints, security measures
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
12
4. Database design
• Conceptual database design(Branch view) DRD
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
13
4. Database design • Conceptual database design(Staff view) ERD
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
14
4. Database design • Conceptual database design(Global view) ERD
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
15
4. Database design • Logical database design(Global view)
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
16
•
4. Database design Physical database design –
DBDL for the PropertyForRent Relation (constraints)
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
17
4. Database design • Physical database design
Shown on next slide
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
18
4. Database design • Physical database design
Adopted from "Database Systems: A Practical Approach to Design, Implementation, and Management", Thomas Connolly and Carolyn Begg,
19
