Project Description

bullet Group Setup: Form your own team. Each team should have at most three members. Find people that you can work with. Do it early enough. If you have difficulty with finding the right group members, you will be assigned one or two. The deadline for this step is October 10, 2005.
bulletStep 1: Database Design: Each team is required to select a topic for their database project. The project should be comparable to the Student Registration System that we have discussed in the class. Imagine that you are developing the application for real!

Some topics that I come up with:
bulletInformation System for Supplied Chain Supermarket (e.g. Walmart)
bulletInformation System for Autopart Store (e.g. Auto Checker)
bulletBook Store Information System (e.g. Barnes and Noble)
bulletLibrary Information System (e.g. NMSU Library)
bulletHotel Management System (e.g. Hilton Hotel) 
bulletAirline Reservation System (e.g. Southwest)
bulletInformation System for a Telephone Company (e.g. Qwest)
bulletBanking System for a Bank (e.g. Wellsfargo)
bulletGeographical Information System (e.g. Mapquest)
bulletHuman Resource Management System (e.g. University HMR)
bulletInformation System for Transportation and Delivery Company (e.g. FedEx)
bulletInformation System for Airtraffic Control at an Airport (e.g. El Paso Airport)

You can come up with your own project topic.  This will need prior approval.

Requirement

Each team is required to write up a report detailing the design of its database system. The report should include:

  1. System Analyst: Write in plain English a systen specification. It should provide the answer for the following questions:
    1. what are the data and requirements for the system?
    2. what are the features that the system can offer?
    3. who are the intended users of the system?
    4. what can a user do?
    5. what benefits are there for using your system?
    6. what are the ten often asked questions in your application?

    Requirements from the literature are acceptable.

    Do not forget the assumptions you have made when design the database.

    For example: I assume that the library has only one copy of each book when I design a database for the library. Furthermore, I assume that each library item has an ISBN. Therefore, I use ISBN as the key of the entity named 'LibraryItem';

    2. This step should be done by October 25 and submitted as Project - Part 1.

  2. Designing your Database: An E/R diagram with constraints. Clearly identify

    1. Entity sets, each their attributes and key(s)
    2. Relationships , each with its attributes, the set of entity sets involved in it, and its multiplicity
    3. Translation of the E/R diagram into relational schema.

    The report should include the ER diagram and the SQL commands for creating the relations/tables as described in Item 3.

    It should also describe how the ten most often asked questions affect the design of your database?

    3. This step should be done by November 3 and submitted as Project - Part 2. It should also conform with Part 1.

  3. Step 2: Implement Your Database:
    1. Design the user interface
    2. Develop the code for populating the database
    3. Develop the code for users of the system

    Your system should be available for use by December 4.

    Follow this link for the instruction on creating database application with PHP.