(Winter 2017) Instructor: Craig Duckett

Slides:



Advertisements
Similar presentations
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
Advertisements

0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
Entity-Relationship Model and Diagrams (continued)
ENTITY RELATIONSHIP DATA MODEL ELIZABETH GEORGE. INTRODUCTION Architect Aeronautical engineers Computer architects Traffic engineers.
Keys Chapter 8 Database Design for Mere Mortals. Why Keys Are Important They ensure that each record in a table can be properly identified. They help.
Establishing Table Structures Chapter 7 Database Design for Mere Mortals.
Project Communications Management J. S. Chou Assistant Professor.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Conceptual Design Lecture - 2 Database Development.
(Spring 2015) Instructor: Craig Duckett Lecture 10: Tuesday, May 12, 2015 Mere Mortals Chap. 7 Summary, Team Work Time 1.
Database Design – Lecture 4 Conceptual Data Modeling.
(Spring 2015) Instructor: Craig Duckett Lecture 08: Tuesday, May 5, 2015 Mere Mortals Chap. 6 Summary, Team Work Time 1.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
1 Project Communications Management Lecture 11. Learning Objectives Describe the importance of good communication on projects and major components of.
(Winter 2016) Instructor: Craig Duckett Lecture 15: Thursday, February 25 th Visual Studio Walk-Through 1.
(Winter 2016) Instructor: Craig Duckett Lecture 13: Thursday, February 18 th Mere Mortals: Chap. 9 Summary, Team Work 1.
(Spring 2015) Instructor: Craig Duckett Lecture 07: Tuesday, April 28, 2015 PHASE 1: Discovery DUE TONIGHT 1.
(Winter 2016) Instructor: Craig Duckett
Data Modeling (Entity Relationship Diagram) Farrokh Alemi, Ph.D. Updated by Janusz Wojtusiak (Fall 2009)
IT 499 Bachelor Capstone Week 2. Adgenda Administrative Review UNIT One UNIT Two Project UNIT Three Preview Project Status Summary.
(Spring 2015) Instructor: Craig Duckett Lecture 14: Thursday, May 12 th, 2016 Visual Studio Community Edition 1.
ASH PSY 496 Week 1 Assignment Foundations for the Final Paper Check this A+ tutorial guideline at
Chapter 3: Modeling Data in the Organization
DATA MODELING AND DATABASE DESIGN
Data Modeling (Entity Relationship Diagram)
(Winter 2017) Instructor: Craig Duckett
Business System Development
(Winter 2017) Instructor: Craig Duckett
(Winter 2017) Instructor: Craig Duckett
(Winter 2017) Instructor: Craig Duckett
Inception/Elaboration
(Winter 2017) Instructor: Craig Duckett
Company Name Report Title.
(Winter 2017) Instructor: Craig Duckett
Database Design – Lecture 4
Collaboration Toolbox Context
Design a Relational Database Identify Database Purpose
Information Systems in Organizations 2. 1
DBM 380 Competitive Success/snaptutorial.com
DBM 380 Education for Service/snaptutorial.com
DBM 380 Teaching Effectively-- snaptutorial.com
Entity-Relationship Model and Diagrams (continued)
Order Database – ER Diagram
(Winter 2017) Instructor: Craig Duckett
(Winter 2017) Instructor: Craig Duckett
TEAM PRESENTATIONS PHASE 05 DUE
Information Systems in Organizations 2. 1
5.02 Understand database queries, forms, and reports used in business.
Requirements Walk-through
Instructor: Craig Duckett
PREP Instructor: Craig Duckett Lecture 07: Tuesday, April 19th , 2016
Database Systems Instructor Name: Lecture-11.
Lecture1: Introduction to IT322 Software Engineering I
(Winter 2017) Instructor: Craig Duckett
Values, Mission and Vision
Lecture 2: Selecting a topic and writing the dissertation proposal
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
(Spring 2016) Instructor: Craig Duckett Lecture 20: Thursday, June 2nd
Visual Studio Walk-Through PHASE 03 DUE THURSDAY
Employee Training and Orientation Process
PHASE 03 DUE (Winter 2016) Instructor: Craig Duckett
Information Systems in Organizations 2. 1
Microsoft Access Date.
Information Systems in Organizations 2. 1
(Winter 2017) Instructor: Craig Duckett Lecture 18: Tuesday, March 7th
(Winter 2017) Instructor: Craig Duckett
People First: True North Challenge
DATA MODELING AND DATABASE DESIGN
Presentation transcript:

(Winter 2017) Instructor: Craig Duckett Lecture 11: Thursday, February 9th Phase 2: Design Prep Workday

PHASE 2: DESIGN DUE Thursday, February 16th , uploaded to Team Web Site and ZIPPED and uploaded to StudentTracker by Phase 2 Project Manager Phase 3: Develop due Tuesday, March 2nd

The Team Project Five Phase Due Dates One (1) Team Project for a Client (3-to-4 Members on Team) 1000 points Total Phase 1: Discovery (200 Points) Phase 2: Design (200 Points) DUE THURSDAY, February 16th Phase 3: Develop (200 Points) DUE THURSDAY, March 2nd Phase 4: Distribute (200 Points) DUE THURSDAY, MARCH 9th Phase 5: Documentation (200 Points) DUE THURSDAY, MARCH 16th (Last Day of Class)

PHASE 02: Design Walk-Through PHASE 2: Project Design Build upon the analysis from the discovery phase to create a conceptual data model and present it to the class.

PHASE 02: Design Walk-Through A: Data Table Descriptions Use the list of subjects, along with implied subjects in the mission objectives, data processes, and characteristics to create a table list for your team database. Make certain the list is comprehensive, so that your database will meet all of your project objectives. Spend time refining the table names and descriptions so that they are clear, unambiguous, descriptive, and meaningful to yourself and the client. Table descriptions should include a subject definition and a description of why the subject is important to the mission.

PHASE 02: Design Walk-Through B. Field Descriptions and Primary Keys Review the characteristics you created from Phase 1 to create a set of fields associated with each table in the data model. Make certain your suggested fields meet the requirements of an Ideal Field (distinct, single-valued, simple, and unique.) Write a description for each field that accurately identifies the field and clearly states its purpose. Assign or create a primary key field for each table. The key field should allow you to uniquely identify each record in the table.

PHASE 02: Design Walk-Through C. Conceptual or Logical Data Model (Data Tables, Fields, Relationships) Base on your understanding of the different types of relationships between subjects identify all the relationships between the data tables. Identify the type of relationship and type of participation in the relationship that is necessary for achieving the mission outcomes. Diagram the data model using the notation for one-to-many, many-to-many relationships, and the type of participation.

PHASE 02: Design Walk-Through D. Present your Relational Data Model Prepare a presentation of your relational data model. Briefly discuss how the model will allow the client to accomplish each mission objective. Note any challenges in your design process, or outstanding design issues.

PHASE 02: Design Walk-Through E. Final Submissions for Design (Due Lecture 13 / Week 7) The list of table names and descriptions and field names and descriptions. The table structure listing all fields and primary key assignments in outline form. A relationship diagram that includes all data tables, their fields, and their relationships showing the relationship’s participation (optional or mandatory.) A presentation of your relational data model and how it meets your mission objectives.

Phase 2: Design Work Day