Who is responsible in administering the primary and secondary resource in the database?

Successfully reported this slideshow.

Your SlideShare is downloading. ×

i. Database Administrators
ii. Database Designers
iii. End Users
iv. System Analysts and Application Programmers (Software Engineers)

i. Database Administrators
ii. Database Designers
iii. End Users
iv. System Analysts and Application Programmers (Software Engineers)

More Related Content

1. 1. Different persons involved in the design, use, and maintenance of a large database with a few hundred users are Actors on the Scene and Workers Behind the Scene. 1. Actors on the Scene We consider the people whose jobs involve the day-to-day use of a large database called as the "actors on the scene.". They are: i. Database Administrators ii. Database Designers iii. End Users iv. System Analysts and Application Programmers (Software Engineers) i. Database Administrators In any organization where many persons use the same resources, there is a need for a chief administrator to oversee and manage these resources. In a database environment, the primary resource is the database itself and the secondary resource is the DBMS and related software. Administering these resources is the responsibility of the database administrator (DBA). The DBA is responsible for authorizing access to the database, for coordinating and monitoring its use, and for acquiring software and hardware resources as needed. The DBA is accountable for problems such as breach of security or poor system response time. ii. Database Designers Database designers are responsible for identifying the data to be stored in the database and for choosing appropriate structures to represent and store this data. These tasks are mostly undertaken before the database is actually implemented and populated with data. It is the responsibility of database designers to communicate with all prospective database users, in order to understand their requirements, and to come up with a design that meets these requirements. In many cases, the designers are on the staff of the DBA and may be assigned other staff responsibilities after the database design is completed. Database designers typically interact with each potential group of users and develop a view of the database that meets the data and processing requirements of this group. These views are then analyzed and integrated with the views of other user groups. The final database design must be capable of supporting the requirements of all user groups. iii. End Users End users are the people whose jobs require access to the database for querying, updating, and generating reports; the database primarily exists for their use. There are several categories of end users: • Casual end users occasionally access the database, but they may need different information each time. They use a sophisticated database query language to specify their requests and are typically middle- or high-level managers or other occasional browsers. • Naive or parametric end users make up a sizable portion of database end users. Their main job function revolves around constantly querying and updating the database, using
2. 2. standard types of queries and updates—called canned transactions—that have been carefully programmed and tested. Bank tellers check account balances and post withdrawals and deposits,reservation clerks for airlines, hotels, and car rental companies check availability for a given request and make reservations. • Sophisticated end users include engineers, scientists, business analysts, and others who thoroughly familiarize themselves with the facilities of the DBMS so as to implement their applications to meet their complex requirements. • Stand-alone users maintain personal databases by using ready-made program packages that provide easy-to-use menu- or graphics-based interfaces. An example is the user of a tax package that stores a variety of personal financial data for tax purposes. iv. System Analysts and Application Programmers (Software Engineers) System analysts determine the requirements of end users, especially naive and parametric end users, and develop specifications for canned transactions that meet these requirements. Application programmers implement these specifications as programs; then they test, debug, document, and maintain these canned transactions. Such analysts and programmers (nowadays called software engineers) should be familiar with the full range of capabilities provided by the DBMS to accomplish their tasks. 2. Workers behind the Scene We consider people who may be called "workers behind the scene"—those who work to maintain the database system environment, but who are not actively interested in the database itself. They include the following categories: • DBMS system designers and implementers are persons who design and implement the DBMS modules and interfaces as a software package. A DBMS is a complex software system that consists of many components or modules, including modules for implementing the catalog, query language, interface processors, data access, concurrency control, recovery, and security. The DBMS must interface with other system software, such as the operating system and compilers for various programming languages. • Tool developers include persons who design and implement tools—the software packages that facilitate database system design and use, and help improve performance. Tools are optional packages that are often purchased separately. They include packages for database design, performance monitoring, natural language or graphical interfaces, prototyping, simulation, and test data generation. • Operators and maintenance personnel are the system administration personnel who are responsible for the actual running and maintenance of the hardware and software environment for the database system.

Who is responsible for database administration?

Who is responsible for the management of the data resource including database planning?