1. © Pearson Education Limited, 20041 Chapter 14 Physical Database Design – Steps 5 & 6 (Design User Views; Design Security Mechanisms) Transparencies

2. © Pearson Education Limited, 20042 Chapter 14 - Objectives Recognise that database represents an essential corporate resource and must be made secure. How to design user views. How to design security mechanisms to satisfy user requirements.

3. © Pearson Education Limited, 20043 Step 5 Design User Views Design user views identified during Requirements Collection and Analysis stage of the database application lifecycle. Normally views created using SQL or a QBE-like facility. For example: CREATE VIEW Staff1_View AS SELECT staffNo, name, position FROM Staff WHERE branchNo = ‘B001’;

4. © Pearson Education Limited, 20044 Step 5 Design User Views – MS Access

5. © Pearson Education Limited, 20045 Step 6 Design Security Measures Design security measures for the database as specified by the users. RDBMSs generally provide two types of database security: system security: access and use of database at system level (such as username/password); data security: access and use of database objects (such as tables and views).

6. © Pearson Education Limited, 20046 Step 6 Design Security Measures - SQL Each database user assigned an authorization identifier by DBA (usually has an associated password). Each object created has an owner. Privileges are the actions that a user is permitted to carry out on a given base table or view (such as SELECT, UPDATE). GRANT statement allows owner to give privileges to other users. REVOKE statement takes privileges away.