Instructor Contact Information

  • Instructor: Amelia Garripoli
  • Office Hours: online Mon&Tue 12:30-1:30, or by appointment
  • Website: argoc.github.io/faculty
  • Skype: Prof. Garripoli
  • Email: amelia.garripoli@wwu.edu
  • Phone: 360-774-0740

Course Detail

  • Catalog description:This course covers the design, implementation, and use of databases. Students learn to analyze and model data and data usage to create an efficient, normalized database, to implement a database in a relational database management system (RDBMS), and to manipulate the data and data format using SQL. Students study other forms of databases, and the security implications of different databases and database access techniques.
  • Credits: 3
  • Class dates: Sep 26 - Dec 7, 2018. School holidays: Nov 12(Mon), Nov 21-23(Wed-Fri).
  • Class format: This class is on ground. Activities may be included in class; make arrangements if you have to miss a class.
  • Class meets: Thursday, 3-5:50, in OCP.
  • Final: Thursday Dec. 13, 3-6pm
  • Text Required: Murach's MySQL, 2nd edition, Joel Murach, ISBN 978-1-890774-82-0. [MM2e]
    Additional material will be supplied in the Canvas course shell.
  • Learning Outcomes:

    By the end of this class, students will demonstrate:

    • Create data models based on data elements, their relations, and how the data is used.
    • Create and normalize database layouts to support data models.
    • Use data definition language, data manipulation language, and other SQL statements to create and use a database.
    • Compare and contrast different database models including relational, network, hierarchical, and key-pair models.
    • Identify security implications of database management systems, database designs, and database implementations.

Schedule

Any changes to the schedule will be announced in class. Students will be held responsible for tracking all changes.

We move quickly through the material. Be prepared to work on the course daily, read the assigned text prior to class, and do not delay labs until the due date.

Visit the course Web site often for current assignments information, due dates, and messages.
The Grades section will show you the work you have submitted and the feedback for it.

See the Canvas Course or your Canvas Calendar for the current schedule of assignments.

All work is to be submitted on Canvas using submissions in Assignments, posts and responses in Discussions, and by submitting Quizzes; these can be found in their assigned module using the "Module" link on the Canvas course navigation to access the modules for this course.

Points on indivudal assignments may not reflect contribution to your final grade; see further information after the table.

Week

Topic

MM2e

Lab

Due

1 Sep 27

Syllabus, Environment, Database Overview

1, 2

 

Module 1 Lab

Oct 3

2 Oct 4

Basic SQL:
SELECT, INSERT, UPDATE, & DELETE

3, 5

Module 2 Lab

Oct 10

3 Oct 11

Database Design

10, 11

Module 3 Lab

Oct 17

4 Oct 18

More on Queries:
Joins, Types, and Functions

4, 8, 9

Module 4 Lab

Oct 24

5 Oct 25

Data Analysis, Views

6, 12

Module 5 Lab

Oct 28

6 Nov 1

Transactions

13, 14

Module 6 Lab

Nov 7

7 Nov 8

Performance & Recovery

17, 19

Module 7 Lab

Nov 14

8 Nov 15

Security

15, 16, 18

Module 8 Lab

Nov 28

9 Nov (22)

(Thanksgiving)

 

 

 

10 Nov 29

NoSQL DataModels

TBD

 

Dec 5

11 Dec 6

Final Project

 

Final Project

Dec 6


See the Canvas Course or your Canvas Calendar for the current schedule of assignments.

Each class meeting is about 3 hours. We will use time across our class as best suits learning modes. Attendance is expected. You have the opportunity to bring questions from the reading and labs to class prior to homework due dates. Participation in class discussions and activities is expected.

See the rubrics for Labs in the course shell.

If you are not able to attend for the Final Project, let me know a few weeks prior to the date so that an alternative can be arranged.

Assessment

Assessment for the course consists of labs, a final project, and class participation. The contribution of each assessment item to the final grade is as shown below:

Labs70%
Final Project20%
Participation10%

Labs must be submitted on-time. If there is a need for a special accommodation for the late submission of a lab, the student may make a request before the due date to the instructor. The instructor may, with discretion, choose to allow a late submission. Late submission will have 10% deducted per day or partial day that it is late. The maximum extension permitted is 2 days. Note no extension is provided after the due date without extremely extenuating circumstances.

Participation: All students are expected to have completed assigned readings prior to coming to class, and to participate fully in activities and discussions in the classroom.

Exams will not be rescheduled, no make-ups are provided. Failure to do the final project, in accordance with University policy, will result in an F grade for the course.

Grades will be assigned on the total of the assessment items according to the following:

Letter Percent Qualitative Definition
A 90% Superior course outcomes mastery
B 80% Exceeds acceptable course outcome mastery
C 70% Acceptable course outcomes mastery
D 60% Minimum course outcomes mastery
F < 60% Failure to master course outcomes

The use of '+' or '-' annotations on a course grade is at the discretion of the instructor.

Points on work submitted on-time are posted as soon as possible, usually within 7 days of the due date; a bit more during exams or if our schedules gets impacted. My goal is to give reasonable feedback to as many students as possible in the shortest time possible. If I have a larger than normal grading load, I will notify you of any delays in grading. See Policies for information on getting assistance, submitting work, academic honesty and more.

Monitor your course progress and see what you have submitted by clicking on "Grades" on the course navigation on the course website.

Technical Expectations

We will be introducing SQL in this class. You will be using a virtual machine with MySQL Community installed on it (by you) to create, debug, and run SQL scripts. We use Canvas for providing course information beyond the classroom, submitting work, and communicating on-line.

You will need to have regular Internet access for completing and submitting coursework. Please develop a plan "B" in case you have issues with your normal Internet access and related software that might affect your ability to participate in this class. Computer or software issues will not change your due date.

Policies

  1. Ask for help:

    First, if you need help, get help early and often - if you wait it can become too late. Start assignments early and be proactive. It takes time to consider the implications of programming, an early start gives you time to consider alternative solutions and get help if you need it.

    You can expect a response from me to your Canvas Inbox message within one school day; do not expect a reply on weekends, breaks, or holidays. If you do not get a response in that timeframe, resend your message and check the to: address to ensure it is going to the appropriate person.

    My role is to teach, not to provide solutions -- that means I may ask you questions, give you additional resources, or review class material. Do not show your work to your classmates or in online forums. Other individuals are not allowed to directly provide any part of a solution to a home work assignment. The work must be the student's own. Similarity detection may be done on any submitted work.

  2. Effort: Regular attendance and success in this course have a strong correlation. Regular attendance for our class means:
    • You are logging in to the Canvas classroom at least three times per week.
    • You are completing the reading prior to attending class.
    • You are attending, or when absent, getting notes from your peers as quickly as possible.
    • You have a plan B in place in case your internet access is interrupted, and use it.
    • You make regular progress on the reading and homework each week.
    • You seek assistance promptly from the instructor when you have questions on the reading, the recordings, or any assignments.

    New concepts tend to build on previous concepts rather than stand on their own. If you have to delay your progress in this course, I suggest you catch up quickly and network with other students to get on track as soon as possible (days, not weeks). Utilize office hours (or make appointments) to ask for assistance.

    Students are responsible for ensuring that they keep up with course material and that they keep informed on class information, as presented in class or advised via the course web site.

    Students are expected to have the Course Textbook and satisfy the Technical Expectations on or before the start of class. Any requested reading or activity should be completed before the first class day of the module, so that the student can better participate in discussions and use lab time effectively. Not having a text and not being prepared will not be an acceptable excuse for not being able to participate in class or to turn in assignments on time.

    By taking this course, you are stating that you will be making appropriate time in your schedule to ensure success and have access to the resources required for this class. Expect to spend about 3 hours per week for each class credit to ensure success. For a 5 credit class this is 15 hours of class work per week. You need to invest regular, consistent time to succeed in this course.

    Attendance at class is required. Recordings of class and make-up work for missed attendance will not be provided.

  3. Late Work: If you have a one time event that is a serious illness or accident, or emergency service or active duty for you, your parent, your spouse, or your child, the late policy may be applied. You must make your request at least one full day before the assignment is due for a late policy waiver or have verifiable proof of your inability to make the request by that time. Vacations, colds, or other discretionary activities will not be accepted. On-going or pre-existing situations can not be used for reasons for late work as they were known constraints at the start of the course.

    A late waiver is a one-time, one-assignment event, and any excused late work will not transfer to additional assignments. You will need to catch up with the course schedule and continue on time. If for some reason you cannot catch up, you can contact the Registrar to withdraw; it is not sufficient to tell me that you are withdrawing.

    Accepted late work will be graded at the discretion of the instructor both for points as well as to when the assignment will be graded.

  4. Academic honesty: Academic dishonesty is defined in the University Catalog as misrepresentation by deception or by other fraudulent means whih ompromises an isntructor's ability to fairly evaluate a studfent's work or achievement. It is the instructor's responsibility to confront a student and to take appropriate action if academic dishonesty, in the instructor's judgment, has occurred. Please refer to the University Catalog for further infromation.

    Any student who violates the University policy on academic dishonesty could receive an F for the course and further disciplinary action from the University.

    You are to complete programming assignments individually. You may discuss the assignment in general terms with other students including a discussion of how to approach the problem, but the code you write must be your own. The intent is to allow you to get some help when you are stuck, but this help should be limited and should never involve details of how to code a solution. You must abide by the following:

    • You may not work as a partner with another student on an assignment.
    • You may not show another student your solution to an assignment.
    • You may not have another person (current student, former student, tutor, friend, anyone) "walk you through" how to solve an assignment.
    • You may not post your homework solution code online to ask others for help or in a public place. This includes public message boards, forums, file sharing sites and services, public web sites, or any other online system.
    • You are not to examine online solutions that you might find on the web.

    Under our policy, a student who gives inappropriate help is equally guilty as one who receives it. Instead of providing such help, refer other students to class resources (lecture examples, the textbook, or the instructor). You must not share your solution and ideas with others. You must also ensure that your work is not copied by others by not leaving it in public places, emailing it to others, posting it on the web, etc. The WWU office has a shred box -- I recommend you use that if you have printed out code.

    We enforce this policy by running similarity-detecting software over submitted student programs, including programs from past quarters and other sources.

  5. Student Code of Conduct: Students must abide by all applicable university and state laws concerning student conduct, including WAC 516-21 and any other University regulations.

Equal Opportunity

I am committed to establishing and maintaining a classroom climate that is inclusive and respectful for all students. Learning includes being able to voie a variety of perspectives, and classroom discussion is encouraged. While students' expressed ideas may vary and/or be opposed to one another, it is important for all of us to listen and engage respectfully with each other.

I, and Western, are committed to an environment free of discrimination and harassment. Federal and State laws, as well as University policies, protect students, faculty and staff against discrimination based on the following legally protected characteristics: Race, Color, Creed, Religion, National Origin, Gender (including pregnancy and parenting status), Age, Disability, Marital Status, Sexual Orientation, Gender Identity and Expression, Genetic Information, and Veteran Status. See Equal Opportunity and Western's Policies on Providing Equal Opportunity and Nondiscrimination and Preventing Sexual Harassment.

Student Services

Western encourages students to seek assistance and support at the onset of an illness, difficulty, or crisis.

  • In the case of a medical concern or question, please contact the Health Center, 360-650-3400
  • In the case of an emotional or psychological concern or question, please contact the Counseling Center: 360-650-3400
  • In the case of a health and safety concern, please contact the OC Campus Police: 360-475-7800
  • In the case of a family or personal crisis or emergency, please contact the Dean of Students: 360-650-3450
  • To seek confidential support related to sexual violence, please contact CASAS (360-650-3700). To report sexual violence, please contact OC Campus Police, Poulsbo Police, and/or the Title IX Coordinator (360-650-3307). Faculty are responsible employees who are required to report sex discrimination, including sexual violence, to the Title IX Coordinator.

Accommodations

Reasonable accommodation for persons with documented disabilities should be established within the first week of class and arranged through Disability Resources for Students: telephone 360-650-3083; email rs@wwu.edu; and on the web at Disability Resources.

Success

I want you to succeed in your pursuit of cyber security. This class gives you an opportunity to develop database skills to help you in your endeavors, both to analyze data you may collect and to determine the impact of cyber attacks on databases. I am here to support your efforts. Please contact me and use my office hours if you need help with this course. I also welcome your insights and feedback.

Welcome to CISS 340, I look forward to sharing SQL and database security with you. ~ Amelia.

Note: Syllabus content, course due dates and assignments may change at any time. Canvas will notify you of any changes during our course.