Database design using entity-relationship diagrams. (2011)

• Record Type: Book
• Further Information: Note: Sikha Bagui and Richard Earp.
• Other Names: Bagui, Sikha, 1964-; Earp, Richard, 1940-
• Contents: Data, Databases, and the Software Engineering Process; Data; Building a Database; What is the Software Engineering Process?; Entity Relationship Diagrams and the Software Engineering Life Cycle; Phase 1: Get the Requirements for the Database; Phase 2: Specify the Database; Phase 3: Design the Database; ; Data and Data Models; Files, Records, and Data Items; Moving from 3 × 5 Cards to Computers; Database Models; The Hierarchical Model; The Network Model; The Relational Model; The Relational Model and Functional Dependencies; Fundamental Relational Database; Relational Database and Sets; Functional Dependency; Non-1NF to 1NF; The Second Normal Form; Anomalies; Non-2NF to 2NF; The Third Normal Form; The Equijoin Operation; Some Functional Dependency Rules; The Boyce Codd Normal Form; The Basic ER Diagram: A Data Modeling Schema; What Is a Data Modeling Schema?; So, What Is an Entity Relationship Diagram?; Defining a Database— Some Definitions: Entity, Relationship, Attribute; A Beginning Methodology; ER Design Methodology; A First "Entity-Only" ER Diagram: An Entity with Attributes; More about Attributes; The Simple or Atomic Attribute; The Composite Attribute; The Multivalued Attribute; The Derived Attribute; Keys; English Description of the Entity; The Method; ER Design Methodology; Examples; Mapping the Entity Diagram to a Relational Database; Case Study Beyond the First Entity Diagram; Examining an Entity: Changing an Attribute to Be an Entity; Defining a Relationship for Our New Entity; ER Design Methodology; A Preliminary Grammar for the ER Diagrams; The Relationship; Defining a Second Entity; Does a Relationship Exist?; Attribute or Relationship?; ER Design Methodology; Case Study Extending Relationships/Structural Constraints; The Cardinality Ratio of a Relationship; One to One (1:1); Many to One (M:1); One to Many (1:M); Many to Many (M:N); Participation: Full/Partial; English Descriptions; Tighter English; Pattern 1—x:y::k:1; Pattern 2—x:y::k:1; Pattern 3—x:y::k:M; Pattern 4—x:y::k:M; Summary of the Patterns and Relationships; ER Design Methodology; Some Examples of Other Relationships; An Example of the One-to-Many Relationship An Example of the Many-to-One Relationship An Example of the Many-to-Many Relationship; One Final Example; ER Design Methodology; Pattern 1—M:1, from the M Side, Full Participation; Pattern 3—1:M, from the 1 Side, Full Participation; Mapping Relationships to a Relational Database; Mapping Binary M:N Relationships; Mapping Binary 1:1 Relationships; Mapping Binary 1:N Relationships; Case Study The Weak Entity; Strong and Weak Entities; Weak Entities and Structural Constraints; Weak Entities and the Identifying Owner; Another Example of a Weak Entity and the Identifying Owner; Weak Entities Connected to Other Weak Entities; Revisiting the Methodology; Weak Entity Grammar; The Keys; Mapping Weak Entities to a Relational Database; Case Study Further Extensions for ER Diagrams with Binary Relationships; Attributes of Relationships; The Attributes; Relationships Developing into Entities: The M:N Relationship Revisited; The Entity; More Entities and Relationships; More than Two Entities; More Evolution of the Database; Attributes that Evolve into Entities; Recursive Relationships; Recursive Relationships and Structural Constraints; Multiple Relationships; The Derived or Redundant Relationship; Optional: An Alternative ER Notation for Specifying Structural Constraints on Relationships; Review of the Methodology; ER Design Methodology; The Entity; The Attributes; The Keys; Mapping Rules for Recursive Relationships; Case Study Ternary and Higher-Order ER Diagrams; Introduction; Binary or Ternary Relationship?; Structural Constraints for Ternary Relationships; Many to Many to Many (M:M:M); An Example of an n-ary Relationship; n-ary Relationships Do Not Preclude Binary Relationships; Methodology and Grammar for the n-ary Relationship; A More Exact Grammar; Grammar in a Partial Participation, Ternary Relationship with an M:1:M Relationship; Ternary Relationships from Relationship-Relationship Situations; n-ary Relationships that May Be Resolved into Binary Relationships; Mapping n-ary Relationships to a Relational Database; Review of the Methodology; ER Design Methodology; The Enhanced Entity Relationship (EER) Model; Introduction; What Is a Generalization or Specialization?; Variants; Examples of Generalizations or Specializations; Methodology and Grammar for Generalization/Specialization Relationships; Mapping Rules for Generalizations and Specializations; Mapping Rule 15; Mapping Rule 16; Mapping Rule 17; Mapping Rule 18; Subclasses of Subclasses; Mapping Rule 19; Categories or Union Types; Participation Ratios in Categories or Union Types; Mapping Categories or Union Types When Superclasses Have the Same Primary Keys; Mapping Categories or Union Types When Superclasse; Final ER Design Methodology; ER Design Methodology; Case Study Relational Mapping and Reverse Engineering ER/EER Diagrams; Introduction; Steps Used to Map ER/EER Diagrams to Relational Databases; Reverse Engineering; Reverse Engineering Rule 1. Develop Strong Entities; &nbsp
• Edition: 2nd ed
• Publisher Details: Place of publication not identified : Auerbach Publications
• Publication Date: 2011
• Extent: 1 online resource, illustrations
• Subjects: 005.74; Database design; Relational databases
• Languages: English
• ISBNs: 9781439861776; 1439861773
• Access Rights: Legal Deposit; Only available on premises controlled by the deposit library and to one user at any one time; The Legal Deposit Libraries (Non-Print Works) Regulations (UK).
• Access Usage: Restricted: Printing from this resource is governed by The Legal Deposit Libraries (Non-Print Works) Regulations (UK) and UK copyright law currently in force.