CIS 399 - Introduction to Oracle and SQL

Homework Assignments

Please turn-in assignments by email to .

You may have noticed that the regular homework assignments are due on Friday, a day when we don't have class. I don't want to ruin your weekend by having a homework due Monday, and I would prefer it if you hand in the homework on Thursday (one day earlier), but I know that isn't always possible. Friday is the compromise.

Data files for the book are available at the publisher website. Select the chapter at the top of the page, and select the "Student data files" link on the left side of the chapter page.

1. Chapter 1, pp. 46-47, Hands-on Exercises #1 and #3. You may create diagrams by hand, or with a drawing program (by hand is messier and requires physically turning in the assignment, but is sometimes faster and easier).
   Chapter 2, pp. 87-90, Hands-on Exercises #1 and #4. Submit any scripts spool files you modified or created.
2. Chapter 3, pp. 140. Hands-on Exercises #2 and #3. Chapter 4, pp. 194-197, Hands-on Exercises #1 and #3.
3. Chapter 5, pp. 260-263. Hands-on Exercises #1 and #3. Chapter 6, pp. 314-318, Hands-on Exercises #1 and #3.
4. Chapter 7, pp. 368-371. Hands-on Exercises #2 and #4. Form a group for a group project, and let me know who is in your group.
5. Chapter 12, pp. 588-589. Hands-on Exercise #2, parts 2, 3 and 4 (but not the LOV step). Hand in a project design document.
6. Chapter 8, pp. 410-411. Hands-on Exercises #1 and #2. Please turn in the .fmb files that you create. If you are working in Deschutes 100, and are unable to test your forms, please let me know. Instructions for using form builder in Deschutes 100 are on the main page for the class.
7. Chapter 10, pp. 512-520. Hands-on Exercises #1 and #2. Please turn in the .jsp files that you create. If you don't have Reports Designer on your PC, you can use either the PC in Deschutes 100 or the PC in my office.

Group Project

• Group teams of 2-4 students each will develop a database application using Oracle.
• The application code will be written in Oracle Forms/Reports, Java/JDBC, Java/JSB/JDBC, PHP or Python/Ruby, or something else (please let me know).
• Your database design should have between 5 and 10 related tables.
• Your database should implement as many of the concepts we have learned (or will learn) as possible, where applicable. For example, use VIEWs for report queries, create users/groups with different privileges, etc.
• Your application should have scripts for building the tables and seeding them with test data.
• Your application should have three or more stored procedures.
• Your application should have auditing for "mission critical" tables.
• Your application should use at least one each of SELECT, UPDATE, DELETE, INSERT statements (they can be in stored procedures).
• The application will be demonstrated in class during the last two class periods of the quarter. And no concept shots - the application has to actually work. :)

Back to Main Page