Managing Information Technology: HE ATA Esource
Managing Information Technology: HE ATA Esource
FIFTH EDITION
CHAPTER 5
Chapter 5 - 2
Page 135
Cataloged Named in standard ways Protected Accessible to those with a need to know Maintained with high quality
Chapter 5 - 3
Page 135
Data model overall map for business data needed to effectively manage the data
Chapter 5 - 4
Page 135
Chapter 5 - 5
Page 135
Entities things about which data are collected Attributes actual elements of data that are to be collected
Page 135
NOTE: Entities are Customer, Order, and Product. Attributes of the Customer entity could be customer last name, first name, street, city,
2005 Pearson Prentice-Hall Chapter 5 - 7
Page 135
Enterprise modeling
Top-down approach Describes organization and data requirements at high level, independent of reports, screens, or detailed specifications Not biased by how business operates today
Chapter 5 - 8
Page 136
Chapter 5 - 9
Page 136
View integration
Bottom-up approach Each report, screen, form, document produced from databases first each called a user view
Chapter 5 - 10
Page 136
Page 136
Chapter 5 - 12
Page 136-137
Chapter 5 - 13
Page 137
Chapter 5 - 14
Page 137
classes)
5. 6.
Page 138
Chapter 5 - 16
Page 138
Page 139
Chapter 5 - 18
Page 139
Security restrictions Volume and sizes List of applications that use the data
Page 139-140
Page 140
The need to manage data is permanent Data can exist at several levels Application software should be separate from the database Application software can be classified by how they treat data 1. Data capture 2. Data transfer 3. Data analysis and presentation
2005 Pearson Prentice-Hall Chapter 5 - 21
Page 140
Chapter 5 - 22
Figure 5.4
Page 142
Application software should be considered disposable Data should be captured once There should be strict data standards
Chapter 5 - 23
Page 143
Chapter 5 - 24
Page 143
Chapter 5 - 25
Page 144
Chapter 5 - 26
Page 146
Chapter 5 - 27
Page 148
Chapter 5 - 28
Page 148
Chapter 5 - 29
Page 149
Page 150
Chapter 5 - 31
Page 150-151