Computer Science
Database Design
Database design involves creating a structure for organizing and storing data in a way that is efficient, secure, and easy to access. It includes defining the data types, relationships between different data elements, and optimizing the database for performance. Good database design is crucial for ensuring data integrity, minimizing redundancy, and supporting the efficient retrieval and manipulation of data.
Written by Perlego with AI-assistance
Related key terms
1 of 5
10 Key excerpts on "Database Design"
- S Krishna(Author)
- 1992(Publication Date)
- WSPC(Publisher)
Chapter 7 Elements of Database Design Now that we are familiar with the essential aspects of database manage-ment systems, we can examine the Database Design process in some detail. In general, the designer in any discipline has to be well-versed with the technical skills of his discipline. Further expertise is gained with experience. The more routine stages of design wdl be automated and whatever cannot be so reduced will provide scope for the exercise of creativity. In the Database Design process also, these factors wUl come into play to an extent dependent on the complexity of the problem. Small databases on single user systems are not likely to need any great exercise in such skdls. Large systems storing several gigabytes of data as per several relation schemes and serving hundreds of users would need to be designed with all avadable expertise. Because of its nature, design remains a gray area with few formal techniques. The present chapter wUl present a brief discussion of recommended techniques. The relational model with its elegant simplicity is the model in which a logical representation of the system of interest is to be developed. But its very simplicity is a source of some problems in implementation. Descrip-tions of structures and activities of an enterprise do not translate direcdy into representation in terms of tables which constitute the relational schema. We have therefore mentioned earlier, the two stages involved in database development. The first one is of representation of the system of interest in terms of a conceptual model. And the second, that of translating it into the formal data model—in our case, the relational model. The overall
eBook - PDF- Lee Chao(Author)
- 2006(Publication Date)
- Auerbach Publications(Publisher)
17 Chapter 2 Conceptual Design and Data Modeling Objectives Get a general idea about the process of Database Design. Learn how to collect information about a business process. Understand the concepts and theory of data modeling. Be able to represent a business process with a data model. 2.1 Introduction to Database Design Process One of the functions of a database is to store data collected from a business process. The question is how to store the data so that database users can easily and quickly find them. Remember, there could be petabytes of data stored in a database. If we simply populate the database with data, live with it, later find out it does not meet the business requirements, and then rebuild it all over again, we will cause a lot of chaos in the entire business process. We must carefully design the database before we can populate it with data. We need to investigate the database requirements, construct a database struc-ture to meet these requirements, classify the data to be stored in the database, come up with a plan of how to help the database users to access the data, and so on. A well-built database should clearly categorize business data and provide useful information for daily business processing. To achieve this goal, we carefully go through three major steps in the Database Design process: conceptual design, Database Design, and physical design. The definitions of conceptual design, Database Design, and physical design may vary from one author to another author. For example, some authors may 18 Database Development and Management consider the Database Design software-dependent and others may not. Some may break the above three stages into five or six stages. To us, how to name the stages in a database process is not that important. The crucial thing is not to miss the major steps in a Database Design process. Conceptual Design At this stage, you, as a Database Designer, investigate business requirements and data used in a business process.
eBook - PDF- H. Adeli(Author)
- 1994(Publication Date)
- CRC Press(Publisher)
The design procedure should follow well-defined steps. The basic problem is that once all the data items have been identified, how should they be combined to form useful relations. The first step is the extraction of all the characteristics of the information that is to be represented in the database. Analysis of the information to form associations and their integration into one conceptual model is the second step. The conceptual data model obtained by this process is abstract. It is independent of any computer restraint or database management software support. In order for the conceptual model to be useful, it must be expressed in terms that are compatible with a particular D B M S by considering efficiency of storage space and access time. An internal model is developed for this purpose which is compatible with the conceptual data model. Finally, the Database Design requires accommodation of different users of the database by providing an external data model. The systematic process by which one traverses the different steps of Database Design and performs the mapping from one level of abstraction to the next is called a Database Design methodology. In this section, a methodology based on the ANSI/SPARC approach to design databases for finite element analysis and structural design optimization applications is presented. The methodology considers the following aspects: (i) three views of data -conceptual, internal, and external; (ii) entity set, relationship set, and attributes to form syntactic basic elements of the conceptual model; (iii) relational data model; (iv) matrix data; (v) processing requirements; (vi) normalization of data for relational model. The material for the section is derived from an article by SreekantaMurthy and Arora (1986b). 9.4.1 General concepts Before presenting the Database Design methodology a few general concepts that are useful in the design process are described. The idea of an entity-relationship model is explained.
eBook - PDFDatabase
Principles Programming Performance
- Patrick O'Neil(Author)
- 2014(Publication Date)
- Morgan Kaufmann(Publisher)
Until now we have dealt with databases made up of a number of distinct tables, without concerning ourselves very much with how the tables and their constituent columns were originally generated. Logical Database Design, also known simply as Database Design or database modeling, stud-ies basic properties and interrelationships between data items, with the aim of providing faithful representations of such items in the basic data struc-tures of a database. Databases with different data models have different structures for representing data; with relational databases the fundamental data structures to provide such representations are what we have been call-ing relational tables. It is the responsibility of the database administrator (DBA) to perform this design, assigning the related data items of the data-base to columns of tables in a manner that preserves desirable properties. The most important test of logical design is that the tables and attributes faithfully reflect interrelationships between objects in the real world, and that this remains true after all likely database updates in the future. The DBA starts by studying some real-world enterprise, such as a wholesale order business, a company personnel office, or a college registra-tion department, whose operation needs to be supported on a computer-ized database system. Often working with someone who has great expertise about the details of the enterprise, the DBA comes up with a list of data items and underlying data objects that must be kept track of (in college student registration, this list might include Student_names, courses, course_secti ons, cl ass_rooms, cl ass_peri ods, etc.), Database Design Chapter 5 DATABASE D E S I G N 294 together with a number of rules, or constraints, concerning the interre-latedness of these data items. Typical rules for student registration are the following: ♦ Every registered student has a unique student ID number (which we name s i d ) .
- Adele Kuzmiakova(Author)
- 2023(Publication Date)
- Arcler Press(Publisher)
Database Planning and Design 151 4Data models may be utilized to communicate the designer’s comprehen- sion of the enterprise’s data needs. Assuming all parties are acquainted with the model’s notation, this would facilitate communication among design- ers and users. Enterprises are unifying how they model data by adopting a single strategy for data modeling and applying it to all database develop- ment initiatives. Depending upon the basics of the Entity-Relationship (ER) model, the ER model has the most frequent higher-level data model utilized in database architecture, and this is also the model that we make use of in this chapter (Hernandez, 2013). Table 5.2. The Requirements for an Optimum Data Model 5.6.3. Database Design Phases The 3 major stages of Database Design are logical, conceptual, and physical design. The procedure of creating a model of a company’s data that has been irrespective of any physical constraints. The 1 st step of Database Design has been known as conceptual Database Design, and it entails creating a conceptual data model of the component of the business that we want to model. The data described in the users’ needs description has been used to build the data model. Implementation aspects like the target DBMS software, the programs of application, hardware platform, the languages of programming, or other physical concerns have no bearing on conceptual database architecture (Chin & Ozsoyoglu, 1981). In the procedure of developing a conceptual data model, the model has been subjected to testing and evaluation concerning the needs of the The Creation and Management of Database Systems 152 customers. The conceptual data model of the enterprise acts as a source of information for the subsequent phases, which are concerned with the logical Database Design (Teng & Grover, 1992). Logical Database Design is the second phase in the process of designing a database.
eBook - ePub- Howard Anderson, Sharon Yull, Bruce Hellingsworth(Authors)
- 2004(Publication Date)
- Routledge(Publisher)
4 Concepts of Database DesignSummaryIntroductionThe aim of this chapter is to provide students with an insight into Database Design and technologies. The chapter provides an introduction into the history of storage mechanisms and how databases have evolved, examination of data models and how they have supported users in the understanding and communicating of data set knowledge. The role of database management systems (DBMSs) will also be examined in terms of its function and architecture. The chapter also provides examples of database uses in real-life contexts.Students are expected to design their own database in order to meet the criteria of the qualification specifications, this chapter will therefore introduce students to database software and the tools and techniques for development.Databases play an integral role in the majority of business systems. Their ability to store and manipulate data has enabled organizations across a range of commercial, financial, academic, industrial and medical domains to keep accurate and up-to-date data about their customer, client and patient base.Databases have evolved from being just a flat-file storage tool to a fully relational management and information system that can analyse, predict and demonstrate certain levels of intelligence.This chapter takes a holistic view of how databases have evolved, design and methodology issues and the uses of databases within real-life contexts. This chapter is also designed to support students with their own Database Designs by introducing the use of database applications software tools and techniques.4.1 Database EnvironmentsTo fully appreciate the contribution that databases have made in terms of data storage, manipulation and management, an insight into the history of database development and an overview of the environment in which they operate will be examined.This chapter looks at how databases have evolved, and the users that have contributed to these advancements. The development, functions and features of database management systems (DBMSs) and examples of the use of databases in real-life contexts.
eBook - PDFInformation Technology and Egyptology in 2008
Proceedings of the meeting of the Computer Working Group of the International Association of Egyptologists (Informatique et Egyptologie), Vienna, 8–11 July 2008
- Nigel Strudwick(Author)
- 2009(Publication Date)
- Gorgias Press(Publisher)
The former two are beyond the scope of this paper. How data are stored, however, can make a great deal of dif-ference to the amount of space required to store them and the time required to retrieve them. In this paper we hope to provide an introduction to the techniques of Database Design which will be useful to the novice user. Some of the terms we will use are not quite correct from a database-theory stand-point. Instead we have chosen to use the same terminology found in the manuals provided with commercial software. As you read the tutorial, we suggest you pay especial attention to the illustrations, noting the connections between the relations and the way data moves from one to the next. The illustrations provide a visual example of what is being described in the text, and are essential for understanding the concepts presented. WHAT IS A DATABASE ? A database is a collection of related data. Not all databases are in computers: the telephone book, dictionary, and encyclopaedia are all databases of sorts, organized in different ways and for different purposes. Computerized data-bases have the advantage of being searched quickly and changed easily. More importantly, they can be organized in several different ways at the same time, by creating indexes . 2 A new index for a different purpose may be created at any time, and the indexes can be updated automatically when data are added or deleted. There are three basic kinds of computerized databases: network, hier-archical, and relational. The former two types are usually organized for maximum access speed, and they sacrifice some flexibility as a result. They are most often used for applications in which the permissible queries are restricted to a few well-defined operations.
eBook - PDF- Fon Silvers(Author)
- 2008(Publication Date)
- Auerbach Publications(Publisher)
Chapter 5 Database Design Introduction Database Design is the first true design activity of a data warehouse (Figure 5.1). In the preceding chapter, Source System Analysis was the primary analysis activity. The information provided by this analysis, describing and defining the entities and processes within the enterprise, is the information on which the Database Design is based. A data warehouse designer organizes the entities and processes of the enter-prise, via the principles in the Data Warehouse Philosophy, in the form of databases, tables, and views. Equally important is the usage patterns by which data warehouse customers will use a data warehouse. Discussed in Chapter 10 (Data Warehouse Customers), customers and their usage patterns also influence the design of a data warehouse. These two considerations, Source System Analysis and customer usage patterns, taken together identify the resources (i.e., source data) and requirements (i.e., usage patterns) of a data warehouse. Database Design simultaneously encompasses three architectural decisions. The first decision has been made—the data warehouse will reside on a Relational Data-base Management System (RDBMS). The remaining questions, in relation to Data Models and Data Architecture, are more difficult to answer. Data Model: How will the data be organized within relational tables? What are the subject areas? What are the entities? How will they relate? What will they mean? n
- John Mylopoulos, Michael L. Brodie(Authors)
- 2014(Publication Date)
- Morgan Kaufmann(Publisher)
Database theory has produced dependency theory (normalization) [ULLM82, MAIE83], which addresses some aspects of logical design. Algorithms have been developed for aspects of the view integration problem (i.e., designing a global schema from several overlapping views or subschemata). In addition, (intuitive) methodologies have been developed for logical design [OST84, OLLE88]. Other methodologies, based on software engineering principles, have been proposed for the design of both schemata and transactions at the conceptual level [BR84, BMS84]. Database Design and development environments to support such methodologies are discussed in Section 4 and [REIN84]. Data models are related to knowledge representation in AI [BMS84]. Issues of common interest include expressive power, modelling capabilities (e.g., abstraction), languages, inference (i.e., search), truth management (i.e., integrity mainte-nance), and formal definition of the representations. There is some controversy between AI and Database people about what is modelled in databases [BLP84, BM86b]. Database people contend that databases model parts of the real world (i.e., information systems applications). Some AI people contend that databases do not provide interpretations in which individuals (e.g., objects in the real world) are identified with representations in the database that are used in any reasoning. They claim that databases store and manipulate data structures (at the symbol level) as opposed to representing knowledge (as perceived at the knowledge level) and supporting inference. A middle ground between these extremes is that DBMSs provide some interpretation but depend largely on user intuition and that databases do represent knowledge and provide elementary inference capabilities. Most attempts to integrate AI and Database concepts have concerned data models and knowledge representation.
eBook - PDFConceptual Data Modeling and Database Design: A Fully Algorithmic Approach, Volume 1
The Shortest Advisable Path
- Christian Mancas(Author)
- 2016(Publication Date)
- Apple Academic Press(Publisher)
• a dynamic one: how should the corresponding db be queried for getting correct and prompt answers? (i.e., what should be the archi-tecture, design, and development of the needed application built on top of the above db?) Generally, dbs have four dimensions: design, implementation, optimi-zation, and usage (i.e., programming for querying and modifying data). The design, implementation and optimization are static, while usage is dynamic. Note that, generally, it is true that daily db tasks involve in average some 90% usage, 3% design and implementation, and 7% optimization; consequently, at a first glance, it might seem that mastering only SQL ’s DML is almost the only key to success in the db field. However, both design, implementation and optimization are crucial and can make the huge difference between a very poor and cumbersome set of interrelated tables and a true database: who would not love to deco-rate and live in a beautifully and intelligently architectured, designed, and built spacious home full of light and splendid views around, but prefer instead a dark underground labyrinth shared with some minotaur? 1.7 CONCLUSION AND BOOK OVERVIEW There are two modes of acquiring knowledge, namely, by reasoning and experience. Reasoning draws a conclusion and makes us grant the conclusion, but does not make the conclusion certain, nor does it remove doubt so that the mind may rest on the intuition of truth unless the mind discovers it by the path of experience. —Roger Bacon 19 Data was stored since the dawn of humanity on various media in order to infer from it information and knowledge. Most of the data is discrete, which makes tables and graphs ideal candidates to store it, with tables having great advantages on both storing and querying, which are still the simplest and fastest.
Index pages curate the most relevant extracts from our library of academic textbooks. They’ve been created using an in-house natural language model (NLM), each adding context and meaning to key research topics.
