Database Modeling & Design Fourth Edition- P57 pptx

Index 267 defined, 33–34 example, 43–46 notation, 35–37 packages, 43–46 See also UML diagrams Classes associations, 37 defined, 34 entities vs., 34–35 notation, 35 organization, 43 Clustering, 74–81 concepts, 75–76 defined, 74 grouping operations, 76–78 illustrated, 76 results, 81 techniques, 78–81 See also Entity-relationship (ER) model Collaboration capabilities, 200–201 concurrency control, 200 support, 200–201 Columns, 2 Comparison operators, 214 Compliance checkers, 204–5 Composition, 36–37 aggregation vs., 41 defined, 37 Computer-aided software engineering tools. See CASE tools Conceptual data modeling, 3–4, 8–10, 55–66 alternative notations, 20–22 analysis results, 142 diagram for UML, 142 emphasis, 9 notations, 21–22 substeps, 55–56 transformation to SQL, 6, 83–106 See also Data modeling Concurrency control, 200 Constraints foreign, 217 not null, 216 primary, 217 unique, 216–17 Data independence, 2 items, 2 semi-structured, 209–10 summarizing, 165–66 XML, 209–10 Database design class diagrams for, 37–43 compliance checking, 204–5 knowledge of, 11 logical, 3–6, 53–54, 139–45 physical, 1, 6–8 Database life cycle, 3–8 illustrated, 4 implementation, 8 logical design, 3–6 physical design, 6–8 requirements analysis, 3 step-by-step results, 5, 7 Database management system (DBMS) DDL, 8 defined, 2 relational, 2 Databases CASE tools support, 199–200 defined, 2 generating from designs, 196–99 Data definition language (DDL), 8, 190, 196, 213, 215–18 constraints, 216–17 referential trigger actions, 217–18 Data manipulation language (DML), 8, 214, 218–29 aggregate functions, 222–24 basic commands, 220–21 intersection command, 221–22 Teorey.book Page 267 Saturday, July 16, 2005 12:57 PM 268 Index Data manipulation language (DML) (cont’d.) referential integrity, 227–28 select command, 219 union command, 221–22 update commands, 226–27 usage, 218 views, 228–29 Data mining, 178–85 algorithms, 147, 178 forecasting, 179–81 text mining, 181–85 Data modeling conceptual, 3–4, 8–10, 55–66 example, 61–66 example illustration, 62–63, 65 knowledge of, 11 Data warehouses, 148–66 architecture, 148 architecture illustration, 150 bus, 164 CASE tool modeling, 207–9 core requirements, 149–51 defined, 148 dimensional data modeling, 152–54 dimensional design process, 156 dimensional modeling example, 156–65 fact tables, 154, 155 integration capabilities, 149–50 life cycle, 151–52 life cycle illustration, 153 logical design, 152–66 OLTP database comparison, 149 overview, 148–52 purpose, 155 snowflake schema, 156, 157 star schema, 154–56 subject areas, 149 DB2 Cube Views, 207 Decisions, 46, 47 Decision support systems (DSSs), 148 Denormalization, 8 Descriptors, 15 Design patterns, 204 DeZign for Databases, 190 Dimensional data modeling, 152–54 example, 156–65 process, 156 See also Data modeling Dimensions degenerate, 154 determining, 159 Dimension tables, 154, 160 Double exponential smoothing, 179, 181 Drill-down, 155 Entities, 13–14 classes vs., 34–35 classifying, 56–57 clustering, 74–81 contents, 56–57 defined, 13 dominant, 78 existence, 19–20 intersection, 20 in ternary relationships, 25–26 transformation, 104 weak, 16, 103 Entity clusters defined, 75 forming, 80 higher-level, 80 root, 75 See also Clustering Entity instances, 13 Entity keys, 54 Entity-relationship diagram (ERD) notation, 194 Entity-relationship (ER) model, 9, 13–31 advanced constructs, 23–30 aggregation, 25 AllFusion Data Modeler, 194 Teorey.book Page 268 Saturday, July 16, 2005 12:57 PM Index 269 application to relational database design, 64–66 with Chen notation, 9, 10 conceptual data model diagram, 141 constructs, 13–22 definition levels, 9 entities, 13–14 entity clustering, 74–81 generalization and aggregation, 101 global schema, 64–66 illustrated, 14 many-to-many binary relationship, 87 one-to-many binary relationship, 87 one-to-one binary relationship, 86 Rational Data Architect, 193 relationships, 14–15, 16–20, 25–29 simple form example, 9–10 subtypes, 23–24 summary, 30 supertypes, 23–24 of views based on requirements, 61–63 ER/Studio, 190 Exclusion constraint, 29 Exclusive OR, 29 Executive information systems (EIS), 148 Existence defined, 19 mandatory, 20 optional, 20, 64 Exponential smoothing, 179–80 defined, 179 double, 179, 181 triple, 180, 182 See also Forecasting EXtensible Markup Language. See XML Fact tables defined, 154 granularity, 155 See also Data warehouses Fifth (5NF) normal form, 127, 133–37 defined, 133 membership algorithm satisfaction, 134 See also Normal forms Files, 2 First normal form (1NF), 109 Flows, 46, 47 defined, 46 guard condition, 46 illustrated, 47 Forecasting, 179–81 defined, 179 double exponential smoothing, 179, 181 exponential smoothing, 179–80 least squares line approach, 179 reliability, 180 triple exponential smoothing, 180, 182 See also Data mining Foreign key constraints, 217 Forks, 46, 47 defined, 47–48 example, 48–49 illustrated, 47 Fourth (4NF) normal form, 127, 129–33 goal, 129 tables, 131 tables, decomposing, 132–33 See also Normal forms Functional dependence, 111 Functional dependencies (FDs) defined, 6 in n-ary relationships, 29 primary, 118, 119 secondary, 118, 119 Teorey.book Page 269 Saturday, July 16, 2005 12:57 PM 270 Index Generalization, 23 completeness constraint, 24 defined, 37 disjointness constraint, 24 ER model, 101 hierarchies, 24, 57–58 UML constructs, 40 UML model, 102 Global schema, 3 Grouping operations, 76–78 application, 77–78 defined, 76 illustrated, 77 types, 77 Guard condition, 46–47 HRU, 173–75 Hypercube lattice structure, 173 IDEFIX notation, 21 Identifiers defined, 15 internal, 16 Inclusive OR, 29 Industry Warehouse Studio (IWS), 207, 208 Information Engineering Workbench (IEW), 20 Informix Data Server (IDS), 211 Intersection command, 221–22 Intersection entities, 20 Join dependencies (JDs), 133, 136 Joins, 46, 47 defined, 48 example, 49–50 illustrated, 47 SQL, 224–26 Keys candidate, 109, 110 entity, 54 equivalent, merge, 126 primary, 42, 109 superkeys, 109, 123–24 Logical design, 3–6, 53–54 CASE tools for, 187–211 conceptual data model diagram, 141, 142 conversion, 197–98 data warehouses, 152–66 example, 139–45 problems, 140 requirements specification, 139–40 Logical model, 6 Logical operators, 214 Mandatory existence, 20 Many-to-many relationships, 14 binary, 85, 87, 89 binary recursive, 90, 91, 92 defined, 18 transformation, 104 See also Relationships Many-to-many-to-many ternary associations, 100 Many-to-many-to-many ternary relationships, 96, 137 Materialized views, 167 metadata, 177 selection of, 173–76 Measures, 159 Multidimensional databases (MDDs), 151 Multiplicities illustrated, 38 many-to-many, 39 one-to-many, 39 one-to-one, 39 Multivalued attributes, 15, 57 Multivalued dependencies (MVDs), 127–29 defined, 127–28 inference rules, 129 nontrivial, elimination, 129 Teorey.book Page 270 Saturday, July 16, 2005 12:57 PM Index 271 N-ary relationships, 28–29, 92–101 ER model, 93–96 UML, 42, 97–100 variations, 92 Nodes, 46, 47 Nonredundant cover partitioning of, 125–26 search for, 125 Normal forms BCNF, 107, 115–16, 118 defined, 108 fifth (5NF), 127, 133–37 first (1NF), 109 fourth (4NF), 127, 129–33 second (2NF), 111–13 third (3NF), 113–15, 118 Normalization, 6, 107–38 accomplishment, 108–9 candidate tables derived from ER diagrams, 118–22 defined, 108 denormalization, 8 fundamentals, 107–16 Normalized tables design, 116–18 minimum set, 127 Not null constraints, 216 Objects constraint-related, 78 defined, 34 dominant, 78 One-to-many relationships, 14 binary, 85, 87, 89 binary recursive, 90, 91 defined, 18 See also Relationships One-to-many-to-many ternary associations, 99 One-to-many-to-many ternary relationships, 95 One-to-one relationships, 14 binary, 85, 86, 88 binary recursive, 90–91 defined, 18 See also Relationships One-to-one-to-many ternary associations, 98 One-to-one-to-many ternary relationships, 94 One-to-one-to-one ternary associations, 97 One-to-one-to-one ternary relationships, 93 Online Analytical Processing (OLAP), 147, 166–78 applications, 8 defined, 166 materialized view selection, 173–76 optimization, 169, 170 overview, 169–70 query optimization, 177–78 view maintenance, 176–77 views, 166, 170–72, 178 Operations defined, 35 notation, 35, 36 Optional existence, 20, 64 Packages, 43–46 contents, expanding, 45 defined, 43 relationships, 44 Physical design, 6–8 Physical model, 6 Polynomial Greedy Algorithm (PGA), 174–75 PowerBuilder, 203 PowerDesigner, 188, 211 merge process, 200 plug-in to Sybase PowerBuilder, 203 reporting features, 206 XML adoption, 210 Preintegration analysis, 67–68 Primary FDs, 118, 119 candidate table, 119 Teorey.book Page 271 Saturday, July 16, 2005 12:57 PM . illustration, 150 bus, 164 CASE tool modeling, 207–9 core requirements, 149–51 defined, 148 dimensional data modeling, 152–54 dimensional design process, 156 dimensional modeling example, 156–65 fact. 148 Denormalization, 8 Descriptors, 15 Design patterns, 204 DeZign for Databases, 190 Dimensional data modeling, 152–54 example, 156–65 process, 156 See also Data modeling Dimensions degenerate, 154 determining,. 209–10 Database design class diagrams for, 37–43 compliance checking, 204–5 knowledge of, 11 logical, 3–6, 53–54, 139–45 physical, 1, 6–8 Database life cycle, 3–8 illustrated, 4 implementation, 8 logical design,