0% found this document useful (0 votes)
444 views26 pages

Categories of End-Users (Contd..) : - Sophisticated User

The document discusses database concepts and users. It defines sophisticated users as those familiar with database systems, like scientists and engineers. Stand-alone users mostly maintain personal databases using applications like tax or address book programs. System analysts and programmers determine requirements for naive users and develop transactions. The document also outlines advantages of the database approach like data sharing and integrity enforcement. It provides an example database for a university with entities like students, courses, and departments.

Uploaded by

Sowmya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
444 views26 pages

Categories of End-Users (Contd..) : - Sophisticated User

The document discusses database concepts and users. It defines sophisticated users as those familiar with database systems, like scientists and engineers. Stand-alone users mostly maintain personal databases using applications like tax or address book programs. System analysts and programmers determine requirements for naive users and develop transactions. The document also outlines advantages of the database approach like data sharing and integrity enforcement. It provides an example database for a university with entities like students, courses, and departments.

Uploaded by

Sowmya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

Categories of End-users (Contd..

)
• Sophisticated user:
These include business analysts, scientists,
engineers , others thoroughly familiar with the
system capabilities.

Many use tools in the form of software packages


that work closely with the stored database.
Categories of End-users (Contd..)

• Stand-alone user:
- Mostly maintain personal databases using
ready-to-use packaged applications

- An example is a tax program user that creates


its own internal database.
- Another example is a user that maintains an
address book
Database Users (Contd..)
• System Analysts and Application
Programmers (System Engineers):
- System analysts determine the requirements of
end users, especially naïve and parametric end
users, and develop specification for canned
transactions that meet these requirements.

Application Programmers implement these


specifications as programs.
Workers behind the scene

• DBMS system designer and implementer

• Tool Developers

• Operators and maintenance personnel


Advantages of Using the Database
Approach
• Controlling redundancy in data storage and in
development and maintenance efforts.
• Sharing of data among multiple users.
• Restricting Unauthorized Access.
Advantages of Using the Database
Approach (Contd..)
• Providing persistent storage for program
Objects

• Providing Storage Structures (e.g. indexes)


for efficient Query Processing
Advantages of Using the Database
Approach (Contd..)
• Providing backup and recovery services.
• Providing multiple interfaces to different
classes of users.
• Representing complex relationships among
data.
Advantages of Using the Database
Approach (Contd..)
• Enforcing integrity constraints on the
database.
• Drawing inferences and actions from the
stored data using deductive and active rules.
Additional Implications of Using the
Database Approach
• Potential for enforcing standards:
This is very crucial for the success of database
applications in large organizations.

• Standards refer to data item names, display formats,


screens, report structures, meta-data (description of
data), Web page layouts, etc.
Additional Implications of Using the
Database Approach (Contd..)
• Reduced application development time:
Incremental time to add each new
application is reduced.
• Flexibility to change data structures:
Database structure may evolve as new
requirements are defined.
Additional Implications of Using the
Database Approach (Contd..)
• Availability of current information
-Extremely important for on-line
transaction systems such as airline, hotel,
car reservations.
Example of a Database
(with a Conceptual Data Model)

• Mini-world for the example:


Part of a UNIVERSITY environment.
• Some mini-world entities:
STUDENTs
COURSEs
SECTIONs (of COURSEs)
(academic) DEPARTMENTs
INSTRUCTORs
Example of a Database
(with a Conceptual Data Model)

• Some mini-world relationships:


SECTIONs are of specific COURSEs
STUDENTs take SECTIONs
COURSEs have prerequisite COURSEs
INSTRUCTORs teach SECTIONs
COURSEs are offered by DEPARTMENTs
STUDENTs major in DEPARTMENTs
Example of a simple database
Example of a simple database
Example of a simplified database
catalog
Data Models
• Hierarchical Data model (Extra information)
• Network Data model (Extra information)
• Relational Data model
• Object-Oriented model (Extra information)
• Deductive Model etc. (Extra information)
Hierarchical Data Model
(Extra information)

• A hierarchy is simply a network that is a forest


(collection of trees) in which all links point in the
direction of child to parent.

• Oldest database model

• Example - Information Management System (IMS)


Network Data model
(Extra information)

• The Network model replaces the hierarchical forest


(collection of trees) with a simple directed graph
model for data.
• In this model a parent node can have multiple child
nodes, and child node can also have many parent
nodes (many-to-many relationships).
• Example : IDMS (Integrated Data Management
System)
Relational Data model

“You will be studying


in depth
in the following sessions”
Other Models
• Object-Oriented model (Extra information)

• Deductive Model etc. (Extra information)


When not to use a DBMS
• Unnecessary Overhead for providing
generality, security, concurrency control,
recovery, and integrity functions

• No multiple-users access to data

• Applications are simple, well defined and


not expected to change.
When not to use a DBMS (Contd..)

• If the database system is not able to handle


the complexity of data because of modeling
limitations

• If there are stringent real-time requirements


that may not be met because of DBMS
overhead.
SUMMARY
• Basic Definitions
• Typical DBMS Functionality
• Example of a Database (UNIVERSITY)
• Characteristics of the Database Approach
• Database Users
• Advantages and When Not to Use Databases
Expected Questions from chapter 1
Hints:
1. Definitions Data, Database, DBMS
2. Disadvantages of File Processing System
3. Characteristics of Database approach
4. Advantages & Disadvantages of DBMS
5. Different types of Database users
(Actors/workers)
6. Responsibilities of Database Administrators,
Database Designers
THANK U

You might also like