University of Dayton
School of Business Administration
Spring, 2015

MIS 385/MBA 664
Systems Implementation with Database Management Systems/Database Management Systems


Any substantive changes to this document will appear with Light Blue Highlight.

Something interesting to read about grades. 

Get your grades, and teams
Jump to course schedule

This page was last modified on Thursday April 23, 2015.



Dr. David Salisbury
Anderson Center, Room 103
937.229.5085 (office); 937.229.1030 (facsimile) (professor) (course)
T/R @ 430-545 PM in MH 102. 
M/W 10AM-12PM; T/TH 2-4PM (email usage is encouraged).  Hours are subject to change due to circumstances not currently foreseen.  Any such changes will be communicated to students via email.

Course Objectives


To provide you with a comprehensive understanding of the conceptual design of databases, the logical and physical design of databases, the database design and implementation process, various database models, and issues related to the centralized storage and control of data.  This will be accomplished through in-class discussion of database theory and application, and the use of hands-on assignments in data modeling (using the Entity-Relationship Model), database design and implementation, using (among others) Structured Query Language (SQL), MySQL Workbench, and Teradata SQL to implement functional, properly normalized, and well-designed databases.  Database implementations for client-server and web-based systems will also be discussed, as will data warehousing. 

As with all courses in the School of Business Administration at the University of Dayton, this course attempts to advance the University and School mission, to wit:

The School of Business Administration is a learning community committed in the Marianist tradition to educating the whole person and to connecting learning and scholarship with leadership and service in an innovative business curriculum designed to prepare students for successful careers in the contemporary business environment. 

To this end, the database management course is designed to bring theory about database design into the course, allow you to put this learning into practice building a prototype database system, and by doing so contribute to your understanding of how information systems are designed and built so you may eventually apply this knowledge in your future careers. 

 Course Materials

Hoffer, J. A., Ramesh, V., and Topi, H. (2013).  Modern Database Management, 11E.  Upper Saddle River, NJ:  Prentice-Hall.  ISBN-10: 0-13-266225-6; ISBN-13: 978-0-13-266225-3

ISBN-10: 0132662256 ē ISBN-13: 9780132662253

Other materials to be distributed as necessary, either electronically or in class. 

Course Procedures


The course deals primarily with database management systems concepts, and the design and implementation of such systems.  We will focus primarily on the Entity-Relationship Model and Structured Query Language. 

Practical Experience

An important aspect of the course will be the emphasis on understanding how database systems are developed and built through the development of data bases using various tools and techniques of the profession.  Some assignments will be performed individuals (to help each of you build your own skills), and others as teams (reflecting that much system development happens in teams). 

Course Assignments

A large proportion of each student's grade in this course will be assessed on the basis of the student's performance on various assignments that are expected to be completed through the semester. All assignments are to be completed by individuals, unless otherwise stated on the assignment. All assignments for this course are to be made via the World Wide Web, at the URL noted above. 

Timeliness of Assignment Submission

It is important to submit assignments on time. All assignments are due on the assigned date. Late assignments will not be accepted. You are all going to be in the real world someday, and this is how they do it there. This policy will be strictly enforced, except as mentioned under the excuses section. Please also know that if the first assignment is late, you put yourself severely behind for subsequent assignments.

Please be aware that no excuses except the approved ones noted in this document below will be accepted for assignments not being submitted on time, unless it's really good.

You should also be aware that you are responsible to see that your assignment has been submitted properly. I am not going to be chasing people down to make certain that they have submitted their work. In addition, due to the number of assignments in a class like this, you are also responsible to keep backups of all submitted work in case something gets lost in the shuffle, and you should keep all returned assignments until the end of the semester as proof they were submitted and marked.  Finally, marks which have been posted for one week are final.  Hence, you should keep track regularly of your course marks as posted on the database. 

Finally, to discourage procrastination, I will offer no assistance on class assignments after 5PM on the day before they are due. This policy will be strictly enforced.  If an assignment is due on Thursday, the last assistance I will render ends at 5PM on Wednesday. 

Class Attendance and Participation

Class time will be devoted to lectures, case discussion, demonstrations of database topics, and open discussion concerning database development issues. Contrary to popular belief, my job is not merely to impart information to you, but to help you learn. The mind is not a vessel to be filled, but a fire to be lighted. Your participation is extremely important to the learning process for yourself and the entire class. Consequently, class attendance and participation are strongly encouraged. For your information, I do keep a participation record, and it will influence your mark. Please also note that attendance is not the same as participation.

Another encouragement to attend is that you are responsible for anything that transpires in class. If you miss an assignment due date or other changes because you were not in class (or don't get it via email), it is your problem.

Classroom Decorum

You should be aware that your actions in the classroom environment should demonstrate intellectual engagement in the course content, and as well respect for your classmates and for your instructor. As such, talking audibly, passing notes, and other similar juvenile behavior simply have no place in a university classroom. If you find yourself unable to avoid chatting with the person next to you, you should consider sitting elsewhere in the class. Expect to be called out when such behavior is observed.

Other behaviors that are disruptive to others' learning involve various electronic devices. Cell phones, pagers and similar electronic communication devices should be turned off and stowed below the desk in a case or bag during all classes. While these devices are useful in their appropriate context, they create a disruption to the learning environment when they go off in class. Further, leaving the room to take a cell phone call is both inappropriate and rude, and also causes a disruption to the learning environment. As a consequence, failure to comply with this policy will result in appropriate disciplinary action, up to and including referral to university judiciaries.

Relevant to computer use (either in laptop required sections or in the lab), engaging in IM sessions, web-browsing, reading your email and other behavior of this type means that you are not paying attention to the material being discussed. Almost invariably this results in disruption to the learning environment as students who have not been paying attention find themselves behind and ask questions that have already been addressed. When you are in the classroom, you are expected to be engaged intellectually.

The instructor reserves the right to limit or prohibit use of any programmable devices (e.g. programmable calculators, laptop computers) and devices for communication and data storage (including but not limited to camera phones, cell phones, pagers, storage media or PDAs) at any time in the classroom. Refusal to comply with a request of this nature will result in sanctions being assessed as appropriate, up to and including referral to university judiciaries.

Please do not leave the class once you have chosen to attend -- it tends to be distracting for the rest of the class. If you must leave early, please sit near the door to make your departure unobtrusive, or do not attend at all. Please do not be late when you attend. Too many people coming after class starts creates a real disturbance. I reserve the right to take corrective action if it becomes a problem.

You should also be aware that being late for classes is no excuse to receive extra time on in-class assignments and quizzes. To arrive late and then demand extra time to complete a quiz disrupts the learning environment and also demonstrates lack of respect for your classmates.  If you are late for class on a day with a quiz or in-class assignment you will have less time to complete this, and if you arrive after the quiz is finished you will receive a zero. Finally, when assignments are due at the start of class, arriving late to class (i.e. significantly after the assignment has been taken up) is grounds for the assignment due that day to be considered a late submission.

I reserve the right to take corrective action if these issues create problems.

Please know that the intent of these policies is not to be unreasonable; from time to time a student may have reasonable need to leave the classroom prior to the end of class, or may have a legitimate reason that they are late. For example, he/she may be ill, may need a drink of water or may need to avail him/herself of the restroom facilities. Further, there are emergency situations in which constant availability via electronic communication may be necessary. In this case, simply notify the instructor of the situation and a reasonable accommodation can be made.

Reading Assignments

While there is not a large amount of material to be covered through this course, it is rather easy to fall behind. Please ensure that you stay current in your readings -- it is expected that you will have read in advance the material to be covered in class on a given day, and be able to discuss it.

Communication with the instructor

While I am around a lot, I am not in perpetually. Consequently, much interaction with me will be through e-mail (  You should also note that I intend to communicate with you via email as well; hence, it is important that you check your email often. 

Examination Procedures

The examinations will contain case-based questions, objective-style questions, and problem-solving questions. Exams will be based on the required text, on the in-class material associated with computer software, and on the other readings assigned by the instructor. Please note this carefully: There will be NO make-up examinations, save for university-approved reasons. If you must miss an examination, be prepared to document a university-approved reason. Job interviews, site visits and incarceration due to over-exuberant Halloween participation are examples of reasons that are NOT university-approved.


Quizzes will be administered at various times during the semester without prior notice. There will be SIX such quizzes this semester, and FIVE of them count (i.e. you can throw out your lowest score). The material will be taken from recently assigned reading. If you miss a quiz without an approved reason (see below and in the examination section), you receive a zero for that quiz. Period.

Grading Scale and Course Components

The grading scale and grading components are presented below. If you make any of the cut-offs, you will receive that mark. For example, if you earn 930 points, you will receive an "A" for the course, or if you receive 885 points, you will receive a "B+" for the course.

MIS 385 Grading Scale

Grade Assignment

Grade Components


>=900 <930
>=870 <900
>=830 <870
>=800 <830
>=770 <800
>=730 <770
>=700 <730
>=600 <700
<600 (failure)

Individual Homework
Team Project
Lowest Exam Score
Highest Exam Score

Total Points



MBA 664 Grading Scale

Grade Assignment

Grade Components


>=900 <930
>=870 <900
>=830 <870
>=800 <830
>=700 <800
<700 (failure)

Individual Homework
Team Database Project
Database Technology Presentation Lowest Exam Score
Highest Exam Score

Total Points



Since the marks in my classes over the long term tend to look like a normal curve, I tend not to force an artificial curve. On the odd chance that there is a curve it will be applied only on the overall grade in all sections I teach. Thus, no question of curving will be entertained until after the final. In addition, no extra credit assignments will be offered; if you are unable to perform well on what has already been assigned, I donít wish to burden you with extra work.  Finally, I encourage you that if you are in trouble, try to demonstrate an effort to improve and ask for help. Do not fail in silence.

Academic Dishonesty

I will vigorously pursue the prosecution of academic dishonesty. It is understood and that students often learn and work together; consequently you may be asking questions or getting help from others. Be very clear, however, that there is a reasonably obvious distinction between "help" and "cheating", which I will elaborate repeatedly in class throughout the semester. In instances where such misconduct is proven, I will invoke University of Dayton policy to the fullest extent. Please consult the most recent edition of the "Student Handbook" for further information on Student Code of Conduct and Academic Policies.

You should also note that the way individuals carry out their roles as a members of a project team could jeopardize the other members of the team with respect to academic misconduct. Specifically, if a team member fails to participate in the manner called for, and appends his/her name to the team's final product, each member of the team is deemed to have been academically dishonest. Thus, it is in each team member's interests to make certain that all team members participate appropriately, and to bring any occurrences of inadequate participation on the part of other members to my attention. Please be aware that the team defines adequate participation; it is reasonable to assume that on a given portion of the assignment some members will contribute more than others. However, this should balance out, and on the bulk of any given assignment, the level of participation should be equitable for all so that all team members receive a good educational experience.

Acceptable Excuses for Rescheduling Exams, Late Assignments, etc.

Note: It is conceivable there are other acceptable excuses that I've not anticipated, but you must receive permission from me personally in advance.

Accommodations for Students with Special Needs

The University of Dayton is committed to providing equal access to its educational opportunities for all its students, including those with special needs.  If you fit this category, inform your instructor, and also contact Disability Services at the Student Learning Support who, along with your instructor will devise the appropriate accommodations for your need.

Four Easy Ways to Raise Your Grade

Changes to the Syllabus

Since the main objective of this class is for you to learn relevant and useful stuff. I reserve the right to alter the syllabus as necessary to meet this goal. Any such changes will be announced, in class, and will be explained.


I took this position because I enjoy teaching. I genuinely care about you and your progress in the class. If you have a problem, complaint, comment, concern, etc., please schedule an appointment or drop in during open office hours.

Schedule--Subject to review and change.
Assignment links will be added soon.

Class Date

Anticipated Topics (slides forthcoming)

Text Chapters


Team Project



T 13 Course introduction, Introduction to database 1    

R 15

Introduction to database & database development

T 20

Basic data modeling (E-R diagramming)
2, Appendix A    
R 22 Basic data modeling, continued 2    
T 27 E-R Diagramming with MySQL Workbench MySQL Installation Guide
MySQL manual (alternate location)
Tutorials and videos
R 29 Modeling Wilco Construction 2, Wilco 1 & 2   Project teams selected
February T 3 Lots more basic E-R diagramming 2   Projects Distributed & Discussed
R 5 Enhanced ER Diagramming
3 #1 - 40/225  
T 10 More enhanced data modeling

R 12

Just when you think you can't stand it any more -  data modeling & enhanced data modeling,  Review & Catch-up 3 #2 - 40/225  
T 17 Digital Mixer @ Wright State University - 400-600 PM @ Wright State University.  Show up and network; especially if you are looking for a summer internship, but even if not it's a good idea to network.  UD provides a bus, see email for more information. 
R 19 Mid-Term Examination
M 23 UD Spring Career Fair - UD Arena - 1-5 PM.   Again, show up and network; especially if you are looking for a summer internship.
T 24 Logical database design using the relational model
4   Executive Summary (team evaluation form)
R 26 Logical database design using the relational model 4  



T 3 Logical database design & transformation using MySQL Workbench 4, MySQL manual #3 - 40/225

R 5

Mid-Term Break - No Class




T 10

Structured query language (SQL) - SQL tutorial, & another & a SQL reference    

R 12

SQL, continued - SQL lab (bring laptops) 6   Make sure you installed your MySQL instance correctly.
T 17 Advanced SQL, maybe a bit of Teradata (student password is "Analytics") 7   Conceptual ER Model (team evaluation form)
R 19 Teradata Finish up SQL - (bring laptops), information on Teradata 1, 2 (manuals)
  #4 - 35/225 SQL FILE  
T 24 Physical database design
Database application development
5, 8    
R 26 Team Project Work Day (as time permits)   #5 - 35/225  
T 31 Data warehousing 
(for what time we need)
9 Logical Design & Data Dictionary (team evaluation form)
April R 2  Easter Break - No Class      

T 7

Data quality & integration
R 9 Data & database administration 11    
T 14 Distributed databases 12 #6 - 35/225  
R 16 Team Project Work Day (as time permits)      
T 21 Review and catch-up      
R 23 System Walkthroughs     Final Working Database Prototype (team evaluation form)

Comprehensive final
Time taken from UD Final Examination Schedule.
Tuesday, April 28, 2015 @ 430 PM

ALL assignments are due at the START of class.