Seminar Agenda |
 |
TOPICAL OUTLINE
A. IRM concepts
- IRM Approach vs. "Systems" Approach
- Shared data concept and its power
- Big Picture: conceptual, logical, and physical data modeling
B.
The process, rules and guidelines of logical data modeling
- Analysis of dataviews/transactions generated by process analysis to discover data element requirements
- Data element standardization
- Detecting the need for the data element
- Determining the entity/relationship of residence
- Choosing the best representation
- Fully defining the data element (pro forma shown)
- Naming the data element; naming standard
- Use of keyword/abbreviation glossaries
- Checking the Dictionary for redundant data elements
- Adding the new data element to the Dictionary
- What to do with derived data in the logical data model
- Diagraming and normalizing the data elements
- Logical bubblechart diagram and how they are used
- Rules of normalization and how to use them to organize data
- Synthesizing of multiple dataviews into the composite logical data model
- Synthesis rule; example of synthesis
- Reviewing the logical model to immunize against future business changes
C. The process, rules and guidelines of physical data modeling, and database specification
- Formalizing and weighting the design objectives/constraints
- Analyzing physical distribution; form and content of a distributed design
- Data distribution modes and their implications
- Transaction distribution modes and their implications
- Determining whether or not to store derived data
- Projecting the volume of data to be stored; adjusting if it exceeds capacity
- Analyzing security requirements; adjusting the design for special security needs
- Analyzing the design for performance of critical transactions
- Physical designer's options for changing performance characteristics
- Denormalizing and tradeoffs
- 1NF Compromise
- 2NF Compromise
- 3NF Compromise
- Analyzing the requirements for end-user or info center ad hoc usage
- Integrating and balancing all of the above in the physical design; deciding the best balanced design
- Translation of the physical model into generic DBMS architectures/DDL
D. Coordination and synchronization of the data- and process-oriented activities in the logical and physical modeling phases of the development project.
E. Extensive Workshop |
 |
