database design challenges conflicting goals
DESCRIPTION
TRANSCRIPT
![Page 1: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/1.jpg)
DATABASE DESIGN CHALLENGES: CONFLICTING GOALS
PRESENTED BY:
MARK ANGELO M. LABITIGANMary Jesette e. PEÑAOJASmaria medea e. villorente
![Page 2: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/2.jpg)
Database designer often must make design compromises that are triggered by conflicting goals such as;
• adherence to design standards• processing speed, and • information requirements
►Design StandardsThe database design must conform to design standards. Such
standards have guided you in developing logical structures that minimize data redundancies.
Without the design standards, it is nearly impossible to formulate a proper design process, to evaluate an existing design, or to trace the likely logical impart of changes in design.
![Page 3: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/3.jpg)
►Processing SpeedIn many organizations, particularly those generating large
number of transactions, high processing speeds are often a top priority in database design.
Example:A “perfect” design might use a 1:1 relationship to avoid nulls,
while a higher transaction- speed design might combine the two tables to avoid the use of additional relationship, using dummy entries to avoid the nulls. If the focus is on data- retrieval speed, you might also be force to include derived attributes in the design.
![Page 4: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/4.jpg)
►Information RequirementsThe quest for timely information might be the focus of
database design. Complex information requirements may dictate data transformations, and they may expand the number of entries and attributes within the design.
A design that meets all logical requirements and design conventions is an important goal. However, if this perfect design fails to meet the customer’s transaction speed and/ or information requirements, the designer will not have done a proper job from the end user’s point of view.
The designer must consider processing requirements and variety that all update, retrieval, and deletion options are available. Finally, a design is of little value unless the end product is capable of delivering all specified query and reporting requirements.
![Page 5: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/5.jpg)
The Complete Tiny College ERD
![Page 6: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/6.jpg)
The conceptual UML class diagram for Tiny Colleges
![Page 7: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/7.jpg)
The implementation-Ready UML class diagram for Tiny college
![Page 8: Database design challenges conflicting goals](https://reader036.vdocuments.us/reader036/viewer/2022081803/549c3fb5ac7959bf2a8b46cd/html5/thumbnails/8.jpg)
Thank You….