Database Design

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

1. 5. Physical Design

2. What is Data?

2.1. Data are facts about object, thing, person, entity, event or anything similar to it

3. Common Features of DBMS

3.1. Database Definition

3.1.1. To define entities, relationships, integrity, constrain and authorization.

3.2. Nonprocedural Access

3.2.1. Access data without complicated coding

3.3. Application Development

3.3.1. Graphical tools to develop menus, data entry forms, and report.

3.3.2. Data requirement for form and report.

3.4. Procedural Language

3.4.1. Combines nonprocedural access with full capabilities.

3.5. Transaction Processing

3.5.1. To prevent interference from simultaneous user. Recover lost data after failure.

3.6. Database Tuning

3.6.1. Tools to monitor and improve database perfomance

4. What is Information?

4.1. Data that has been processed

4.2. Can be used to make decision

5. Categories of DBMS

5.1. 1.Desktop Databases

5.2. Desktop databases offer an inexpensive, simple solution to many less complex data storage and manipulation requirements.

5.3. Examples - Microsoft Access, FoxPro,FileMaker Pro ,Paradox and Lotus Approach are the major players.

5.3.1. BENEFITS

5.3.1.1. a) Inexpensive.

5.3.1.2. b) User-friendly.

5.3.1.3. c) Offer web solutions.

5.4. 2.Server Databases

5.4.1. Offer organizations the ability to manage large amounts of data efficiently and in manner that enables many users to access and update the data simultaneously.

5.4.2. Example - Microsoft SQL Server ,Oracle and IBM DB2 .

5.4.2.1. BENEFITS

5.4.2.1.1. a) Flexibility - can handle just about any data management problem . Available for multiple operating system .

5.4.2.1.2. b) Powerful performance - can manage multiple high-speed processors, clustered servers, high bandwidth connectivity and fault tolerant storage technology .

5.4.2.1.3. c) Scalability - able to garcefully handle a rapidly expanding amount of users and/or data .

6. What is Database?

6.1. Collection of related data that is shared by the various categories of users to meet the requirements of an organization's information

7. What is DBMS?

7.1. A software system that enables to define, create and maintain the database

8. Database Development Process

8.1. 1. Project identification

8.2. 2. Project Initiation and Planning

8.3. 3. Analysis

8.4. 4. Logical Design

8.5. 6. Implementation

8.6. 7. Maintenance

9. What is Data Sharing?

9.1. The ability to share the same data resource with multiple applications or users.

10. Properties of Database

10.1. Completeness

10.2. Integrity

10.3. Flexibility

10.4. Efficiency

10.5. Usability (ease of use)

11. DBMS Usage Requirement

11.1. Store Data Efficiently

11.2. Maintains Data Easily

11.3. Combining The Data

11.4. User Accessible Catalog

11.5. Transaction Support

11.6. Concurrency Control Services

11.7. Recovery Services

12. Data Model

12.1. Hierarchical Database

12.1.1. Develop to manage large amount of data

12.1.2. Assume data relationships are hierarchical

12.1.3. One to many (1:M) relationship

12.1.4. Represented by an upside down tree

12.2. Network Database

12.2.1. Similar to Hierarchical Model. Records linked by pointer.

12.2.2. Composed of sets

12.2.3. Many to Many (M:N) relationships

12.3. Entity Relationship Model

12.3.1. Graphical representation of entities

12.3.2. Based on Entity, Attributes & Relationship

12.3.3. Complements the relational data concept

12.4. Relational Database

12.4.1. Problem with legacy database systems

12.4.1.1. Required excessive effort to maintain.

12.4.1.2. hard to manipulate by end-users

13. Client-Server Architecture of DBMS

13.1. A network architecture in which each computer or process on the network is either a client or a server.

14. Three-Schema Architecture of DBMS

14.1. 1. External Level / Schema

14.1.1. The user's view of the database

14.1.2. Consists of a number of different external views of the DB

14.1.3. Describes part of the DB for particular group of users

14.2. 2. Conceptual Level / Schema

14.2.1. The logical structure of the entire database as seen by DBA

14.2.2. What data is stored in the database

14.3. 3. Internal Level / Schema

14.3.1. Physical representation of the DB on the computer

14.3.2. How the data is stored in the database

14.3.3. The relationships among the data