SWE4004 S2 Database Enviroment

Get Started. It's Free
or sign up with your email address
Rocket clouds
SWE4004 S2 Database Enviroment by Mind Map: SWE4004 S2 Database Enviroment

1. names of authorized users;

2. Software components of a DBMS.

3. Typical functions and services a DBMS should provide.

4. Support for Data Communication.

5. Internal structure of database should be unaffected by changes to physical aspects of storage.

6. Client-server

7. Objectives

7.1. Purpose of three-level database architecture.

7.2. Contents of external, conceptual, and internal levels.

7.3. Meaning of logical and physical data independence.

7.4. Distinction between DDL and DML.

7.5. Purpose/importance of conceptual modeling.

7.6. Function and importance of system catalog.

7.7. Meaning of client–server architecture and advantages of this type of architecture for a DBMS.

7.8. Function and uses of Transaction Processing Monitors.

8. Objectives of Three-Level Architecture

8.1. All users should be able to access same data.

8.2. A user’s view is immune to changes made in other views.

8.3. Users should not need to know physical database storage details.

8.4. DBA should be able to change database storage structures without affecting the users’ views.

8.5. DBA should be able to change conceptual structure of database without affecting all users.

9. ANSI-SPARC Three-Level Architecture

9.1. External Level

9.1.1. Users’ view of the database.

9.1.2. Describes that part of database that is relevant to a particular user.

9.2. Conceptual Level

9.2.1. Community view of the database.

9.2.2. Describes what data is stored in database and relationships among the data.

9.3. Internal Level

9.3.1. Physical representation of the database on the computer.

9.3.2. Describes how the data is stored in the database.

9.4. Differences between Three Levels of ANSI-SPARC Architecture

10. Database Languages

10.1. Data Definition Language (DDL)

10.1.1. Allows the DBA or user to describe and name entities, attributes, and relationships required for the application

10.1.2. plus any associated integrity and security constraints.

10.2. Data Manipulation Language (DML)

10.2.1. Provides basic data manipulation operations on data held in the database.

10.3. Procedural DML

10.3.1. allows user to tell system exactly how to manipulate data.

10.4. Non-Procedural DML

10.4.1. allows user to state what data is needed rather than how it is to be retrieved.

10.5. Fourth Generation Languages (4GLs)

11. Functions of a DBMS

11.1. Data Storage, Retrieval, and Update.

11.2. A User-Accessible Catalog.

11.3. Transaction Support.

11.4. Concurrency Control Services.

11.5. Recovery Services.

11.6. Authorization Services.

11.7. Integrity Services.

11.8. Services to Promote Data Independence.

11.9. Utility Services.

12. System Catalog

12.1. Repository of information (metadata) describing the data in the database.

12.2. One of the fundamental components of DBMS.

12.3. Typically stores:

12.3.1. names, types, and sizes of data items;

12.3.2. data items accessible by a user and the type of access;

12.3.3. usage statistics

12.3.4. constraints on the data;

13. Multi-User DBMS Architectures

13.1. Teleprocessing

13.2. File-server

14. Components of Database Manager