RelationalDBDesign
SiteMap
Database Analysis
Database Design
Extended DB Features
Oracle SQL Extensions
Database Design
«Prev
Next»
Database Design
Database Structure
Relational Database Model
Relationally Complete
Relational Completeness
Database Structure
Linking Database Tables
SQL in RDBMS
Create Table SQL
DBMS
Database Change Management
Relational DB Structure
Database Life Cycle
Database Design Strategy
Subject Approach DB Design
Design Subject
Application Approach Design
Schema Architecture
Three Schema Arch
DBLC Design Stages
Post Design Stages
Design Tools
DB Design Strategy Conclusion
Requirements Analysis
Requirements Analysis
Define Business Objects
BO Characteristics
Business Rules Importance
Interview Data Users
Data Flow Diagram
Creating User Views
Calculated Fields
Requirements Documentation
Requirements Analysis Conclusion
Attributes and Entities
Entities Conceptual Model
Store Entity Values
Rules for Creating Identifiers
Entity Instances
Attribute Domains Types
Multivalued Attribute
Multi-Valued Attributes
Multivalued Attribute(resolve)
Entity Attribute Constraints
Module Summary
ER Diagrams
ERD Concept
Three Relationship Types
One to One Relationships
Identify one To One
One to many Relationships
Identify One to Many
Define many To Many
Identify Many To Many
Many to Many Challenges
Convert m:n to 1:n
Mandatory Optional Relationship
Optional Participation Relationships
ERD Conclusion
ERD Conventions
ER Diagram
Three Model Types
idef1x Crowsfoot Chen Models
Entity Attribute Relationship
ER Diagram Types
Crow's Foot Notation
DB Participation Types
Interview End- Users
Verbalize ER Diagram
ER diagram model Types
Business Rules - Exercise
Objective:
Identify business rules and constraints
Exercise Scoring
This exercise is worth a total of 15 points. You will receive up to five points for each correctly described constraint matching the business rules outlined below, and up to an additional five points for a correctly described business rule matching the constraint outlined below.
Background
In the preceding lesson, you learned that many (not all) business rules can be imposed on the logical schema by the database designer, who places
constraints
on table fields and relationships between tables to force business rules to be honored. These constraints are then enforced by the RDBMS.
By examining the existing database(s), you may be able to spot constraints already in place and work backwards to the business rule from which it was derived. But, more commonly, you are apprised of business rules, and must create the constraints yourself.
Instructions
Below are two business rules and one constraint. For each business rule, compose a single sentence that
generally
describes the constraint you would impose.
(A sentence might read something like this: Place a (relationship or field) constraint on .) For the constraint, compose a single sentence that posits the probable business rule.
Business rule:
No single customer order may be less than $1.00 or exceed $500.00.
Business rule:
No high-school instructor can sponsor more than two student committees.
Constraint:
Only MasterCard, VISA, and Discover button options appear on an order form.
Submitting your exercise
Type or paste your answers into the text box below, then click
Submit
to submit them and view a results page.