1. CIS 3650: DATABASE MANAGEMENT SYSTEMS
Instructor: Dr. Qingxiong Ma Phone: 660-543-8637
Class Time: T, R WDE 2810 Email: email@example.com
9:30:00 AM – 10:45 AM
Office Hours: Monday, Wednesday 10:00am -12:00pm Thursday 11:00am - 12:00pm,
Dockery 300B. Other time by appointment
Course Website: Blackboard
This course introduces relational database design, implementation, and management. Special
emphasis is placed on the applying the knowledge of structured query language (SQL), data
normalization, and entity-relationship (E-R) modeling to solve real business problems. Primary
database implementation will be done using SQL Server 2005 (MS Access or MySQL). An
introduction to Web-based database may also be provided.
1. **Gaining factual knowledge (trends, terminology, and methods).
2. *Learning fundamental principles, concepts, and guidelines of relational database.
3. *Learning to apply course material (to improve understanding and solve business
4. **Developing specific skills and competencies needed by CIS professionals related to
database design and management.
Textbook: David M. Kroenke, Database Processing—Fundamentals, Design, and
Implementation, 10th Edition, Prentice Hall, 2006.
Software: DeZign, MS SQL Server, MS Access, Visual Studio 2005
Prerequisite: CIS 2610
Additional Materials: 3 Scantrons (Form 882-ES) and portal storage medium
There are THREE major learning components in this course,
b) Business Knowledge
c) People Skills
• Database Design Skills- especially entity relationship modeling and data normalization
• Software Application Skills—Using E-R modeling tools and DBMS
2. o For modeling and creating database Schema, DeZign will be used.
o For database implementation and administration, MS SQL server and Visual Studio
will be used.
• Think as a solver of business problems
o understand business problem and translate it into technically solvable objects
o Identify the potential entities and attributes. Not all information are obvious, this
identification process is iterative. It will be back and forth several times. The
validation from business customers on the entities and attributes is necessary.
• Project management
o Project planning, completion and testing
• Communicate with the business as an IT consultant
o System requirement collection, validation, and testing
o Class discussion and team work.
o Business interview and project presentation
o Discussion and feedback from the instructor.
At the end of semester, students are expected to:
1. Understand the basic professional requirements – Assignment1
2. Understand basic database concepts – Assignment2
3. Be able to use Structured Query Language (SQL) to define, maintain and query
relational databases – Assignment3, 7
4. Understand functional dependency and apply data normalization process –
5. Be able to create entity-relationship diagrams and know the related terminologies
- entities (Strong Entities, Weak Entities, and Subtype Entities),
- keys (candidate key, primary key, surrogate key, composite key, foreign key)
-relationships (one-to-one, one-to-many, and many-to-many relationships),
-attributes (cardinalities and multi-valued attributes;
6. Be able to transform a E-R model to a relational database Model – Assignment6
7. Be able to apply the knowledge and create a data-oriented web application –
ROLE OF CIS 3650 IN CIS MAJOR
Students successfully completing the CIS major will be able to:
1. Demonstrate knowledge of professional and ethical expectations in the work place.
3. 2. Use productivity software (word processing, spreadsheet, and database) effectively and
manage hardware and software resources by applying knowledge of operating systems and
3. Develop application software using skills in appropriate business programming languages
(e.g. COBOL, Visual Basic, Java).
4. Develop and maintain databases using theoretical and applied knowledge of relational
database management systems (e.g. Oracle, SQL Server, DB2).
5. Develop and maintain telecommunications networks using theoretical and applied knowledge
of telecommunications (e.g. Novell, Windows/NT).
6. Analyze business problems and develop solutions by applying critical thinking skills within
the systems development process (e.g. The Systems Development Life Cycle [SDLC] and
7. Be a team player by applying group process skills: participate fully in group discussion and
activities, lead/follow when appropriate, provide support and collaboration when needed.
8. Access information resources and communicate effectively using a variety of methods: oral,
written, and electronic.
9. Design and construct client/server applications by using appropriate tools and architectures
and develop effective graphical user interfaces (GUIs).
Final course grades will be determined based on your final weighted score using the following
fixed percentage cutoffs. Please be noted that the final course grade will not be rounded up.
For example, in order to receive an A, your final course score must be 90.00 or above.
Α = 90.00% οr above B = 80.00% to 89.99% C = 70.00 to 79.99%
D = 60.00% to 69.99% F = less than 60.00%
ACTIVITY Possible Points
Exam 1: 100
Exam 2: 100
Exam 3: 100
Pop Quizzes (5) 50
Individual Assignments 150
A1: Job requirements 10 10
A2: Database Concepts (MS Access) 10
A3: SQL—Query 30
A4: Normalization 20
A5: E-R diagram Modeling 15
A6: Database Design 15
A7: SQL—DDL 30
A8: Data-oriented web application 20
Group Project 100
Participation & Attendance 50
Total possible points 650
4. The detailed requirements of each assignment will be posted on blackboard a week ahead. All
assignments should be submitted in both electronic copy in blackboard and hard copy before
class. The detailed requirements for the Group project will be given separately.
 Class Participation and Attendance: You are expected to read the assigned reading
material, work diligently toward the completion of assignments, attend classes regularly
and participate in all discussions, presentations, and activities constructively. In addition,
you are expected to show respect, collegiality, and good citizenship toward others in the
class. It is your responsibility to inform the instructor ahead if you are unable to show up
or will be late for the class. Each absence without acceptable excuse is worth 10 points. If
you have more than 5 absences, you will have an incomplete as the final grade. Every two
times of tardiness will be considered as one absence.
 Missed Tests: No make-up examinations will be given except for university-approved
emergencies. If you anticipate problems regarding scheduled test or class activity, please
see me in advance to make alternative arrangements.
 Late submission Meeting deadlines for class assignments is very important. Late
assignments will be penalized. There will be a penalty of 20% of the assignment's maximal
grade (i.e. 20 pts on a 100-point base) per calendar day for late submission, and no late
submission will be graded after the solution of the assignment is discussed in the class.
Excuses such as the system was down, the printer was running out of paper or ink
cartridges, or there was a virus on your diskette, you were not being able to get onto a
computer or printer in the labs, or having your computer's hard drive crash at the last
minute are not acceptable.
 Bonus Assignments: Instructor may provide students with a number of bonus
assignments throughout the session. Students should determine by themselves whether to
submit a bonus assignment or not. The maximal total credit that a student can earn from
his or her bonus assignments is 1% of course grade. This extra credit will be added to the
student’ session score. According to the instructor’s experience, the extra credit is
normally a critical help to students whose session scores are marginal.
 Team Work: Project and some of homework are to be done in teams. The teams may
consist of no more than three members. All team members are expected to contribute
equally and fairly to the team activities. If you encounter difficulties in the smooth
functioning of the team, bring it to instructor’s attention early. Peer evaluation will be
conducted to detect any significantly unbalanced contribution amongst team members.
 Announcements: Announcements will be made in class about changes in schedules,
computer lab meetings, assignments, exams, readings, policies and other class activities. It
is entirely your responsibility to attend classes and keep abreast of the announcements and
changes. Important announcements may also be posted on the course web site.
 Academic Misconduct: All assignments and tests should be the product of individual
effort. Feel free to discuss problems, but make sure that what you turn in is the product of
your own. No form of reference material may be used during an examination. Students are
expected to understand and follow the Harmon College of Business Administration Code of
Conduct (http://www.ucmo.edu/hcba/code). Any form of copying, either on computer
5. assignments or tests, will be considered academic misconduct and will be dealt with
according to the Honesty and/or Computer Network procedures on page 129-151 of the
 Disabilities: Any student who has a disability that may prevent him or her from fully
demonstrating his or her abilities should contact me personally as soon as possible to
discuss accommodations necessary to ensure full participation and facilitate the student's
educational opportunity. Students with documented disabilities who are seeking academic
accommodations should contact the Office of Accessibility Services, Union 220, (V)
 Special Note: Please turn off your cell phone when you are in the classroom.
6. Tentative Schedule: (as of 1-13-2009)
Week Topics Assignments
1 Chapter 1: Why use a database A1
Chapter 1: What is a database system
Chapter 2: Structured Query Language (SQL--DML)
Chapter 2: Structured Query Language (SQL--DML) A2
Chapter 2: SQL Practice (Single table)
Chapter 2: SQL Practice (Multiple table)
Chapter 3: Relational Model
Chapter 3: Functional Dependencies and Normal Forms (BCNF, 4th NF)
Chapter 3: Eliminating Anomalies From Functional Dependency (Example A 3
Chapter 3: Eliminating Anomalies From Multivalued Dependency
Chapter 4: Using Normalization
Chapter 5: Entity-Relationship Data Model (concepts)
Chapter 5: Patterns in forms, Reports and E-R models
Chapter 5: Data modeling process and practice using DeZign
Group project (preliminary presentation) A4
9 Chapter 6: Transforming Data Models into Database Design (process)
10 SPRING BREAK
Chapter 6: Create Relationships A5
Chapter 6: Design for Minimum cardinality
Exam 2 A6
Chapter 7: SQL for database construction (SQL--DDL)
13 Chapter 7: Application processing and ADO.net
14 Data-oriented Web application design A7
15 Chapter 11: Database Administration with SQL Server 2005
16 Final Group Project presentation
17 Final Exam
Note: The above schedule is subject to change if it is deemed appropriate at the instructor’s discretion.