mis405 1301 a-01 ph 3 gp final draft for grading
TRANSCRIPT
A Database for RoboBoysMIS405-1301A-01 Database Systems
Phase 3 Group ProjectChad Davis, Jedidiah Harrison, and Sabrina Mergenthaler
Colorado Technical UniversityProfessor Anita Arceneaux
January 28, 2013
Table of Contents
Table Structure and FieldsBy Chad Davis
Primary Keys and RelationshipsBy Chad Davis
Business RulesBy Sabrina Mergenthaler
Logical and Physical ModelsBy Jedidiah Harrison
Collective References
MIS405-1301A-01
Phase 3 Group Project Slides
Table Structures and Fields
Chad Davis
Colorado Technical University Online
Professor: Anita Arceneaux
January 28, 2013
INTRODUCTION TO TABLES AND FIELDSWITHIN A DATABASE
Introduction to Table Structures
Detailed Customer List: Customer ID Primary Key and Product Foreign Key detailing the customers order and establishing a relationship between the Customer Table and the Order Table.
Basic View of Customer Table
Table and Field Structure Breakdown
Record(PK)
A Field
(Barrows, Stockman & Young, 2010).
The Field Value
Field Characters and Properties Design View
Every table and field has properties which can be setup in order to control the tables characteristics and behaviors as the Database designer sees fit.
Use the View Button here and select Design View to getto the properties of a table.
Renaming Field Values
This Highlighted Column’s “Field” can be manipulated now or later and will later be seen in the database within each of the respective tables.
(Rost, 2011)(From Phase 2 IP)
Data / Entity Relationships
Use this button to establish Relationships between tables
1
2
You will then see a relationship map containing each of the tables that were selected in the following slide.
(Hernandez, 2003)
Data /Entity Relationships Continued
Visual Diagram of what a Relationship Map between tables looks like.
(Hernandez, 2003)
Primary Key Relationship
Table and Field Integrity and Validity
Actual numerical keys assigned managed by Access
Allow the “Wizard” to assign Keys within your tables, or, opt to assign your own.
(From Phase 2 IP)
Business Rules
MIS405-1301A-01: Database Systems
Phase 3 Group Project
Sabrina Mergenthaler
Colorado Technical University Online
Professor: Anita Arceneaux
January 28, 2013
Business RulesPiece By: Sabrina Mergenthaler
What is Normalization?• Controls redundancy• Defines the parameters under which a database
operates• Aids in elimination of errors by user
What are Business Rules?• Formalized approach for indentifying and
articulating the structure of a database in order to aid in the normalization and integrity of the database
• Rules are declarations of policy or conditions • that must be satisfied
• Identified by an analyst
• Considers the constraints by which the business is held to and the capabilities the company would like to perform with the database
Generation of Business Rules
•ValidationData type, Domain of values, Reference table
•DerivationFormula or Inference
•ConstraintState Transition enabler or enforcer
•Event/Action
Automatic Triggers
•RelationshipReferential Integrity
Additional Notes on Generation
•Placing constraints on how and when and where data can be entered
•Done after or along with table design
•Part of design process because many constraints are established at the database and table levels
•Business rule implementation should be documented: how and where it is enforced in the design.
Modeling Business Rules
Analysis Steps:1 Identify Actors, Context, Objectives, Deliverables2a Identify Business Processes
Decompose Processes into ActivitiesDecompose Activities into System Operations
2b For all Activities, Define Sequence ControlsProduce Activity Dependency Diagrams
3 For all Activities, Identify Data Inputs and OutputsProduce Data Object Models
Modeling Rules: Scope
Identify Actors, Context, Objectives, DeliverablesThe Roles of Actors
Customers, Regulators, Partners, Executives, Managers, Operators
The Context of the ActorsAccounting Dept deal with debits & creditsOrdering Dept with sales and purchases
The Business GoalsTo produce error free Purchase Orders
The Business OutputsNew Customer AccountsPurchase Order Document
Create Customer Account Collection Agency
Chase Outstanding Accounts
Accounts Clerk Process Late Payments
Activity & Data Rules
Decompose Processes into Activities Activity Types:
Create… Read… Update… Delete… Derive… Calculate… Test… Validate... Constrain...
Regulatory ControlsCorporate PoliciesContractsRelationship Integrity Constraints
• Activity Decompositions Create Customer Account
Authorize CustomerMaintain CustomerCreate AccountReceive Payment
Create Customer Order
Calculate Order Total
Calculate Cust Balance
Check Cust Credit
Create Order Item
Data Rules•Model Activity Inputs and Outputs
Data ObjectsAttributes (object values and identifiers)Relationships
Testing of Business Rules
• Always test business rule implementation– What happens when rule is met?– What happens when rule is violated?
• Not much good as a data entry constraint if it fails to constrain properly• Good application or interface design will provide feedback when user
violates a constraint or rule
Levels of Enforcement
• Referential Integrity enforced at database level because it affects relationship between two tables.
• Many other business rules enforced at field and table level to ensure data integrity.
• Some rules cannot be enforced at table or field level; must be enforced in the application level.
Field Level Integrity• Constraining by use of field
properties– Data type: text, number,
Yes/No, Date/Time– Field size– Formats
• Entry and editing constraints– Required– Indexed, with or without
duplicates– Input masks– Default value– Validation Rule
Table Level Integrity• Field Comparisons
– Compare value in one field to value in another
– Comparison performed before record is saved
– Violations could display an error message or force constraint of available values
• Validation or Lookup Tables– Store generally static set of
values– Stored values used to
populate new records to ensure accuracy of data entry
Integrity & Rules
Logical and Physical Design
MIS405-1301A-01: Database Systems
Phase 3 Group Project
Jedidiah Harrison
Colorado Technical University Online
Professor: Anita Arceneaux
January 28, 2013
Logical Design Concepts
• Illustrate entities with tables
• Eliminate redundancies
• Create table access models, transactions.
• Data is arranged into Objects
• Tables are Entities
• Rows are Tuples, aka Records
• Fields / Cell-values are Attributes in each Column.
Logical Organization
• Organization is Important.• Must be easy to understand.• Easy to use and interact with.• Tables custom tailored.• Pre-plan and customize entities.
Physical Design Concepts
• Physical design should be optimized.• Reflect the Logical design.• Most accessed entities placed first.• Optimized and efficient.
ROBOBOYSModel 4567
SilverHeight: 4ft
Optional:Attachments,
Extra RAM,Personalization
References
Arceneaux, A. (2012). Live Chat. Database Systems. Colorado Technical University.
Creating and Managing Databases. (n.d.). M.U.S.E. Database Systems. Colorado Technical University. Retrieved from https://campus.ctuonline.edu/courses/MIS405/p3/hub1/4312.pdf
Hernandez, M. J. (2003). Database Design for Mere Mortals™: A Hands-On Guide to Relational Database Design (Second ed.). Boston, MA: Addison-Wesley Professional.
Kroenke, D. (2010). MIS Essentials. Upper Saddle River, New Jersey: Prentice Hall.
Rost, R. (Designer) (2011). Learning access 101 [Web]. Retrieved from http://599cd.com/Access/Microsoft-Access-101-FREE- Preview/?key=YOUTUBE_AC2010B1_FREE_ORGANIC&QCode=X0DIZX
Oracle (1997). Guide to Database Design and Definition. Retrieved from: http://preview.tinyurl.com/OracleGuideDBDesign.
Barrows, A., Stockman, J., & Young, M. (2010). Access 2010 all-in- one for dummies. (1st ed., pp. 67-179). Hoboken, NJ: Wiley Publishing Inc.