BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor...

5
BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor Faculty of Business, OUC

Transcript of BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor...

Page 1: BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor Faculty of Business, OUC.

BUAD 283: Management Info Systems

Database DesignAssignment #1

Glen J. Coulthard, InstructorFaculty of Business, OUC

Page 2: BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor Faculty of Business, OUC.

Slide 2

Specific Requirements (1/2)

Report Structure:Letter of Understanding (LU) or Transmittal Memo (TM)

A. Statement of Problem or Opportunity

B. Description of Entity Classes (Tables)

C. Identification of Attributes (Fields) and Keys (PK and FK)

D. Diagram of Logical Relationships (E-R diagram)

E. Discussion of Relationship Rules, Constraints, & Assumptions

F. Proposed Report Structures (min 3 pages; max 5)

G. Summary/Conclusion: How does this solve my problem?

Appendices: E-R Diagram, Sample Reports, Data Dictionary

No Executive Summary necessary; info contained in LU or TM

Page 3: BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor Faculty of Business, OUC.

Slide 3

Specific Requirements (2/2)

If used, please cite references properly using “APA Style”

Not www.zdnet.com; instead, use:

Doherty, S. (2002, March 18). Managing data. Ziff-Davis Publishing. [On-line]. Retrieved from http://www.zdnet.com/1306ws1.htm.

Not “Management Information Systems textbook;” instead, use:

Haag, S., Cummings, M., et al. (2004). Management information systems for the information age. Toronto, ON: McGraw-Hill Ryerson.

Page 4: BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor Faculty of Business, OUC.

Slide 4

Data Modeling Concepts

Logical versus PhysicalLogical: Entity Relationship (E-R) diagramming

Physical: Creating and relating tables in Microsoft Access

Basic components of an E-R DiagramEntity (Table)

Attribute (Field)

Relationship

Basic components of a Data Dictionary

FieldName TableRelation KeyField DataType Precision Description

CustomerID Customer Primary Numeric 9,0 Unique customer number

Surname Customer Text 20 Family or last name

Page 5: BUAD 283: Management Info Systems Database Design Assignment #1 Glen J. Coulthard, Instructor Faculty of Business, OUC.

Slide 5

E-R Diagramming Software Tools

Microsoft ExcelUse the drawing tools

Microsoft Visio drawing programhttp://www.microsoft.com/office/visio

CASE Studio 2 by CharonWarehttp://www.casestudio.com/

DeZign for Databases by Datanamichttp://www.datanamic.com/dezign

DDS-Lite or DDS-Pro from Chilli Sourcehttp://www.dds-lite.comhttp://www.dds-pro.com