Database Analysis II,,. II.. 3 ( ),.,..,, ;. (strong) (weak), (identifying relationship). (required) (optional), (simple) (composite), (single-valued) (multivalued), (derived), (identifier). (associative entity). (unary), (binary), (ternary) (degree). (cardinality).. E-R Pine Valley Furniture Company. Microsoft Visio. 4 ( E-R )
118 II, ERD.. (enhanced entity-relationship: EER) (supertype)/(subtype)., ( ), ( ).,. /. (generalization) (specialization) /. / (universal), 4., (clustering). ERD...,, EER. UML, (objectoriented). V 15., 4 15. II. E-R.
03 Modeling Data in the Organization
120 II
121
122 II
123.,.
124 II
125
126 II
127..
128 II
129
130 II,. E-R.
131
132 II <> < > < > < > <> < > < > < > <> <>
133
134 II,,,...
135
136 II....
137
138 II
139...
140 II.
141..
142 II. ( ).
143.
144 II
145
146 II
147.,.
148 II,.
149
150 II..
151
152 II
153..
154 II
155
156 II ( ).
157..
158 II
159
160 II ( ).
161
162 II
163
164 II
165
166 II
167
168 II
169
170 II
171
172 II
173
174 II
175
176 II
177
178 II
179
180 II
181
182 II
183
184 II
185
186 II
187
188 II
189
190 II Aranow, E. B. 1989. Developing Good Data Definitions. Database Programming & Design 2,8 (August): 36 39. Batra, D., J. A. Hoffer, and R. B. Bostrom. 1988. A Comparison of User Performance Between the Relational and Extended Entity Relationship Model in the Discovery Phase of Database Design. Proceedings of the Ninth International Conference on Information Systems. Minneapolis, November 30 December 3: 295 306. Bruce, T. A. 1992. Designing Quality Databases with IDEF1X Information Models. New York: Dorset House. Chen, P. P.-S. 1976. The Entity-Relationship Model Toward a Unified View of Data. ACM Transactions on Database Systems 1,1(March): 9 36. Elmasri, R., and S. B. Navathe. 1994. Fundamentals of Database Systems. 2d ed. Menlo Park, CA: Benjamin/Cummings. Gottesdiener, E. 1997. Business Rules Show Power, Promise. Application Development Trends 4,3 (March): 36 54. Gottesdiener, E. 1999. Turning Rules into Requirements. Application Development Trends 6,7 (July): 37 50. Hay, D. C. 2003. What Exactly IS a Data Model? Parts 1, 2, and 3 DM Review Vol 13, Issues 2 (February: 24 26), 3(March: 48 50), and 4 (April: 20 22, 46). GUIDE. GUIDE Business Rules Project. Final Report, revision 1.2. October 1997. Hoffer, J. A., J. F. George, and J. S. Valacich. 2005. Modern Systems Analysis and Design. 4th
191 ed. Upper Saddle River, NJ: Prentice Hall. ISO/IEC. 2004. Information Technology Metadata Registries (MDR) Part 4: Formulation of Data Definitions. July. Switzerland. Available at http://metadata-standards.org /11179. ISO/IEC. 2005. Information Technology Metadata Registries (MDR) Part 5: Naming and Identification Principles. September. Switzerland. Available at http://metadatastandards.org/11179. Moriarty, T. 2000. The Right Tool for the Job. Intelligent Enterprise 3,9 (June 5): 68, 70 71. Owen, J. 2004. Putting Rules Engines to Work. InfoWorld (June 28): 35 41. Plotkin, D. 1999. Business Rules Everywhere. Intelligent Enterprise 2,4 (March 30): 37 44. Salin, T. 1990. What s in a Name? Database Programming & Design 3,3 (March): 55 58. Song, I.-Y., M. Evans, and E. K. Park. 1995. A Comparative Analysis of Entity-Relationship Diagrams. Journal of Computer & Software Engineering 3,4: 427 59. Storey, V. C. 1991. Relational Database Design Based on the Entity-Relationship Model. Data and Knowledge Engineering 7: 47 83. Teorey, T. J., D. Yang, and J. P. Fry. 1986. A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model. Computing Surveys 18, 2(June): 197 221. von Halle, B. 1997. Digging for Business Rules. Database Programming & Design 8,11: 11 13. Batini, C., S. Ceri, and S. B. Navathe. 1992. Conceptual Database Design: An Entity- Relationship Approach. Menlo Park, CA: Benjamin/ Cummings. Bodart, F., A. Patel, M. Sim, and R. Weber. 2001. Should Optional Properties Be Used in Conceptual Modelling? A Theory and Three Empirical Tests. Information Systems Research 12,4 (December): 384 405. Carlis, J., and J. Maguire. 2001. Mastering Data Modeling: A User-Driven Approach. Upper Saddle River, NJ: Prentice Hall. Keuffel, W. 1996. Battle of the Modeling Techniques. DBMS 9,8 (August): 83, 84, 86, 97. Moody, D. 1996. The Seven Habits of Highly Effective Data Modelers. Database Programming & Design 9,10(October): 57, 58, 60 62, 64. Teorey, T. 1999. Database Modeling & Design. 3d ed. San Francisco, CA: Morgan Kaufman. Tillman, G. 1994. Should You Model Derived Data? DBMS 7,11 (November): 88, 90. Tillman, G. 1995. Data Modeling Rules of Thumb. DBMS 8,8 (August): 70, 72, 74, 76, 80 82, 87.
192 II
193
194 II
195
196 II