Some examples of simple business rules:

Slides:



Advertisements
Similar presentations
Business Processes, Data Modeling and Information Systems
Advertisements

CIS458 Organizational Database Management Sungchul Hong
Accounting System Design
Entity Relationship Diagrams
Ch5: Software Specification. 1 Descriptive specifications  Describe desired properties of system  Three types:
1 Database Design Victor Matos. 2 Phases of Database Design u Conceptual design begins with the collection of requirements and results needed from the.
Implementing an REA Model in a Relational Database
Database Design Using the REA Data Model
Entity Relationship Model Chapter 6. Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier,
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 15, Section 1 Purchasing Items Needed by a Business
Practice of ER modeling
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 96 C HAPTER 17 Special Topics in REA Modeling for the.
Entity Relationship Diagrams (ERDs). Entity Relationship Diagram (ERD) documentation technique to represent relationship between entities in system. Think.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj InClass ER Examples.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Advanced Accounting Information Systems Day 7 Database Modeling.
IT 21103/41103 System Analysis & Design. Chapter 04 Data Modeling.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj ER Model Lecture 2 © Akhilesh Bajaj, 2000, 2002, 2003, 2004,
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
Entity Relationship Diagrams (ERDs)
Lecture 5 Entity Relationship Modeling
ENTITY RELATIONSHIP DIAGRAM. Objectives Define terms related to entity relationship modeling, including entity, entity instances, attribute, relationship.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Entity/Relationship Modelling
©2005 The McGraw-Hill Companies, All rights reserved McGraw-Hill/Irwin
Let try to identify the conectivity of these entity relationship
Semantic Object Modeling (SOM)
Management Movie Management System Customers Databases Vendors
Chapter 4: Logical Database Design and the Relational Model
Event-driven accounting information systems
Case Studies: Data Modeling
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
© The McGraw-Hill Companies, All Rights Reserved APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Implementing an REA Model in a Relational Database
The Jonesburgh County Basketball Conference (JCBC) is an amateur basketball  association. Each city in the county has one team that represents it.  Each.
Entity-Relationship Modeling
Lecture on Data Modeling and Analysis
Implementing an REA Model in a Relational Database
Databases and Information Management
Accounting System Design
Data Modelling Introduction
ERD’s REVIEW DBS201.
Practice of ER modeling
Relational Database.
ERD Exercises.
Practice of ER modeling
Sales/Collection Process
Database Systems: Design, Implementation, and Management Tenth Edition
MIS2502: Data Analytics Relational Data Modeling
Bookstore DB Requirements
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
Accounting System Design
Databases and Information Management
Database Systems Instructor Name: Lecture-9.
Chapter 3: Modeling Data in the Organization
Relationships—Topics
MIS2502: Data Analytics Relational Data Modeling
MIS2502: Data Analytics Relational Data Modeling 2
E.R. Examples.
Database Management system
Database Management system
Conceptual Data Modeling
DFD Process & Examples.
Presentation transcript:

CIS 381 – Database Systems ENTITY RELATIONSHIP DIAGRAM (ERD) FUNCTIONAL DECOMPOSTION

Some examples of simple business rules: There are several protocols to the way business rules are written. Not every protocol has to be followed, but in general, a well-written set of business rules consist of having a unique identifier, describes one and only one concept, are written in plain language, are written, and are from a single source. In terms of a unique identifier, business rules should come with an identifier that may consist of the rule number and the department it affects. Some examples of simple business rules: Department ------ offers --------- Courses Course ---------- generates ------ Class Professor ------- teaches -------- Class

Business Entities CUSTOMER A person or organization who has ordered or might order products. PRODUCT A type of furniture made by Pine Valley Furniture that may be ordered by customers. Note that a product is not a specific bookcase, because individual bookcases do not need to be tracked. ORDER The transaction associated with the sale of one or more products to a customer and. identified by a transaction number from sales or accounting. ITEM A type of component that goes into making one or more products and can be supplied by one or more suppliers. SUPPLIER Another company that may provide items to Pine Valley Furniture. SHIPMENT The transaction associated with items received in the same pack- age by Pine Valley Furniture from a supplier. All items in a shipment appear on one bill-of-lading document.

Rules for Drawing an E-R Diagram

Business Rules Example Note that these business rules roughly follows a certain grammar: <entity> <minimum cardinality> <relationship> <maximum cardinality> <entity> For example <A SHIPMENT> <must> < include>< one or more> < ITEMs> OR <ITEM> <may> <be included><on several><SHIPMENTs> This grammar gives you a standard way to put each relationship into a natural English business rule statement.

Business ERD Example

Shipment-Supplier Example A SUPPLIER may send many SHIPMENTs. Each shipment must be sent by exactly one SUPPLIER. (Notice that sends and supplies are separate concepts. A SUPPLIER may be able to supply an item, but may not yet have sent any shipments of that item).

A SHIPMENT must include one (or more) ITEMs. Shipment-Item Example A SHIPMENT must include one (or more) ITEMs. An ITEM may be included on several SHIPMENTs.

Supplier-Item Example A SUPPLIER may supply many ITEMs (by "may supply" we mean the supplier may not supply any items) . Each ITEM is supplied by any number of SUPPLIERs (by "is supplied" we mean that the item must be supplied by at least one supplier) .

Item-Product Example Each ITEM must be used in the assembly of at least one PRODUCT, and may be used in many products. Each PRODUCT must use one or more ITEMs.

An ORDER must request one (or more) PRODUCTs. Product-Order Example A given PRODUCT may not be requested on any ORDER, or may be requested on one or more orders. An ORDER must request one (or more) PRODUCTs.

Customer-Order Example A CUSTOMER may submit any number of ORDERs. Each ORDER must be submitted by exactly one CUSTOMER.