Conceptual Design Verification, Logical Design, and Implementation cn cn cn cn cn cn
Appendix C cn
The UniversityLab: ConceptualDesign, Verification, cn cn cn cn cn
Logical Design,and Implementation cn cn cn cn
Discussion Focus cn
How is a database design verified, and why is such verification necessary?
cn cn cn cn cn cn cn cn cn cn cn
Use our detailed answer to question 1 to focus class discussion on database design verification. Stress that
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
the verification process uses the initial ER model as a communication tool.
cn cn cn cn cn cn cn cn cn cn cn cn
The designer may begin the verification process by describing the organization's operations to its end users,
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
basing the detailed description on the initial ER model. Next, explain how the operations will be supported by
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
the database design. Stress that the design must support the end-user application views, outputs, and
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
inputs. Points to be addressed include such questions as:
cn cn cn cn cn cn cn cn cn
• Is the description accurate? If not, what aspects of the description must be corrected?
cn cn cn cn cn cn cn cn cn cn cn cn cn
• Does the model support the end-user requirements? If not, what aspects of the end-
c n c n c n c n c n c n c n c n c n c n c n c n c n
userrequirements have not been addressed or have been addressed inadequately?
cn cn cn cn cn cn cn cn cn cn
Keep in mind that even a model that perfectly addresses all initially determined end user requirementsis
cn cn cn c n cn cn c n cn cn cn cn cn cn cn c n cn
likely to need adjustments as those end users begin to understand the ramifications of the database design's
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
capabilities. In many cases, the end users may learn what the organization's processes and procedures
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
actually are, thus leading to new requirements and the perception of new opportunities. The database
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
designer must keep such likely developments in mind, especially if (s)he works as a database design
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
consultant. (Anticipation of such developments must be factored into the contract negotiations for
cn cn cn cn cn cn cn cn cn cn cn cn cn
consulting fees.)
cn cn
Discuss the role of the system modules. cn cn cn cn cn cn
1
, Appendix C The University Lab: cn cn cn cn
Conceptual Design Verification, Logical Design, and Implementation cn cn cn cn cn cn
The use of system modules can hardly be overemphasized in a database design environment.
c n c n c n c n c n c n c n c n c n c n c n c n c n
cStressthese module characteristics and features:
n cn cn cn cn cn
• Modules represent subsets of the database model: Smaller "pieces" are more easily
cn cn cn cn cn cn cn cn cn cn cn
understood.
cn
• Modules are self-contained and accomplish a specific system function; if such a system
cn cn cn cn cn cn cn cn cn cn cn cn
function must be modified, other functions remain unaffected.
cn cn cn cn cn cn cn cn
• Modules fit into a modular database design, which is more easily modified and adapted tonew
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
circumstances. Because modification efforts are focused on a database subset, productivity of
cn cn cn cn cn cn cn cn cn cn cn cn
both designers and application developers is likely to be enhanced.
cn cn cn cn cn cn cn cn cn cn
Module interfaces must be clear if the modules are expected to work well within the overall system.
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
2
, Appendix C The University Lab: cn cn cn cn
Conceptual Design Verification, Logical Design, and Implementation cn cn cn cn cn cn
Answers to Review Questions cn cn cn
1. Why must a conceptual model be verified? What steps are involved in the verification process?
cn cn cn cn cn cn cn cn cn cn cn cn cn cn
The verification of a conceptual model is crucial to a successful database design. The verification process
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
allows the designer to check the accuracy of the database design by:
cn cn cn cn cn cn cn cn cn cn cn cn
• Re-examining data and data transformations. cn cn cn cn
• Enabling the designer to evaluate the design efficiency relative to the end user's and c n c n c n c n c n c n c n c n c n c n c n c n c n
system's design goals.
cn cn cn
Keep in mind that, to a large extent, the best design is the one that serves the end-user requirements
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn c n cn
best. For example, a design that works well for a manufacturing firm may not fit the needs of a marketing
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
research firm, and vice versa.
cn cn cn cn cn
The verification process helps the designer to avoid implementationproblems later by:
cn cn cn cn cn cn cn cn cn cn cn
• Validating the model's entities. (Remember the minimal data rule.) cn cn cn cn cn cn cn cn
• Confirming entity relationships and eliminating duplicate, unnecessary, or improperly cn cn cn cn cn cn cn cn
defined relationships.
cn cn
• Eliminating data redundancies. cn cn
• Improving the model's semantic precision to better represent real-world operations. cn cn cn cn cn cn cn cn cn
• Confirming that all user requirements (processing, performance, or security) are met. cn cn cn cn cn cn cn cn cn cn
Verification is a continuous activity in any database design. The database design process is evolutionary
cn cn cn cn cn cn cn cn cn cn cn cn cn cn
in nature: It requires the continuous evaluation of the developing model by examining the effect of
cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn cn
adding new entities and by confirming that any design changes enhance the model's accuracy.
cn cn cn cn cn cn cn cn cn cn cn cn cn cn
The verification process requires the following steps:
cn cn cn cn cn cn
1. Identify the database's central entity. cn cn cn cn
The central entity is the most important entity in our database, and most of
c n c n c n c n c n c n c n c n c n c n c n c n c n
cthe otherentities depend on it.
n c n cn cn cn cn
3
, Appendix C The University Lab: cn cn cn cn
Conceptual Design Verification, Logical Design, and Implementation
cn cn cn cn cn cn
2. Identify and define each module and its components.
cn cn cn cn cn cn cn
The designer divides the database model into smaller sets that reflect the data
c n c n c n c n c n c n c n c n c n c n c n c n
cneeds ofparticular systems modules such as inventory, orders, payroll, etc.
n c n cn cn cn cn cn cn cn cn cn
3. Identify and define each of the module's processes.
cn cn cn cn cn cn cn
Specifically, this step requires the identification and definition of the database transactions
cn c n c n c n c n c n c n c n c n c n c n
that represent the module's real-world operations.
cn cn cn cn cn
4