IST466: Database Programming
Course Syllabus
Fall 2002, TTh 11:00 am – 12:15 pm, Morrow
G31
|
Instructor |
:
Daniel Dementiev |
|
Office |
:
Prichard Hall 208 |
|
Phone Number |
: (304) 696-7241 |
|
Office Hours |
:
Mon: 8:00 – 9:30, 1:30 – 3:00 Tue: 8:00 – 9:30, 1:30 – 3:00 Thu:
8:00 – 9:30, 1:30 – 3:00 Fri:
8:00 – 9:30 |
|
E-Mail |
Textbooks:
The following textbook is required for the course:
Oracle 9i: A Beginner’s Guide, by Michael Abbey, Mike
Corey, and Ian Abramson; ISBN: 0-07-219279-8.
Supplementary sources:
Computer Requirements:
I will be sending class announcements,
updates, etc. using your Marshall e-mail account. Access to a WWW browser is required (Netscape 4.7 or higher or
Internet Explorer 5.0 or higher) and Secure Shell Client.
Course Description:
Concepts of high-level database server such as oracle database instances, the
database data files, rollback segments, log files, table partitioning will be
discussed. Database administrator functions, user management, and usage of
Oracle service tables will be learned. PL/SQL language is emphasized.
Credit:
The course is three
(3) credit hours. It includes classroom lectures, exams, and laboratory
programming projects. Students will participate in programming projects that
illustrate the implementation of concepts in database applications.
Pre/co-requisites:
IST365: Database Management
Desired Objectives/Outcomes:
By the end of this course, you should be able to:
-
Create and manage
Oracle databases
-
Demonstrate
programming skills Oracle SQL language
- Develop procedures and functions using Oracle PL/SQL
- Manage user’s privileges and roles for Oracle databases
Instruction method:
There will be approximately 3 contact hours of classroom lecture per week. I will try to give you at least half of one
class per week to work on lab assignments once they have been assigned. The laboratory programming projects cover
the major topics of the course.
Students may work on their assignments in Prichard Hall 200 or 207.
Evaluation method:
Evaluation of student's performance will be based on the quality of your
performance on programming assignments, exams, and class participation.
Grading
Policy:
Final grades are based on performance in assignments, exams, and attendance as
indicated below.
|
1
In-class Exam |
20% |
|
Final
Exam |
30% |
|
Projects |
30% |
|
Homework
assignments |
15% |
|
Attendance
& Participation |
5% |
Assessment of Projects:
The grading of all programming projects will take into
account the following:
1.
Although the most
important attribute of a program is correctness, grading will take into
consideration (if appropriate) such
items as time and space efficiency, documentation,
etc.
2.
Programs and scripts
must have proper inline documentation and must be properly indented. Up to 20%
can be deducted for poorly documented and/or poorly indented code.
3.
Although interactions
with other students are encouraged, you must compose your own answers, unless
otherwise noted.
Individuals who utilize other people’s code, thoughts, or
ideas must provide appropriate references to said resources. Failure to provide such documentation will
result in a failing grade for the assignment, and may result in a failing grade
for the course.
In determining the overall grade for a project, you can
expect the following grades based on performance:
A – Excellent work that meets and/or exceeds all of the
requirements for a given project, code compiles and works for multiple test
samples, all code and associated files are well documented, and the code is
written efficiently.
B – Good work that meets all of the requirements of the
assignment, but may have errors in documentation or coding, or contains code
that may not work with all possible data samples.
C – Average work that meets all of the requirements of the
assignment, but is missing one or more of the items in its entirety that is
mentioned in terms of an A grade.
D – Below average work which fails to meet one or more of
the requirements of the assignment.
F – Unacceptable work, which fails to meet two or more
requirements for an assignment, or has code that will not compile and execute.
Final letter grades are determined based on
the following grading scale:
|
90-100% |
A |
|
80-89% |
B |
|
70-79% |
C |
|
60-69% |
D |
|
Below
60 |
F |
The instructor reserves the right to change these values depending on the overall class performance and/or extenuating circumstances.
Policy Statement:
Programming assignments: The
course includes a number of programming assignments. All assignments are due by
midnight on the due date. Late assignments will be penalized at the rate of
10% per day (including weekends).
Exams: There is one midterm exam and a comprehensive Final exam
(as scheduled). Exact dates and times of exams will be announced in class.
Final exam will be given on Thursday December 12 from 10:15am till 12:15pm.
Make-up
Exams and Late Penalty: Make‑up exams will not be given except under unusual circumstances and
satisfactory written justification. Any
student who misses an exam due to an unexcused absence will receive a grade of
zero for that exam with no opportunity for make-up or substitution. University excused absences or those
occurring with a good reason will be excused.
Make up exams must be taken within one week of the original scheduled
date. The decision whether to give a
make up exam rests with the instructor.
Passing grade:
Programming assignments and exams are required parts of the course and
must be satisfactorily completed to pass this course. A student must have a passing performance on each part. A failing grade on a component may
result in a failing grade in the course.
Attendance Statement:
Class attendance is not mandatory and is not a required part of the course,
although highly encouraged. Those who miss a class should remember that it is
their responsibility to cover all the material by themselves.
Withdrawal Policy:
The University
withdrawal policy is followed in this course. The last day to drop an
individual course for the Fall of 2002 is November 1, 2002.
University Holidays:
The class is officially dismissed on the following dates:
Labor Day: September 2, 2002
Fall Break:
November 27, 2002
November 28, 2002
November 29, 2002
Effort
Required:
This course is provided as a 400-level course and due to the amount of new
concepts presented in the course there will
be a considerable amount of development and research effort required of
the student. For every one hour in
class, the student is expected to put in an effort of at least 3 hours outside
the class for studying and programming.
Because of background and preparedness, some students may have to put in
additional efforts.