IFSM410 CLASS PROJECT

Course Project

A semester-long project will allow the student to practice the skills learned in class. The project is to be completed by teams of three or four members(with approval). The product will be a professionally produced database system, which will include development of a working prototype of an application for an organization. The project can be assigned to each team. Otherwise, it is the responsibility of the teams to find an organization that will let the team complete a database system. The type of organization is not restricted; it may be a small business, a non-profit organization, or a division of a corporation. The choice should depend on the ease of access to and cooperation from the company or unit, and on the perceived database or information systems needs of the organization.

The project will be completed in stages. At the end of each stage, each team will submit one portion of the project (a "deliverable"). Each deliverable should be prepared in duplicate (two copies). A single copy is to be submitted. The other copy is to be kept in a project file (three-ring binder). The teams are to organize the project documentation in a three-ring binder; this project file is to be turned in at the end of the semester (after changes have been made, if necessary). The software for the prototype that was developed is to be saved on 3.5 inch disc/s and submitted together with the project documentation. Each group member should keep his or her own copy of the entire project.

Planning for each stage is highly recommended. Planning means that the team (1) identify activities to be completed during this stage (2) identify team member(s) responsible for those activities and (3) establish deadlines for completion of those activities. Be certain to allocate enough time in establishing deadlines so that the person(s) having primary responsibility for an activity can complete a draft version that can be checked by at least one other group member. It is also a good idea to allow yourselves several days before the delivery date for final packaging of the material to be submitted. The deliverables submitted will be assessed, either by signing off or rejecting the deliverable. In the case of a rejection, the group will have one week to re-do that deliverable. The deliverables are due on dates specified below. They will not be accepted late. Teams are to turn in whatever they have on that day.

DUE DATES for Deliverables:

Additional materials to be included in the final report:

• System Menu structure e.g. design tree, etc
• Design of the user interface (input) e.g. menu screens
• Documentation and Implementation Plans e.g. user manual, ERD,data dictionary, etc
• Project documentation and appendices e.g. Gantt Chart, Schedule, etc
• Sample Output e.g. reports, labels, etc.
• Software for the prototype developed.
• Other materials relevant to your project.

The final report must be professionally prepared and organized, containing all the earlier deliverables as well as the supplementary materials noted above. The final report should be systematically organized in a three-ring binder. The software for the prototype that was developed is to be saved on 3.5 inch disc/s and submitted together with the project documentation.

Teams will present their projects to the class on Dec 10, 1998 the second last day of class.

As occurs in many project groups in organizations, team members will have the opportunity to evaluate the performance of the other members at the conclusion of the project. The evaluation will be formal and confidential. The instructor will formally weigh the evaluations when assigning grades to individual team members. This means that each team's members may not receive the same grade for the project.