how database system deal with database applications

ANS-The DBMS is an important component of the database environment.

This environment also includes different types of hardware and software,

people who perform different functions within the environment, procedures

designed to accomplish desired activities, and data.

The data constitute the database’s central component through which information is generated.

Let me emphasize that the main purpose of the database environment is to help an organization

to perform its mission and to achieve its goals.

The Database Environment Components

Note that the database administrator writes and enforces the procedures and standards

that are then used by designers, analysts, programmers, and end users.

The end users use the application programs created by analysts and programmers.

Note: Analysts wear two hats. They are end users in that they perform analysis

based on the application programs.

And they help produce application programs by collaborating with programmers

to define the parameters of the applications.

In turn, the application programs make use of the DBMS, which manages the data.

Note also that the database designer and the database administrator perform their jobs

through the interface – that would be shown on the computer.

The interface is the gateway to the database, which resides within the hardware.

Finally, the System Administrator manages the entire system.

The modern database‑and‑applications development software is so easy to use that

many people can quickly learn to implement a simple database and develop simple

applications within a week or so, without giving design a thought.

As data and reporting requirements become more complex,

those same people will simply (and quickly!) produce the required add-ons.

That’s how data redundancies and all their attendant anomalies develop,

thus reducing the “database” and its applications to a status worse than useless.

Good applications can’t overcome bad database designs.

The existence of a DBMS does not guarantee good data management,

nor does it ensure that the database will be able to generate correct and timely information.

Ultimately, the end user and the designer decide what data will be stored in the database.

Since most current DBMSes are based on the relational model, the relational model’s

conceptual simplicity could be compared to the hierarchical and network models.

Because the entity relationship model’s representation – through the ERD –

is the basis for database design.

Database design is a process that, in effect, yields a detailed database blueprint.

This blueprint, usually in the form of an E-R diagram or ERD,

is used as the basis for database implementation.

A database created without the benefit of a detailed blueprint is unlikely to be satisfactory.

Would you think it smart to build a house without the benefit of a blueprint?

So why would you want to create a database without a blueprint?

(Perhaps it would be OK to build a chicken coop without a blueprint,

but would you want your house to be built the same way?)