|Location||Shillman Hall 420|
|Office Hours||WVH 208, Tuesdays/Thursdays 5-5:45pm|
|Office Hours||WVH 462, Fridays 5-7pm (on 9/29: Shillman 415)|
|Office Hours||Nightingale 132, Wednesday 3-5pm|
|Office Hours||Nightingale 132, Mondays 6-8pm (starting 9/18)|
This course introduces relational database management systems as a class of software systems and prepares students to be sophisticated users of database management systems...
|Lectures||will focus on developing a conceptual understanding of database design & usage, as well as DBMS implementation.|
|Homework||will ask students to apply their conceptual knowledge via problems and code implementation.|
|Team Project||will allow students to collaboratively complete a database application from start to finish, including design & creation/optimization within a DBMS, as well as a programmatic user-interface.|
The final grade for this course will be weighted as follows...
Final grades will be assigned based on the following scale...
All assignments have a specific due date and time. Submissions will be accepted up to one day after the deadline with a 50% penalty. The assignment will be graded and returned as normal, but the grade will be recorded as half of what was earned. For example, an on-time submission might receive a grade of 90 points. The same assignment submitted after the deadline would receive 45 points (90 x 0.5).
Students who miss scheduled exams will not, as a matter of course, be able to make up those exams. If there is a legitimate reason why a student will not be able to complete an assignment on time or not be present for an exam, then they should contact the instructor beforehand. Under extreme circumstances, as decided on a case-by-case basis by the instructor, students may be allowed to make up assignments or exams without first informing the instructor.
Submissions will be made via Blackboard as a single ZIP file. Any written work (e.g. math problems, reports) is to be included as a PDF (preferably in LaTeX). Code is expected to be professional and properly documented; any required data files/libraries must be included.
This class has very strict standards for borrowing code: if you borrow anything for use in your homework/project, you must have a citation. A good guideline is that if you take more than three lines of code from some source, you must include the information on where it came from. A URL or a notation (e.g., "MATLAB help files") is fine. If it is an entire function, note it at the beginning of the code segment and include any original credit information. Provide a qualitative description of what you used, and what you changed/contributed. If you have a question about what is considered a violation of this policy, ASK!
The university's academic integrity policy discusses actions regarded as violations and consequences for students: http://www.northeastern.edu/osccr/academic-integrity
Group projects are sometimes looked upon as being "unfair." To combat contribution inequity, each team member's perception of the quantity of work that s/he performed and that of each team member will be analyzed against the perceptions of the team member(s). Through this process, hopefully equity will be achieved.
Each team member will submit a report rating the relative contributions of each team member (including her/himself) using a single number, as well as optional commentary. The aggregate rating for each student will determine the grade that individual receives, relative to the group grade. In order for this process to work effectively there is the need for each group member to be honest and objective; these ratings and comments will be kept confidential.
Note: This schedule is subject to change and will be adjusted as needed throughout the semester.
|Day||Topics||Reading||Due (default=M@5pm, late=T@5PM)|
|No class first week|
|Sep 12||Course/Syllabus, DBMS/Architecture||1, 2|
Relational Data Model, Relational Algebra/SQL (SELECT)
||5, 6, 8, Codd|
|Sep 26||SQL cont'd (INSERT, UPDATE, DELETE; DDL+), Programming||6, 7, 8, 10, Boyce||HW::SQL.1 (SELECT, RA)|
|Oct 3||Exam Review, Web Development Intro||11||HW::SQL.2 (SELECT, JDBC)|
Exam 1 (Test, Debrief)
|Oct 17||Conceptual Modeling/ER Diagrams||3, 4|
|Oct 24||Logical Design/Mapping ERD, Normalization||9, 14||HW::ERD|
|Oct 31||Exam Review, NoSQL Overview||24, Strauch||HW::Logical (Mapping, Normalization)|
|Nov 7||Exam 2 (Test, Debrief)|
Indexing, Physical Design
||17, 18||PRJ::Milestone.1 (ERD, Mapping)|
||22, 30||PRJ::Milestone.2 (Data, Queries)|
|Dec 12||Exam 3 (Test, Debrief)||PRJ::Final|
Students are expected to read the materials in preparation of each lecture.
To create and preserve a classroom atmosphere that optimizes teaching and learning, all participants share a responsibility in creating a civil and non-disruptive forum for the discussion of ideas. Students are expected to conduct themselves at all times in a manner that does not disrupt teaching or learning. Your comments to others should be constructive and free from harassing statements. You are encouraged to disagree with other students and the instructor, but such disagreements need to respectful and be based upon facts and documentation (rather than prejudices and personalities). The instructor reserves the right to interrupt conversations that deviate from these expectations. Repeated unprofessional or disrespectful conduct may result in a lower grade or more severe consequences. Part of the learning process in this course is respectful engagement of ideas with others.
Title IX of the Education Amendments of 1972 protects individuals from sex or gender-based discrimination, including discrimination based on gender-identity, in educational programs and activities that receive federal financial assistance.
Northeastern’s Title IX Policy prohibits Prohibited Offenses, which are defined as sexual harassment, sexual assault, relationship or domestic violence, and stalking. The Title IX Policy applies to the entire community, including male, female, transgender students, faculty and staff.
If you or someone you know has been a survivor of a Prohibited Offense, confidential support and guidance can be found through University Health and Counseling Services staff (http://www.northeastern.edu/uhcs/) and the Center for Spiritual Dialogue and Service clergy members (http://www.northeastern.edu/spirituallife/). By law, those employees are not required to report allegations of sex or gender-based discrimination to the University.
Alleged violations can be reported non-confidentially to the Title IX Coordinator within The Office for Gender Equity and Compliance at: firstname.lastname@example.org and/or through NUPD (Emergency 617.373.3333; Non-Emergency 617.373.2121). Reporting Prohibited Offenses to NUPD does NOT commit the victim/affected party to future legal action.
Faculty members are considered "responsible employees" at Northeastern University, meaning they are required to report all allegations of sex or gender-based discrimination to the Title IX Coordinator.
In case of an emergency, please call 911.
Please visit http://www.northeastern.edu/titleix for a complete list of reporting options and resources both on- and off-campus.
Students who have disabilities who wish to receive academic services and/or accommodations should visit the Disability Resource Center at 20 Dodge Hall or call (617) 373-2675. If you have already done so, please provide your letter from the DRC to me early in the semester so that I can arrange those accommodations.