Instructor: Ken Baclawski
|College of Computer Science||Ken@Baclawski.com|
|Northeastern University||Fax: 617-373-5121|
|Boston, MA 02115|
Class meeting times and location: Thursdays 6:00-9:00PM in 220 Shillman
Office hours and location:Monday, Wednesday and Thursday 4:40-5:40PM in 342 WVH.
Fall office hours will begin on 4 September 2013 and end on 12 December 2013.
There will be no classes or office hours on the holidays 14 October, 11 November, 27 November and 28 November 2013.
Academic Honesty and Integrity[pdf]
Accommodations for Students with Disabilities
Database Design and Implementation by Edward Sciore
John Wiley, October 2008
The course grade will be based on six individual assignments (30%), a group project (20%), and a Final Exam (50%). The Final Exam will be an open-book/open-notes exam. Laptops, PDAs or other communication devices are not permitted at the Final Exam. The Final Exam will be given on 12 December 2013 during the regular class time but not the same room. The Final Exam will use assigned seating and will have a strict time limit.
The course grade will be reduced for the following:
There will be assigned seating during classes, with students in a team sitting together. The seating chart will be posted after the teams have been formed.
Exercises, quizzes and exams (some of which have solutions) from previous terms are available:
The technique for making an OData query in Java is illustrated in ODataRequest.java
The format for a software project report is in Software Project Report Format.
There is a weekly discussion session every Friday from 4pm to 5pm in 366 WVH. The discussion session will be led by a TA.
|9/5||Overview of database systems, the relational model and UML design||Chapters 1, 2, Sections 3.1 and 3.2, and Academic Honesty and Integrity Data Semantics|
|9/12||Database design and translating UML to the relational model||Sections 3.3 and 3.4|
|9/19||SQL queries||Section 4.3|
|9/26||Advanced SQL queries, updates and views||Sections 4.3 to 4.5|
|10/3||Integrity, security, triggers and stored procedures||Chapter 5|
|10/10||The database design process and basic relational operators||Sections 3.5, 3.6, 4.1 and 4.2, Relational Algebra Symbols|
|10/17||Index design principles and introduction to database programming||Section 6.3, Chapter 7 and Section 8.1|
|10/24||Advanced JDBC and object-relational mapping||Sections 8.2, 8.3, and Chapter 9|
|10/31||Web services and OData||Introduction to OData (slide presentation that will be available to the class)|
|11/7||XML and storage devices||Chapter 10, and Sections 12.1 to 12.4|
|11/14||Concurrency control and metadata management||Sections 14.4.1 to 14.4.8, and Chapter 16|
|11/21||Log, buffer and recovery management||Sections 13.1 to 13.4 and 14.1 to 14.3|
|12/5||Query processing and optimization||Sections 17.1 to 17.5 and 21.1 to 21.5|
|12/12||Final exam||All course material|
The Final Exam will mostly consist of problems similar to the individual assignments, but it will also cover course material that is not on any assignment, such as the last lecture.
There will be 6 assignments.
|1||Basic database design and translation to the relational model||Wednesday 18 September 2013 at 11:00pm.||Solution #1|
|2||SQL queries, updates and views||Wednesday 2 October2013 at 11:00pm.||Solution #2|
|3||DBMS API features, including integrity, security, triggers, stored procedures, the design process and relational operators||Saturday 19 October2013 at 11:00pm.||Solution #3|
|4||JDBC programming and object-relational mapping||Saturday 2 November 2013 at 11:00pm.||Solution #4|
|5||Web services, OData, XML and JSON||Saturday 16 November 2013 at 11:00pm.||Solution #5|
|6||DBMS components||Saturday 30 November 2013 at 11:00pm.||Solution #6|
All assignments must be uploaded to Blackboard. Be sure to check that your upload has been accepted by Blackboard and has been assigned a timestamp. You may upload your solution to an assignment more than once, but only the last one (and its timestamp) will be used for grading. A late submission will lose 1 point out of 100 for each hour that it is late, as determined by the timestamp.
Every student must be part of a group that submits a group project. A group may have up to 4 students. A group can consist of a single student.
The possibilities for projects will be discussed in class. Also see Ideas for Database Projects.
The following are the deadlines for group project submissions:
|Group formation||Members of the group and an optional group name||Wednesday 11 September 2013 at 11:00pm||0%|
|Project topic||Purpose and objectives. Use the Proposal Format.||Wednesday 25 September at 11:00pm||10%|
|Project requirements||Use cases and use case descriptions. See Size Criteria. An example and style files are available in usecase.zip||Saturday 12 October2013 at 11:00pm||20%|
|Project design||Varies with project, but will always include a UML class diagram and may include other diagrams. See Size Criteria. Submit a zip file with the images of your diagrams.||Saturday 26 October 2013 at 11:00pm||20%|
|Project implementation||Source code. See Size Criteria||Saturday 30 November 2013 at 11:00pm||30%|
|Project report||HTML document and slide presentation||Wednesday 11 December 2013 at 11:00pm||20%|
All group submissions must be uploaded to Blackboard. Be sure to check that your upload has been accepted by Blackboard and has been assigned a timestamp. All students must submit the first (group formation) assignment to confirm their membership in a group. The other submissions should only be done by one of the group members. You may upload your group submission more than once, but only the last one (and its timestamp) will be used for grading. Late submissions will lose 1 point out of 100 for each hour that it is late, as determined by the timestamp.
Individual extensions to the deadlines are given only for documented medical reasons, in which case a grade of I will be given for the course. Extensions are sometimes given to the class as a whole but only for compelling reasons that are discussed in class well before the deadline.