Database: Difference between revisions
From CEOpedia | Management online
m (Infobox update) |
m (Text cleaning) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
"Database" (Database [[Management]] [[System]]) DBMS - it's a computer based collection of different files within specific restrictions. Database works as a very functional part of reality and serves to public, institutions, companies etc. "Database finds its application in creating and managing [[information]] in computer systems (Simon, Shaffer, 2002, p. 147) | |||
"Database" (Database [[Management]] [[System]]) DBMS - it's a computer based collection of different files within specific restrictions. Database works as a very functional part of reality and serves to public, institutions, companies etc. "Database finds its application in creating and managing [[information]] in computer systems | |||
==Purpose of Database== | ==Purpose of Database== | ||
"The major function of database is storage of [[information]] as well as editing already existing data which is used on daily bases by certain [[organization]]. Therefore, for instance every university works based on the same principles in order to keep track of students in the university and class enrollment. Since the [[information]] changes every semester database has to be well maintained to keep the system in functional conditions. The structure is very simple and follows logical principles, almost always hierarchic schema, thus database is also known as: file collection | "The major function of database is storage of [[information]] as well as editing already existing data which is used on daily bases by certain [[organization]]. Therefore, for instance every university works based on the same principles in order to keep track of students in the university and class enrollment. Since the [[information]] changes every semester database has to be well maintained to keep the system in functional conditions. The structure is very simple and follows logical principles, almost always hierarchic schema, thus database is also known as: file collection (Cieciura,2006, p. 89) | ||
==Functions of Database== | ==Functions of Database== | ||
Updating Functions- a transaction is an updating function, modifying database and changing old [[information]] to new. Updating functions play significant role in university database such: | Updating Functions - a transaction is an updating function, modifying database and changing old [[information]] to new. Updating functions play significant role in university database such: | ||
* Semester initiation/enrollment | * Semester initiation/enrollment | ||
* Suggest a module | * Suggest a module | ||
| Line 29: | Line 13: | ||
* Transfer student to another module | * Transfer student to another module | ||
Functions and relations - updating and relations functions play interchangeable role in the system. In case of updating functions we deal with constant conditions which represent data integrity. | |||
Functions and relations | |||
Updating function: transfer student X from module 1 to module 2 | Updating function: transfer student X from module 1 to module 2 | ||
| Line 43: | Line 26: | ||
* confirm that student is passing module 2 | * confirm that student is passing module 2 | ||
Verification Functions- do not modify existing data in any way: | Verification Functions - do not modify existing data in any way: | ||
* is course X available? | * is course X available? | ||
* did student X pass course Y? | * did student X pass course Y? | ||
| Line 50: | Line 33: | ||
Database can be characterized by the following properties: | Database can be characterized by the following properties: | ||
* data accessibility- [[information]] stored in database is not only used to be accessed by only one person, but to be used by multiple people to access needed [[information]] even at the same time. | * data accessibility- [[information]] stored in database is not only used to be accessed by only one person, but to be used by multiple people to access needed [[information]] even at the same time. | ||
* data integrity- data accessibility is very useful and can makes operating large database very simple. However, in order to have a large scale system running efficiently we [[need]] a good maintenance. | * data integrity - data accessibility is very useful and can makes operating large database very simple. However, in order to have a large scale system running efficiently we [[need]] a good maintenance. | ||
* database integrity to be fully effective and efficient [[needs]] to be designed within specific scope of the [[project]] requirements in order to store needed [[information]] and prevent future problems. | * database integrity to be fully effective and efficient [[needs]] to be designed within specific scope of the [[project]] requirements in order to store needed [[information]] and prevent future problems. | ||
* [[information]] security- one of the main security features is to assure that database is accessible only for users who are allowed to have access and also by restricting access to certain [[information]] by password. | * [[information]] security - one of the main security features is to assure that database is accessible only for users who are allowed to have access and also by restricting access to certain [[information]] by password. | ||
* abstract data- database can be treated as a real life object that reflects day-to-day operations. | * abstract data - database can be treated as a real life object that reflects day-to-day operations. | ||
* data independency - data is separated form processes which use that data. | * data independency - data is separated form processes which use that data. | ||
"These benefits satisfy conditions of ideal database that could be used by a large [[company]] or even a [[government]] institution. Such properties are indispensable when it comes database design and security and at this point such high [[standard]] in only partially achievable". (Paul Beynon-Davies 1993, | "These benefits satisfy conditions of ideal database that could be used by a large [[company]] or even a [[government]] institution. Such properties are indispensable when it comes database design and security and at this point such high [[standard]] in only partially achievable". (Paul Beynon-Davies 1993, p. 26) | ||
{{infobox5|list1={{i5link|a=[[Knowledge tree]]}} — {{i5link|a=[[Virtual structure]]}} — {{i5link|a=[[Ascii text]]}} — {{i5link|a=[[Knowledge structure]]}} — {{i5link|a=[[EDI systems]]}} — {{i5link|a=[[Asynchronous communication]]}} — {{i5link|a=[[Business memo]]}} — {{i5link|a=[[Management information system]]}} — {{i5link|a=[[Documentation]]}} }} | |||
==References== | ==References== | ||
Latest revision as of 19:43, 17 November 2023
"Database" (Database Management System) DBMS - it's a computer based collection of different files within specific restrictions. Database works as a very functional part of reality and serves to public, institutions, companies etc. "Database finds its application in creating and managing information in computer systems (Simon, Shaffer, 2002, p. 147)
Purpose of Database
"The major function of database is storage of information as well as editing already existing data which is used on daily bases by certain organization. Therefore, for instance every university works based on the same principles in order to keep track of students in the university and class enrollment. Since the information changes every semester database has to be well maintained to keep the system in functional conditions. The structure is very simple and follows logical principles, almost always hierarchic schema, thus database is also known as: file collection (Cieciura,2006, p. 89)
Functions of Database
Updating Functions - a transaction is an updating function, modifying database and changing old information to new. Updating functions play significant role in university database such:
- Semester initiation/enrollment
- Suggest a module
- Cancel module
- Enroll student into a course
- Enroll student into a module
- Transfer student to another module
Functions and relations - updating and relations functions play interchangeable role in the system. In case of updating functions we deal with constant conditions which represent data integrity.
Updating function: transfer student X from module 1 to module 2
Given conditions:
- student X passes module 1
- student X fails module 2
- module 2 is available
Procedure:
- disagree that student X is passing module 1
- confirm that student is passing module 2
Verification Functions - do not modify existing data in any way:
- is course X available?
- did student X pass course Y?
Benefits of Database
Database can be characterized by the following properties:
- data accessibility- information stored in database is not only used to be accessed by only one person, but to be used by multiple people to access needed information even at the same time.
- data integrity - data accessibility is very useful and can makes operating large database very simple. However, in order to have a large scale system running efficiently we need a good maintenance.
- database integrity to be fully effective and efficient needs to be designed within specific scope of the project requirements in order to store needed information and prevent future problems.
- information security - one of the main security features is to assure that database is accessible only for users who are allowed to have access and also by restricting access to certain information by password.
- abstract data - database can be treated as a real life object that reflects day-to-day operations.
- data independency - data is separated form processes which use that data.
"These benefits satisfy conditions of ideal database that could be used by a large company or even a government institution. Such properties are indispensable when it comes database design and security and at this point such high standard in only partially achievable". (Paul Beynon-Davies 1993, p. 26)
| Database — recommended articles |
| Knowledge tree — Virtual structure — Ascii text — Knowledge structure — EDI systems — Asynchronous communication — Business memo — Management information system — Documentation |
References
- Ramakrishnan, R., & Gehrke, J. (2000). Database management systems. Osborne/McGraw-Hill.
Author: Paweł Węgrzynowski
