CIS 336 DeVry All Week Course Project Latest

Downloading is very simple, you can download this Course here:

http://wiseamerican.us/product/cis-336-devry-week-course-project-latest/

Or

Contact us at:

SUPPORT@WISEAMERICAN.US

CIS 336 DeVry All Week Course Project Latest

CIS336

CIS 336 DeVry All Week Course Project Latest

This project is designed to touch all aspects of the fundamental concepts of database design and logical data modeling covered during the class. Each student will be responsible for designing, developing, and demonstrating the functionality of a database created based on a set of business specifications that you create. At the end of the session, each student will submit a report that includes the logical and physical design of the database and demonstrates the database’s ability to deliver meaningful reports. All aspects of the project will be covered during the week or weeks prior to a deliverable, and each task deliverable in the project will be supported through the exercises and labs done in the course.

Guidelines

You will create a proposal for a commerce business of your choosing. This can be an actual or fictional business that sells products and/or services. You will determine the business rules and report requirements. Entities that must be included in your model are the following.

Customer

Product (or Service)

Order

Project Deliverables

This task is broken down into four deliverables.

  1. Task 0 (due at the end of Week 1)
  2. Task 1 (due at the end of Week 3)
  3. Task 2 (due at the end of Week 5)
  4. Task 3 (due at the end of Week 7)

Remember that this is a work in progress and in all likelihood, you will have to make numerous changes to your tables and schema as you go along. These changes are to be expected and are a normal part of the database design and implementation process.

Please refer to the sections below for details regarding deliverables for each task.

Task 0 (due at the end of Week 1)

The first task is to create your business narrative. Some of the questions that you should address include (but are not limited to) the following.

  • What is the name of your business?
  • Who will be the users of the system (managers, employees, customers)?
  • What product(s) and or service(s) does it sell? Be specific.
  • Who are the customers? What is the customer base?
  • What sales and distribution channels are used?
  • How are payments made?
  • Are products delivered or shipped to customers in some way?
  • Are sales reps involved? Are they paid on commission?
  • What type of reports are needed by the business?

Please include as much detail as possible in order to provide a foundation for Task 1. Submit your proposal as a Word document. Note that this proposal may be revised in the coming weeks as your understanding of the database modeling process grows.

Task 1 (due at the end of Week 3)

Develop a detailed logical model of your database based on your business scenario submitted for Task 0. Your data model will include an entity-relationship diagram (ERD) developed with Microsoft Visio or MySQL and a data dictionary (DD) developed with Microsoft Excel.

Note that your deliverables each week include any revisions to the previous task.

Submit your Task 1 deliverable as a zip file including the following.

  • Task 0 proposal (with any revisions or updates)
  • Your ERD copied to a Word document that fits on a single 8 x 10 page
  • Your DD (Excel file)

Task 2 (due at the end of Week 5)

First, make sure to make any necessary revisions to your logical model based on Task 1 feedback. Using MySQL, write the statements to develop a physical model of your database by creating the tables and constraints based on your Task 1 logical model. Be sure to use your ERD and data dictionary and create all constraints appropriately.

Once your tables are created, you will populate them with data using MySQL statements to insert records into the database. You should insert a minimum of five records into each table and more where necessary to ensure that the data in the database is sufficient to allow for each of your reports to be tested.

The result will be a script file that includes statements to

  • DROP all tables;
  • CREATE all tables with constraints;
  • INSERT data into all tables; and
  • SELECT data from all tables to show the data in each table.

Name this file yourname_task2.txt.

Also create a Word document that shows the structure of each table and the data in each of your tables (copy and paste from MySQL). Name this file yourname_tables.docx.

Note that your deliverables each week include any revisions to a previous task.

Submit your Task 2 deliverable as a zip file including the following.

  • Task 0 proposal (with any revisions)
  • Your Task 1 ERD (with any revisions)
  • Your Task 1 DD (with any revisions)
  • Your Task 2 script file to create and populate tables (yourname_task2.txt)
  • A Word document showing all tables and data (yourname_tables.docx)

Task 3 (due at the end of Week 7)

Your final task is to use your tables for an update and for reports. There are two requirements.

  1. You will demonstrate an update that includes two tables and uses a subquery. Make sure to prove that your update executed correctly by showing data in the tables before and after the update.
  2. You will also develop at least four meaningful reports. One must include a join, one must use a subquery, and one must use an aggregate function. You need to describe the business requirement of the update and each report. Note that numeric PK values are not often meaningful to a person looking at the report.

You will create a script file that has each of the queries called yourname_task3.txt. You will also document the results of this task in a Word document called yourname_reports.docx to show the result of each query. For the update and each report,

  • describe the update and report requirement;
  • show the query; and
  • show the result of the query.

Include a final section for Conclusions and Lessons Learned regarding the project.

Note that your deliverables each week include any revisions to a previous task.

Submit your Task 3 deliverable as a zip file including the following.

  • Task 0 proposal (with any revisions)
  • Your Task 1 ERD (with any revisions)
  • Your Task 1 DD (with any revisions)
  • Your Task 2 script file to create and populate tables (with any revisions)
  • A Word document showing all tables and data (with any revisions)
  • Your Task 3 script file with update and reports (yourname_task3.txt)
  • A Word file with results of Task 3 and lessons learned (yourname_reports.docx)