The University Lab: Conceptual Design, Verification, Logical Design, and Implementation | Complete Database Systems Design Project | ER Modeling, Logical Design & Database Implementation Solutions

Appendix C The University Lab: bv bv bv bv


Conceptual Design Verification, Logical Design, and bv bv bv bv bv


Implementation bv



Appendix C bv




The University Lab: Conceptual Design, bv bv bv bv




bv Verification,Logical Design, and Implementation vb bv bv bv




Discussion Focus bv




How is a database design verified, and why is such verification necessary?
bv bv bv bv bv bv bv bv bv bv bv




Use our detailed answer to question 1 to focus class discussion on database design verification.
bv bv bv bv bv bv bv bv bv bv bv bv bv bv


Stress that the verification process uses the initial ER model as a communication tool.
bv bv bv bv bv bv bv bv bv bv bv bv bv bv




The designer may begin the verification process by describing the organization's operations to its
bv bv bv bv bv bv bv bv bv bv bv bv bv


end users, basing the detailed description on the initial ER model. Next, explain how the
bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv


operations will be supported by the database design. Stress that the design must support the
bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv


end-user application views, outputs, and inputs. Points to be addressed include such questions
bv bv bv bv bv bv bv bv bv bv bv bv bv


as:
bv




 Is the description accurate? If not, what aspects of the description must be corrected?
bv bv bv bv bv bv bv bv bv bv bv bv bv


 Does the model support the end-user requirements? If not, what aspects of
b v b v b v b v b v b v b v b v b v b v b v


bvthe end-userrequirements have not been addressed or have been addressed
b v bv bv bv bv bv bv bv bv bv


inadequately?
bv




Keep in mind that even a model that perfectly addresses all initially determined end user
bv bv bv bv bv bv bv bv bv bv bv bv bv bv


requirements is likely to need adjustments as those end users begin to understand the
bv vb bv bv bv bv bv bv bv bv bv bv bv bv


ramifications of the database design's capabilities. In many cases, the end users may learn what
bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv


the organization's processes and procedures actually are, thus leading to new requirements and
bv bv bv bv bv bv bv bv bv bv bv bv bv


the perception of new opportunities. The database designer must keep such likely developments
bv bv bv bv bv bv vb bv bv bv bv bv bv


in mind, especially if (s)he works as a database design consultant. (Anticipation of such
bv bv bv bv bv bv bv bv bv bv bv bv bv bv


developments must be factored into the contract negotiations for consulting fees.)
bv bv bv bv bv bv bv bv bv bv bv




Discuss the role of the system modules.
bv bv bv bv bv bv




1

, Appendix C The University Lab: bv bv bv bv


Conceptual Design Verification, Logical Design, and
bv bv bv bv bv


Implementation bv




The use of system modules can hardly be overemphasized in a database design
bv bv bv bv bv bv bv bv bv bv bv bv


environment. Stressthese module characteristics and features:
bv bv vb bv bv bv bv




 Modules represent subsets of the database model: Smaller "pieces" are more
bv bv bv bv bv bv bv bv bv bv


easilyunderstood.
bv bv


 Modules are self-contained and accomplish a specific system function; if such a
bv bv bv bv bv bv bv bv bv bv bv


system function must be modified, other functions remain unaffected.
bv bv bv bv bv bv bv bv bv


 Modules fit into a modular database design, which is more easily modified and
bv bv bv bv bv bv bv bv bv bv bv bv


adapted to new circumstances. Because modification efforts are focused on a
bv bv bv bv bv bv bv bv bv bv bv


database subset, productivity of both designers and application developers is likely
bv bv bv bv bv bv bv bv bv bv bv


to be enhanced.
bv bv bv




Module interfaces must be clear if the modules are expected to work well within the overall system.
bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv




2

, Appendix C The University Lab: bv bv bv bv


Conceptual Design Verification, Logical Design, and bv bv bv bv bv


Implementation bv

Answers to Review Questions
bv bv bv




1. Why must a conceptual model be verified? What steps are involved in the verification process?
bv bv bv bv bv bv bv bv bv bv bv bv bv bv




The verification of a conceptual model is crucial to a successful database design. The
bv bv bv bv bv bv bv bv bv bv bv bv bv


verification process allows the designer to check the accuracy of the database design by:
bv bv bv bv bv bv bv bv bv bv bv bv bv bv




 Re-examining data and data transformations. bv bv bv bv


 Enabling the designer to evaluate the design efficiency relative to the end
bv bv bv bv bv bv bv bv bv bv bv


user's andsystem's design goals.
bv bv bv bv bv




Keep in mind that, to a large extent, the best design is the one that serves the end-user
bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv b v


requirements best. For example, a design that works well for a manufacturing firm may not
bv bv bv bv bv bv bv bv bv bv bv bv bv bv bv


fit the needs of a marketing research firm, and vice versa.
bv bv bv bv bv bv bv bv bv bv bv




The verification process helps the designer to avoid implementation problems later by:
bv bv bv bv bv bv bv bv bv bv bv




 Validating the model's entities. (Remember the minimal data rule.)
bv bv bv bv bv bv bv bv


 Confirming entity relationships and eliminating duplicate, unnecessary, or
bv bv bv bv bv bv bv


improperlydefined relationships.
bv bv bv


 Eliminating data redundancies. bv bv


 Improving the model's semantic precision to better represent real-world operations.
bv bv bv bv bv bv bv bv bv


 Confirming that all user requirements (processing, performance, or security) are met.
bv bv bv bv bv bv bv bv bv bv




Verification is a continuous activity in any database design. The database design process is
bv bv bv bv bv bv bv bv bv bv bv bv bv


evolutionary in nature: It requires the continuous evaluation of the developing model by
bv bv bv bv bv bv bv bv bv bv bv bv bv


examining the effect of adding new entities and by confirming that any design changes
bv bv bv bv bv bv bv bv bv bv bv bv bv bv


enhance the model's accuracy.
bv bv bv bv




The verification process requires the following steps:
bv bv bv bv bv bv




1. Identify the database's central entity. bv bv bv bv




The central entity is the most important entity in our database, and
b v b v b v b v b v b v b v b v b v b v b v


most of the otherentities depend on it.
b v b v b v b v vb bv bv bv




3

, Appendix C The University Lab: bv bv bv bv


Conceptual Design Verification, Logical Design, and
bv bv bv bv bv


Implementation bv




2. Identify and define each module and its components.
bv bv bv bv bv bv bv




The designer divides the database model into smaller sets that reflect the
bv bv bv bv bv bv bv bv bv bv bv


data needs ofparticular systems modules such as inventory, orders, payroll, etc.
bv bv bv vb bv bv bv bv bv bv bv bv




3. Identify and define each of the module's processes.
bv bv bv bv bv bv bv




Specifically, this step requires the identification and definition of the database transactions
bv bv bv bv bv bv bv bv bv bv bv


that represent the module's real-world operations.
bv bv bv bv bv




4