Chapter 2 Role of Information Systems in Organizations Link 2

Slides:

Advertisements

Similar presentations

Concepts of Database Management Seventh Edition Chapter 6 Database Design : ERD Model.

Advertisements

Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.

Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.

Chapter 9 - Implementing Association Relationships1 Chapter 9 Implementing Association Relationships.

Data Modeling and Relational Database Design. Analyze and model the relationships between entities Draw an initial entity relationship diagram Read the.

DATABASEMODELSDATABASEMODELS  A database model ◦ defines the logical design of data. ◦ Describes the relationships between different parts of data.

Jozef Kuper.  Describe a Database  Entities  Atributes  Relationships.

Lesson 2: Designing a Database and Creating Tables.

Social Roles and Relationships.

INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.

© 2006 The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.

Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 2: MODELING DATA.

Tutorial on E-R Diagrams 1.Learn basic terminology and symbols –See next four slides; refer to as needed in steps 2-4 below 2.Learn the basics of E-R diagramming.

The Gaps Model of Service Quality

THE MOUSE Left Click THE MOUSE Right Click.

OPS 571 Week 1 DQ 2 To purchase this material click below link 571/OPS-571-Week-1-DQ-2 Some suggest that customer expectation.

HCS 430 Week 1 DQ 1 Who should be responsible for governing health care delivery in the United States? What should the role of the government be, if any?

ISCOM 424 Week 3 DQ 2 How has information technology changed customers’ expectations of product quality and delivery? What supply chain management information.

BSA 385 Week 3 Individual Assignment Frequent Shopper Program Part 2 Check this A+ tutorial guideline at

Data Modeling Using the Entity- Relationship (ER) Model

Database Design Chapters 17 and 18.

Core LIMS Training: Key Concepts & Definitions.

Data Modeling and the Entity-Relationship Model

TMC2034 Database Concept and Design

Chen’s Type Guidance.

CSIS 115 Database Design and Applications for Business

Requirements Become the E-R Data Model

© The McGraw-Hill Companies, All Rights Reserved APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.

Entity-Relationship Model

Database Design – Lecture 4

Figure Specialization Hierarchy

Customer Relationship Management

Customer Relationship Management

Customer Relationship Management

Customer Relationship Management

Customer Relationship Management

Customer Relationship Management

Seminar 4 UML Object Diagram.

Customer Contract Management Scenario Overview

Overview of Entity‐Relationship Model

Chapter 9 Use Cases.

5.02 Understand database queries, forms, and reports used in business.

Database Systems: Design, Implementation, and Management Tenth Edition

Database Systems Instructor Name: Lecture-11.

Database Design Chapters 17 and 18.

Database Systems Instructor Name: Lecture-10.

Customer Contract Management Scenario Overview

Entities Things about which you need to store data. One entity for each different thing. At least two attributes At least two occurrences Not a property.

Chapter 3: Modeling Data in the Organization

Logical Data Model – step-by-step instructions and template

STORE MANAGER RESPONSIBILITIES.

Relationships—Topics

Chapter 4 Entity Relationship (ER) Modeling

Database Processing: David M. Kroenke’s Chapter Five:

Guide to Modeling Keys to E-R diagrams.

Microsoft Access - A Primer for Relational Database Design and Use

Weak Entities (cont…) Entities that do not have key attributes of their own Related to specific entities from another entity type plus their own attributes.

Chapter 7 Structuring System Requirements: Conceptual Data Modeling

CLICK TO START.

Guide to Modeling Keys to E-R diagrams.

CLICK TO START.

Entity Relationship (ER) Modeling

Chapter # 4 Entity Relationship (ER) Modeling.

© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke

Entity-Relationship Design

Call Now : Click : -

Call Now : Click : -

Call Now : Click : -

Presentation transcript:

Chapter 2 Role of Information Systems in Organizations Link 2 Chapter 2 Role of Information Systems in Organizations Link 2.1 Reading the Information Architecture Figure 2.12

Click the mouse to see how to read this model. places 1 CUSTOMER n ORDER This reads as: One customer may place many orders. This means that customer data can be stored without the need for a customer to place an order. Over time, a customer may place more than one order with the organization. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. places 1 CUSTOMER n ORDER This reads as: An order must be placed by one customer. This means that order data cannot be stored without the order being related to an existing customer. One order must be related to only one customer. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. CUSTOMER receives 1 n DELIVERY This reads as: One customer may receive many deliveries. This means that customer data can be stored without the need for a customer to receive a delivery. Over time, a customer may receive more than one delivery from the organization. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. CUSTOMER receives 1 n DELIVERY This reads as: One delivery must be received by one customer. This means that delivery data cannot be stored without the data being related to an existing customer. One delivery must only be related to one customer. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. DELIVERY dispatches m n PRODUCT This reads as: One delivery must dispatch one or more products. This means that delivery data cannot be stored without the data being related to an existing product. One delivery can be for one product, or more than one product. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. DELIVERY dispatches m n PRODUCT This reads as: One product may be dispatched by one or more deliveries This means that product data can be stored without the data being related to an existing delivery. One product may be subject of 0, 1 or more deliveries. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. Is for ORDER PRODUCT n This reads as: One order must be for one or more products. This means that order data cannot be stored without the data being related to an existing product. One order must be for one product, or more than one product. Click the mouse to see how to read this model.

Click the mouse to see how to read this model. Is for ORDER PRODUCT n This reads as: One product may be for one or more orders. This means that product data can be stored without the data being related to an order. A product can be included on 0, 1 or more orders. Click the mouse to see how to read this model.

Key to Notation ENTITY relationship Group of data. Structure or action that connects entities together. Optional relationship. Entity can exist without being associated with an instance of the entity at the other end of the relationship. 1 One instance of an entity. n Many instances of an entity in a one to many relationship. Mandatory relationship. Entity cannot exist without being associated with an instance of the entity at the other end of the relationship. m Many instances of an entity in a many to many relationship.