Scribd
Upload
1K views

Section 4 Quiz

It is important to identify and document structural and procedural business rules to ensure an accurate data model, proper data storage, and correct system functionality. Not all constraints can be modeled on an ER diagram, so any additional constraints should be documented separately. Business rules regarding shipping goods and payment deadlines are best enforced through additional programming code. Structural rules like employee department membership can be modeled, while other rules like student attendance need only be documented. Key ER diagram components include entities and relationships between entities.

Uploaded by

Rizki Rian Anugrahani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views

Section 4 Quiz

It is important to identify and document structural and procedural business rules to ensure an accurate data model, proper data storage, and correct system functionality. Not all constraints can be modeled on an ER diagram, so any additional constraints should be documented separately. Business rules regarding shipping goods and payment deadlines are best enforced through additional programming code. Structural rules like employee department membership can be modeled, while other rules like student attendance need only be documented. Key ER diagram components include entities and relationships between entities.

Uploaded by

Rizki Rian Anugrahani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1. Why is it important to identify and document structural rules?

o Ensures we know what data to store and how that data works together. (*)
o Ensures nothing. There are no benefits to be gained from documenting your Structural
Business Rules. We need to concentrate on the Procedural Business Rules only.
o Ensures we know what processes are in place and how to program them.
o All of the Above.
2. Can all constraints be modeled on an ER diagram?
o No, in which case you should let the database administrator handle them
o No, and those that cannot be modeled should be listed on a separate document to be
handled programmatically (*)
o Yes, all constraints must be modeled and shown on the ER diagram
o No, but you just explain them to the users so they can enforce them
3. A business rule such as "We only ship goods after customers have completely paid any
outstanding balances on their account" is best enforced by:
o Creating additional programming code to verify no goods are shipped until the account
has been settled in full. (*)
o Making the payment attribute optional.
o Making the payment attribute null.
o We need to trust our customers, and we know they will pay some day.
4. A business rule such as "All accounts must be paid in full within 10 days of billing" is best
enforced by:
o Making the relationship between CUSTOMER and PAYMENT fully mandatory and 1:1 on
both sides.
o Making the payment attribute mandatory.
o Creating a message to be printed on every bill that reminds the customer to pay within
ten days.
o Creating additional programming code to identify and report accounts past due. (*)
5. Which of the following is an example of a structural business rule?
o All products will have a selling price no less than 30 % greater than wholesale.
o All employees must belong to at least one department. (*)
o Buildings to be purchased by the business must be current with earthquake building
code.
o All overdue payments will have an added 10 % late fee.
6. Why is it important to identify and document business rules?
o It allows you to create a complete data model and then check it for accuracy. (*)
o It allows you to improve the client's business.
o It ensures that the data model will automate all manual processes.
o None of the above
7. How would you model a business rule that states that on a student's birthday, he does not have
to attend his classes?
o Use a supertype
o Make the attribute Birthdate mandatory
o Use a subtype
o You cannot model this. You need to document it (*)
8. All instances of the supertype must be an instance of one of the subtypes. True or False?
o True (*)
o False
9. Which of the following is true about subtypes?
o Subtypes must not be mutually exclusive.
o One instance of a supertype may belong to two subtypes.
o Subtypes must be mutually exclusive. (*)
o Subtypes should not be exhaustive.
10. A subtype is shown on an ERD as an entity with a one to many relationship to the supertype.
True or False?
o True
o False (*)
11. A supertype can only have two subtypes and no more. True or False?
o True
o False (*)
12. All instances of a subtype must be an instance of the supertype. True or False?
o True (*)
o False
13. You can only create relationships to a Supertype, not to a Subtype. True or False?
o True
o False (*)
14. All ER diagrams must have one of each of the following: (Choose two)

(Choose all correct answers)


o One or more Entities (*)
o Arcs
o Relationships between entities (*)
o At least one supertype and subtype
15. A Supertype can have only one subtype. True or False?
o True
o False (*)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy