| Assignments/Project
This is the page where you can view and download your
assignments. Just click on the assignment number and it will take you to the page
where you will get all the details for that assignments. If an assignment is not
hyperlinked it means that details of the assignment are not yet available.
| |
Remarks |
Coverage |
Weeks |
Book
Chapters |
Assignment 1 |
Flat
Files in Java |
1 and 2 |
1 and 2 |
Assignment 2 |
Data Modeling -
Three-Part EER Diagrams Exercise |
3 |
3 and 4 |
Assignment 3 |
Real Estate Problem Extensions |
4 |
4 and 5 |
Assignment 4
and 4N |
EER Diagrams - Scholarships Problem with
Normalization (4N) |
5 |
5 |
EXAM I |
|
6 |
1-5 |
| Assignment 5
(over two weeks) |
Project - Phase I (Establish team and find a project.) |
7-8 |
1-5 |
Assignment 6 |
SQL |
7-8 |
7-8 |
Assignment 7
(over two weeks) |
Project - Phase II (Detailed description of database design) |
9-10 |
3-5, 7 and 8 |
| EXAM II |
(not given in
Spring 2004) |
9 |
3-5, 7 and 8 |
Assignment 8 |
(not used in
Spring 2004) |
10 |
3-5, 7 and 8 |
Assignment 9 |
Review for Reading
re Physical DB Design and Performance (not yet done) |
11-12 |
6 |
Assignment 10 |
Project
- Phases III and IV (Submit
milestone reports and Final Report) |
13-14 |
1-5, 7-8 |
Project
1. Establish the team
and find a project 2. Submit
Proposal
3. Final submission |
|
|
|
Project:
The idea of the project is to give you a feel of of how a real life information
system is developed, using a DBMS. You will determine the requirements for the system,
design the database and develop a menu driven information system to satisfy these needs.
Your final submission should include the working software and documentation. In the
documentation include the description of the business/case you analyzed and their
requirements for information. Also show the ERD and tables you designed. Provide user
instructions how to use the system you developed and show the various forms, menu and
reports. You will have a better understanding of how these peices fit together as we
proceed through the first half of the course.
This is a team project, where 3 to 4 students develop a 'relatively small' system
utilizing a DBMS. You are free to choose any case for your project. It could be one from
your lab book, text book or one of your own.
Due consideration will also be given to the project details, such as: overall design,
data validation, integrity checks, fields labels, navigation keys and any extra feature
you wish to incorporate. Of particular importance is a demonstration that you have applied
all relevant database design techniques discussed in the course.
Before you begin your project you need to give the instructor a proposal
providing a rough outline of what you plan to do. The focus of this proposal should
be on the expected output from the project: initial designs of screens, forms,
query results, and reports and most important.
Project Proposal:
You can talk to me to clarify your ideas about your project. For the proposal, submit a
brief write-up of your case, initial descriptions and our illustrations of your expected
output, and an E-R diagram for the database. The diagram should include the context and
some user requirements. You are allowed to make changes to the basic idea when you
actually implement your project, as long as it does not decrease the project scope. The
proposal should be several pages long.
The Finished Product (The Deliverables):
Your system should include:
· Tables
You must have at least 5 tables. The relationships between the tables should be defined.
Take care to correctly define the properties of all the fields in the tables.
· Queries
You must have at least 5 queries. At least 3 of them should be parameterized.
Parameterized means that the criteria of some of the fields of these queries must be an
expression and not a constant.
· Forms
There should be at least 5 forms. These should be data entry/updating forms. At least
one of them should have a subform that depends on the main form. Take care to title
the forms correctly, At least one of the controls on each form should be a calculated
control. This means the control should contain an expression in its control Source
property.
·
Reports
There should be at least 2 reports.
· Switchboard
Your project must begin with a switchboard to allow the user to easily navigate to your
forms and reports.
· Macros/Visual Basic Module
You must write at least 1 module. You could use this module to calculate and return value
or signal an error on a form.
Important dates:
Late date for proposal :
Mid to late March, 2004 (exact date to be determined)
Final Project due : Last day of class
(Early May, 2004 - exact date to be determined)
|
