Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
15 Cards in this Set
- Front
- Back
|
DBMS Design Methodology
|
structured approach using procedures, techniques, tools, and documentation to facilitate design
|
|
|
Database Design Phases
|
-Conceptual
-Logical -Physical |
|
|
Conceptual Design
|
Data Model construction independent of all other considerations
|
|
|
Conceptual Data Model
|
Enterprise information in its purist entity-relational form independent of any implementation details
|
|
|
Logical Database Design
|
Translates the Conceptual Data Model into the enterprise-specific application.
|
|
|
Physical Database Design
|
Process of producing the description of the database relations, file organizations, indexes, integrity constraints, and security measures.
|
|
|
Physical Design
|
Evolving the Conceptual and Logical Design into the actual DBMS application; requiring accommodation to specific application program indiosyncracies and feedback from users
|
|
|
DB Design Critical Success Factors
|
-Working with users
-Willingness to work iteratively -Willingness to revisit user/usability issues |
|
|
Conceptual Model Components
|
Comprises entity types, relationship types, attributes, attribute domains, primary keys, alternative keys
|
|
|
Conceptual Model Documentation
|
-Entity/Relationship Diagrams
-Data Dictionary |
|
|
Conceptual Data Model Validation (1)
|
Check that required transactions are supported by entities, relationships, and attributes as diagrammatically depicted
|
|
|
Conceptual Data Model Validation (2)
|
Trace each required transaction by overlaying it on the foundation ER diagram to verify legitimacy
|
|
|
Conceptual Design Steps
|
1-Identify entity types
2-Identify relationships types 3-Identify and associate attributes to Es and Rs 4-Determine attribute domains 5-Determine candidate, primary, and alternate keys 6-Consider using advanced modeling 7-Check model for redundancy 8-Validate model against user transactions 9-Review model with users |
|
|
Logical Design Steps
|
1-Derive relations for logical data model
2-Validate relations by utilizing normalizaiton 3-Validate model using transactions 4-Define integrity constraints 5-Review logical data model with user 6-Merge logical models into global model 7-Check for future growth |
|
|
Physcal Design Steps (apps sys)
|
1-Build base relations
2-Design representation of derived data 3-Catalogue general constraints 4-Analyze transactions 5-Design and build file organization 6-Set up indexes 7-Estimate disk space requirements 8-Design user views 9-Build security mechanisms 10-Build backups and redundancy 11-Test, monitor, and tune |
