CSE 444 Syllabus
- Course Goals
- Databases are at the heart of modern commercial
application development. Their use extends beyond this to many
applications and environments where large amounts of data must be
stored for efficient update and retrieval. The purpose of this course
is to provide an introduction to the design and use of database
systems, as well as an appreciation of the key issues in building such
- We begin by covering the relational model and the SQL
language. We then study methods for database design, covering the
entity relationship model. We then
inspect the architecture of a database system, and discuss efficient
storage of data, execution of queries and query optimization. Finally,
we touch on some advanced topics in database systems.
- For the detailed list of topics and schedule, please see the course calendar.
- Course Format
- The class meets three times a week for lectures; we won't
meet in the computer lab. We will follow parts of the textbook (see
below). The lectures are designed to be clear and self-contained, and
to cover all the material used in class. Still, you are strongly
encouraged to read from the textbook, both in order to get a better
understanding of the material covered and to learn about related
topics, which are not covered in class.
- There will be three homework
assignments (some of which will involve light programming), and there
will be four mini-projects. You can usually find copies of the
slides used in the lecture on the web site, on the day of the
- In addition to the lecture there will be two sections taught by the TAs. The sections will give you
an opportunity to ask questions about homework assignments and projects.
- MWF 12:30-1:20 pm, EEB 045
- Midterm: Please see course calendar for location and time information
- Final: Please see course calendar for location and time information
Web sources: there will be some reading assignments from
The library has the following that you might find useful if you
require another explanation of a topic.
- Database management systems by Raghu
and Johannes Gehrke. (often used alternative textbook)
- Foundations of database systems by Abiteboul,
and Vianu. (focus on theory)
- Fundamentals of database systems by Elsmasri and
- Programming and
- Some programming will be
necessary in this course. One can
only start to appreciate database systems by actually trying to use
one. Databases only hold the data, the application logic needs
to be written in some general purpose language.
- Late Policy
- You are allowed a total of 3 late-days that you can use in 24-hour chunks at anytime. Please note that once you use-up your late days, no additional extensions will be granted for any reason at all. You should thus save your late-days only for true emergencies. Also note that everything must be handed in by the end of the last lecture in the quarter. No assignments nor projects will be accepted after that date even if you have late-days left.
- Homeworks: 30%
- Mini-projects: 30%
- Midterm: 15%
- Final: 25%
- We hope
you will attend every lecture. If you miss a
lecture, talk to a
friend who was present, and be sure to check the Web site for class
- The course website and mailing list will be used
extensively to provide you with
course information, such as the schedule mentioned above, homework
and solutions, class messages and many other things. Please see the main webpage of the course for details.
- Computer Systems
- For the required hands-on homework, access to Microsoft SQL
Server is needed, for which you will all be given accounts. This
software is available in the NT lab. Additional
software may be required for the project. You are allowed to use a
relational database management system, such as MySQL, Oracle and DB2,
if you wish. In that case you need to install it yourself. We will
support at all.
- Note: You will be required to change the passwords the
first time you access to MS SQL Server IISQLSRV. The new passwords must
obey the Windows password policy as follows (from "MSDN" website):
- Password complexity policies are designed to deter brute
force attacks by increasing the number of possible passwords.
When password complexity policy is enforced, new passwords must
meet the following guidelines:
* The password does not contain all or part of the account
the user. Part of an account name is defined
as three or more
consecutive alphanumeric characters delimited
on both ends by
white space such as space, tab, and return, or
any of the
following characters: comma (,), period (.),
underscore (_), or number sign (#).
* The password is at least eight characters long.
* The password contains characters from three of the
following four categories:
o Latin uppercase
letters (A through Z)
o Latin lowercase
letters (a through z)
o Base 10 digits (0
characters such as: exclamation point (!), dollar sign ($),
number sign (#), or percent (%).
- Please contact the TA if there is some problem with your
account on IISQLSRV.
- Computer Use Policy
- Some excerpts from the campus policies.
Take them seriously: "You must use all UW [computing] resources in
accordance with local, state, and federal laws. These laws cover such
as illegal access to computer systems, networks, and files; copyright
and harassment issues... Software and information resources provided
the university for use by faculty, staff, and students may be used on
equipment only as specified in the various software licenses.
use of software, images, or files is regarded as a serious matter and
such use is without the consent of the University of Washington...If
of computer software, images, or files occurs, those responsible for
abuse will be held legally accountable."
- Academic Misconduct
- All work turned in is expected to be your own.
are encouraged to study together, each student is expected to produce
or her own solution to the homework problems. Coping or using sections
of someone else's program, even if it has been modified by you, is not
acceptable. The University has very clear guidelines for academic
and the staff of CSE 444 will be vigorous in enforcing them.