Database

Project Proposal

Each group will write a proposal for a system that solves a real or fictitious problem. The

proposal should describe the problem and how this database driven application will solve it.

Your proposal should include the choice of technology (e.g. Java on MariaDB... PHP on

MySQL) etc. If there is a change of technology prior to the project submission, you must inform

the instructor of the change.

The proposal should also describe the users of the system, and what they each will want to do

with the system. You must include at least 2 different user types. List the requirements in the

following user story form:

As a , I would like to , so that

There is not a limit to the number of requirements to be implemented and just because a story

exists, does not mean it

has

to be implmented in the final product. Least the stories in priority

order. The stories higher on the list should be implemented first, and lower on the list

implemented later. The final product must include the ability to Create, Read, Update and

Delete records (CRUD).