File Organization Terms and Concepts
File Organization Terms and Concepts
An effective information system provides users with accurate, timely, and relevant information.
Accurate information is free of errors.
A record describes an entity. An entity is a person, place, thing, or event on which we store and maintain information.
Data redundancy is the presence of duplicate data in multiple data files so that the same data are stored in more than one
place or location.
Data redundancy wastes storage resources and also leads to data inconsistency, where the same attribute may have different
values.
Additional confusion might result from using different coding systems to represent values for an attribute.
Program-Data Dependence
Program-data dependence refers to the coupling of data stored in files and the specific programs required to update and
maintain those files such that changes in programs require changes to the data.
Lack of Flexibility
A traditional file system can deliver routine scheduled reports after extensive programming efforts, but it cannot deliver ad
hoc reports or respond to unanticipated information requirements in a timely fashion.
Poor Security
Because there is little control or management of data, access to and dissemination of information may be out of control.
Because pieces of information in different files and different parts of the organization cannot be related to one another, it is
virtually impossible for information to be shared or accessed in a timely manner. Information cannot flow freely across different
functional areas or different parts of the organization.
The DBMS relieves the programmer or end user from the task of understanding where and how the data are actually stored by
separating the logical and physical views of the data.
-The logical view presents data as they would be perceived by end users or business specialists
- Physical view shows how data are actually organized and structured on physical storage media.
DBMS have a data definition capability to specify the structure of the content of the database.
A data dictionary is an automated or manual file that stores definitions of data elements and their characteristics.
Most DBMS have a specialized language called a data manipulation language that is used to add, change, delete, and retrieve the
data in the database. The most prominent data manipulation language today is Structured Query Language, or SQL
Microsoft Access also uses SQL, but it provides its own set of user-friendly tools for querying databases and for organizing data from
databases into more polished reports.
Microsoft Access and other DBMS include capabilities for report generation so that the data of interest can be displayed in a more
structured and polished format than would be possible just by querying. Crystal Reports is a popular report generator for large
corporate DBMS, although it can also be used with Access.
A data model is a relatively simple representation, usually graphical, of more complex real-world data structures. In general terms, a
model is an abstraction of a more complex real-world object or event.
1. Entity is anything (a person, a place, a thing, or an event) about which data are to be collected and stored.
2. Attribute is a characteristic of an entity.
3. Relationship describes an association among entities.
4. Constraint is a restriction placed on the data.
BUSINESS RULES
A business rule is a brief, precise, and unambiguous description of a policy, procedure, or principle within a specific organization.
The relational model foundation is a mathematical concept known as a relation. To avoid the complexity of abstract mathematical
theory, you can think of a relation (sometimes called a table) as a matrix composed of intersecting rows and columns. Each row in
a relation is called a tuple.
A relational diagram is a representation of the relational database’s entities, the attributes within those entities, and the relationships
between those entities.
A Relational Diagram
A relational table stores a collection of related entities.
the entity relationship (ER) model, or ERM, has become a widely accepted standard for data modeling
Peter Chen first introduced the ER data model in 1976; it was the graphical representation of entities and their relationships in a
database structure that quickly became popular because it complemented the relational data model concepts. The relational data
model and ERM combined to provide the foundation for tightly structured database design. ER models are normally represented in
an entity relationship diagram (ERD), which uses graphical representations to model database components.