
Description of Final Project
the marking will be an onging process
create a project calendar with important dates
Your final project counts for 260 points (21% of your grade in this course). I would encourage you to attempt to treat the project like a "real world" situation involving databases.
Marks will be allocated for separate parts:
logfile is needed-- as Jan 9,2001
- a detailed log of everyday in the project should be kept
- you can use Yahoo calendar and share it with me( I should be able to access it any day that I want)
- with the following headings- month day "important dates" detailed description with minutes
- send account and details that are needed
document 1-- project specifications--.here the important decision of what to do--due Jan 12-- 20 marks
In the project specifications you will need to include:
Purpose - What your program will do, what need it fulfills, who the audience is.
Requirements - Describe in detail the minimum set of required features, functionality, capabilities that your program should perform by the submission date. In other words, if you are creating a major program with many features, what features will be functional when you turn in the project.
Submit project specifications for instructor approval.
document 2
It must be a word document with a chart or an Ms Project or spreadsheet file send as an attachment.
The "Feasibility Report" is a document which often is the first major piece that must be produced for the users. It is what the title suggests, a document that outlines the feasibility of the project for the users. The most important thing to remember about this document is that it is the basis of the user's decision to go ahead with the project . If you do not have a real user, then assume that you do or that you want to sell the product to some user. There must be some "USER" here.
The Feasibility Report is challenging (difficult in plain language) to write because you have to have enough information about what the user requires, preliminary estimates of costs, preliminary projections of development schedules and the like before you have done the complete study. In one sense it is an impossible task but it still must be done in order to secure the project. Keep in mind that users have the following three major considerations when they are making the decision to go ahead with a project or not:
| WILL THIS COMPUTER PROJECT SOLVE MY PROBLEMS? what does it accomplish ? for whom? |
| WHAT WILL THE PROJECT COST?---in your case can you do> |
| HOW LONG WILL IT TAKE AND HOW WILL IT BE IMPLEMENTED? how will you do it? |
Title page
Table of Contents
Logical Model
-Break it down in major parts
-Describe options considered for things like the following (assess feasibility of each possibility as it is described):
Recommendation
Development Plan
Project planning
document 3-- analysis and design -- modularisation ---60 marks---Jan 12
Use ALL the same steps as outlined on the modularisation handout.
Forms - List all the forms that you think your project will need with a brief description of each form.
Database Description - If the project involves the use of databases, list all database tables your project will use and include a brief description of each table. Be sure that you are capable of including the table(s) or a portion of them with your project for testing your project. You will need to create Access JET sample data for your project.
example
NORMALIZATION
Ward Patient *Ward number * Patient Number Ward manager Patient surname Ward name Patient first names Route Number @Ward Number @Doctor Identifier Doctor Prescription *Doctor Identifier *Prescription number Doctor Surname @Doctor Identifier Doctor first names @Patient Number etc Date Issued Drug Catalogue Label (prescription/Drug *Drug code Items) Drug name *Prescription Number Drug cost *Drug Code Drug notes Dosage Length of treatmentor just show it like this
Travel Agency
A travel agency arranges holidays for customers. Bookings are made directly by customers. When a customer makes an approach, the reservations clerk selects appropriate flight details and hotel details from lists which are regularly updated. The details are entered onto a Provisional Booking file.
The customer must confirm this booking within three days by sending a deposit of 10% of the costs. On receipt of the deposit, Reservations transfer the details from the Provisional Bookings file to the Full Bookings file.
Four weeks before the flight is due, Accounts send an invoice to the customer for the remaining costs. Accounts notify Customer services when the full payment is received, and Customer Services then send tickets and joining instructions to the customer.
There is no control mechanism for prompting customers to confirm the booking, or to chase payments. Business might be lost, and customers might miss their flights accordingly. IT could be used to retrieve such details and to automate the initiation of the reminder procedures.
There is scope for error in transferring the details between the provisional and full bookings files - IT could minimise this.
The system is a little too sequential. If all depts. used a common database, the customer billing could be automated, as could the issue of tickets, etc. Time would be saved and omissions avoided by not having to have information flows between depts.
The customer file provides a valuable marketing database which can be exploited for mailshotting in the future.
send in ERD, database with data in it.
actual code part 3--the actual working program-- this have is marked in three stages------165 marks---
Consideration will be given to a project that requires learning a lot of new material. All projects must meet the following MINIMUM standards:
- Have multiple forms
- Use VB prefix conventions for naming control variables
- Use at least one code module (.Bas) file
- mastery of functions, procedures, arrays, ---Speed Up your Apps with Data Structures----should be evident in the project
- In the code windows, use remarks throughout your program to describe what your code is doing
- Include an opening "help" form which introduces your project.
- error checking routines.
hand-in the program with all the proper files and packaging.
stage 1-basic prototype with some main options working--Jan 17
30 marks
stage 2-near completion with most options-Jan 22 ----105 marks
stage 3-completed Jan 25----ready to hand in-----------------------30 marks