The Experts below are selected from a list of 234 Experts worldwide ranked by ideXlab platform
Toby J Teorey - One of the best experts on this subject based on the ideXlab platform.
-
11 – CASE Tools for Logical Database Design
Database Modeling and Design, 2020Co-Authors: Toby J TeoreyAbstract:Publisher Summary There are several good CASE tools available for computer- assisted Database Design. Database Design is just one part of the analysis and Design phase of creating effective business application software, but it is often the part that is the most challenging and the most critical to perform. This chapter focuses on commercially available tools that simplify these Design processes. These computer-aided system engineering, or CASE, tools provide functions that assist in system Design. CASE tools are widely used in numerous industries and domains, such as circuit Design, manufacturing, and architecture. Logical Database Design is another area where CASE tools have proven effective. This chapter explores the offerings of the major vendors in this space: IBM, Computer Associates, and Sybase. Each of these companies offers feature-rich technology for developing Logical Database Designs and transitioning them into physical Databases you can use. The aim of this chapter is to survey these products to give the reader a taste for the capabilities they provide.
-
11 case tools for Logical Database Design
Database Modeling and Design (Fifth Edition)#R##N#Logical Design, 2011Co-Authors: Toby J TeoreyAbstract:Publisher Summary There are several good CASE tools available for computer- assisted Database Design. Database Design is just one part of the analysis and Design phase of creating effective business application software, but it is often the part that is the most challenging and the most critical to perform. This chapter focuses on commercially available tools that simplify these Design processes. These computer-aided system engineering, or CASE, tools provide functions that assist in system Design. CASE tools are widely used in numerous industries and domains, such as circuit Design, manufacturing, and architecture. Logical Database Design is another area where CASE tools have proven effective. This chapter explores the offerings of the major vendors in this space: IBM, Computer Associates, and Sybase. Each of these companies offers feature-rich technology for developing Logical Database Designs and transitioning them into physical Databases you can use. The aim of this chapter is to survey these products to give the reader a taste for the capabilities they provide.
-
Requirements Analysis and Conceptual Data Modeling
Database Modeling and Design, 2011Co-Authors: Toby J Teorey, Sam Lightstone, Tom Nadeau, H.v. JagadishAbstract:Logical Database Design is accomplished with a variety of approaches, including the top-down, bottom-up, and combined methodologies. The traditional approach, particularly for relational Databases, has been a low-level, bottom-up activity, synthesizing individual data elements into normalized tables after carefully analyzing the data element interdependencies defined during the requirements analysis. Although the traditional process has been somewhat successful for small-to medium-sized Databases, when used for large Databases its complexity can be over-whelming to the point where practicing Designers do not bother to use it with any regularity. In practice, a combination of the top-down and bottom-up approaches is used; in most cases, tables can be defined directly from the requirements analysis.
-
case tools for Logical Database Design
Database Modeling and Design (Fourth Edition)#R##N#Logical Design, 2006Co-Authors: Toby J Teorey, Sam Lightstone, Tom NadeauAbstract:There are several good CASE tools available for computer- assisted Database Design. Database Design is just one part of the analysis and Design phase of creating effective business application software, but it is often the part that is the most challenging and the most critical to perform. This chapter focuses on commercially available tools that simplify these Design processes. These computer-aided system engineering, or CASE, tools provide functions that assist in system Design. CASE tools are widely used in numerous industries and domains, such as circuit Design, manufacturing, and architecture. Logical Database Design is another area where CASE tools have proven effective. This chapter explores the offerings of the major vendors in this space: IBM, Computer Associates, and Sybase. Each of these companies offers feature-rich technology for developing Logical Database Designs and transitioning them into physical Databases you can use. The aim of this chapter is to survey these products to give the reader a taste for the capabilities they provide.
-
an example of Logical Database Design
Database Modeling and Design (Fourth Edition)#R##N#Logical Design, 2006Co-Authors: Toby J Teorey, Sam Lightstone, Tom NadeauAbstract:This chapter develops a global conceptual schema and a set of SQL tables for a relational Database, given the requirements specification for a retail store Database. The example illustrates the Database life cycle steps of conceptual data modeling, global schema Design, transformation to SQL tables, and normalization of those tables. The example given in the chapter presents a management of a large retail store who need a Database to keep track of sales activities. The requirements analysis for this Database leads to the six entities and their unique identifiers shown in the chapter. For physical Design (access methods, etc.) it is necessary to determine what kind of processing needs to be done on the data. The requirements analysis should determine if there will be substantial Database growth; what time frame that growth will take place over; and whether the frequency and type of queries and updates will change, as well. The first step is to develop a conceptual data model diagram and a set of functional dependencies (FDs) to correspond to each of the assertions given. Figures present the diagram for the entity–relationship (ER) model and show the equivalent diagram for the Unified Modeling Language (UML). Normally, the conceptual data model is developed without knowing all the FDs, but in this example the nonkey attributes are omitted so that the entire Database can be represented with only a few statements and FDs. The results of this analysis, relative to each of the assertions are given.
Tom Nadeau - One of the best experts on this subject based on the ideXlab platform.
-
Requirements Analysis and Conceptual Data Modeling
Database Modeling and Design, 2011Co-Authors: Toby J Teorey, Sam Lightstone, Tom Nadeau, H.v. JagadishAbstract:Logical Database Design is accomplished with a variety of approaches, including the top-down, bottom-up, and combined methodologies. The traditional approach, particularly for relational Databases, has been a low-level, bottom-up activity, synthesizing individual data elements into normalized tables after carefully analyzing the data element interdependencies defined during the requirements analysis. Although the traditional process has been somewhat successful for small-to medium-sized Databases, when used for large Databases its complexity can be over-whelming to the point where practicing Designers do not bother to use it with any regularity. In practice, a combination of the top-down and bottom-up approaches is used; in most cases, tables can be defined directly from the requirements analysis.
-
case tools for Logical Database Design
Database Modeling and Design (Fourth Edition)#R##N#Logical Design, 2006Co-Authors: Toby J Teorey, Sam Lightstone, Tom NadeauAbstract:There are several good CASE tools available for computer- assisted Database Design. Database Design is just one part of the analysis and Design phase of creating effective business application software, but it is often the part that is the most challenging and the most critical to perform. This chapter focuses on commercially available tools that simplify these Design processes. These computer-aided system engineering, or CASE, tools provide functions that assist in system Design. CASE tools are widely used in numerous industries and domains, such as circuit Design, manufacturing, and architecture. Logical Database Design is another area where CASE tools have proven effective. This chapter explores the offerings of the major vendors in this space: IBM, Computer Associates, and Sybase. Each of these companies offers feature-rich technology for developing Logical Database Designs and transitioning them into physical Databases you can use. The aim of this chapter is to survey these products to give the reader a taste for the capabilities they provide.
-
an example of Logical Database Design
Database Modeling and Design (Fourth Edition)#R##N#Logical Design, 2006Co-Authors: Toby J Teorey, Sam Lightstone, Tom NadeauAbstract:This chapter develops a global conceptual schema and a set of SQL tables for a relational Database, given the requirements specification for a retail store Database. The example illustrates the Database life cycle steps of conceptual data modeling, global schema Design, transformation to SQL tables, and normalization of those tables. The example given in the chapter presents a management of a large retail store who need a Database to keep track of sales activities. The requirements analysis for this Database leads to the six entities and their unique identifiers shown in the chapter. For physical Design (access methods, etc.) it is necessary to determine what kind of processing needs to be done on the data. The requirements analysis should determine if there will be substantial Database growth; what time frame that growth will take place over; and whether the frequency and type of queries and updates will change, as well. The first step is to develop a conceptual data model diagram and a set of functional dependencies (FDs) to correspond to each of the assertions given. Figures present the diagram for the entity–relationship (ER) model and show the equivalent diagram for the Unified Modeling Language (UML). Normally, the conceptual data model is developed without knowing all the FDs, but in this example the nonkey attributes are omitted so that the entire Database can be represented with only a few statements and FDs. The results of this analysis, relative to each of the assertions are given.
-
4 – Requirements Analysis and Conceptual Data Modeling
Database Modeling and Design, 2006Co-Authors: Toby J Teorey, Sam Lightstone, Tom NadeauAbstract:Publisher Summary This chapter highlights how the ER and UML approaches can be applied to the Database life-cycle. Logical Database Design is accomplished with a variety of approaches, including the top-down, bottom-up, and combined methodologies. The traditional approach, particularly for relational Databases, is a low-level, bottom-up activity, synthesizing individual data elements into normalized tables after carefully analyzing the data element interdependencies defined during the requirements analysis. The conceptual data model is most successful as a tool for communication between the Designer and the end user during the requirements analysis and Logical Design phases. Its success is owing to the fact that the model, using either ER or UML, is easy to understand and convenient to represent. Another reason for its effectiveness is that it is a top-down approach using the concept of abstraction. The number of entities in a Database is typically far fewer than the number of individual data elements, because data elements usually represent the attributes. Therefore, using entities as an abstraction for data elements and focusing on the relationships among entities greatly reduces the number of objects under consideration and simplifies the analysis.
Tok Wang Ling - One of the best experts on this subject based on the ideXlab platform.
-
Wiley Encyclopedia of Computer Science and Engineering - Entity‐Relationship Model
Wiley Encyclopedia of Computer Science and Engineering, 2008Co-Authors: Tok Wang LingAbstract:Data modeling is an important phase in the development of a Database system. The Entity-Relationship (ER) model was introduced by Peter Chen in 1977. This model has been widely used for conceptual data modeling and has become a tool for communication between Database Designers and end users at the analysis phase of Database development. This article presents the main constructs of the ER model, namely, entities and relationships and their associated attributes, as well as some of its extensions. We also discuss how conceptual Database Design can be carried out using the ER model, the normal form ER diagram and the translation of ER diagrams to the relational model. Keywords: entity-relationship model; data model; normal form; conceptual Database Design; Logical Database Design
-
ICDE - Logical Database Design with inclusion dependencies
[1992] Eighth International Conference on Data Engineering, 1992Co-Authors: Tok Wang LingAbstract:Classical data dependencies are oblivious to important constraints which may exist between sets of attributes occurring in different relation schemes. The authors study how inclusion dependencies can be used to model these constraints, leading to the Design of better Database schemes. A normal form called the inclusion normal form (IN-NF) is proposed. Unlike classical normal forms, the IN-NF characterizes a Database scheme as a whole rather than the individual relation schemes. It is shown that a Database scheme in IN-NF is always in improved third normal form, while the converse is not true. It is demonstrated that the classical relational Design framework may be extended to facilitate the Design of Database schemes in IN-NF. >
-
Logical Database Design with inclusion dependencies
[1992] Eighth International Conference on Data Engineering, 1992Co-Authors: Tok Wang LingAbstract:Classical data dependencies are oblivious to important constraints which may exist between sets of attributes occurring in different relation schemes. The authors study how inclusion dependencies can be used to model these constraints, leading to the Design of better Database schemes. A normal form called the inclusion normal form (IN-NF) is proposed. Unlike classical normal forms, the IN-NF characterizes a Database scheme as a whole rather than the individual relation schemes. It is shown that a Database scheme in IN-NF is always in improved third normal form, while the converse is not true. It is demonstrated that the classical relational Design framework may be extended to facilitate the Design of Database schemes in IN-NF.
Yuan-ching Wang - One of the best experts on this subject based on the ideXlab platform.
-
COMPSAC - Reverse engineering tools supporting LDBR model for Logical Database Design
Proceedings Eighteenth Annual International Computer Software and Applications Conference (COMPSAC 94), 1994Co-Authors: Jenn-nan Chen, Pi-te Chen, Yuan-ching WangAbstract:Based on reverse engineering and restructuring technologies, the Logical Database ReDesign (LDBR) model is proposed to restructure Logical Database schemas from existing Database files. We have developed PC based LDBR-supporting tools to provide analysts and Designers with an automated environment that can extract valuable semantics from existing Database files, analyze functional dependencies to determine candidate keys and normalize Database files to generate new Logical Database schemas for re-engineering. At last, the ER model, a new abstraction, can be created. In addition, the statistics report of all null value, duplicate and redundant fields etc. can be shown from LDBR data dictionary. >
-
Reverse engineering tools supporting LDBR model for Logical Database Design
Proceedings Eighteenth Annual International Computer Software and Applications Conference (COMPSAC 94), 1994Co-Authors: Jenn-nan Chen, Pi-te Chen, Yuan-ching WangAbstract:Based on reverse engineering and restructuring technologies, the Logical Database ReDesign (LDBR) model is proposed to restructure Logical Database schemas from existing Database files. We have developed PC based LDBR-supporting tools to provide analysts and Designers with an automated environment that can extract valuable semantics from existing Database files, analyze functional dependencies to determine candidate keys and normalize Database files to generate new Logical Database schemas for re-engineering. At last, the ER model, a new abstraction, can be created. In addition, the statistics report of all null value, duplicate and redundant fields etc. can be shown from LDBR data dictionary.
Cb Lucasius - One of the best experts on this subject based on the ideXlab platform.
-
genetic algorithms for optimal Logical Database Design
Information & Software Technology, 1994Co-Authors: P Van Bommel, Thp Van Der Weide, Cb LucasiusAbstract:Abstract The focus of this paper is Database Design using automated Database Design tools or more general CASE tools. We present a genetic algorithm for the optimization of (internal) Database structures, using a multi-criterion objective function. This function expresses conflicting objectives, reflecting the well-known time/space trade-off. This paper shows how the solution space of the algorithm can be set up in the form of tree structures (forests), and how these are encoded by a simple integer assignation. Genetic operators (Database transformations) defined in terms of this encoding behave as if they manipulate tree structures. Some basic experimental results produced by a research prototype are presented.
