This preview shows pages 1–3. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: . . Fall 2007 CSC/CPE 366: Database Modeling, Design and Implementation Alexander Dekhtyar . . Project: Implementation Stage Due date: Thursday, March 20 . Overview This document provides instructions for the implementation stage of the course project, and specifies the expected deliverables, as well as the delivery process. Deliverables The project will have the following deliverables: Final database design document . You need only submit the simplified version of the database design document, which includes: 1. The final E-R model of the database. 2. The final relational model of the database. 3. Changelog. Include all changes in design undertaken after Lab 4 submission. Submit hardcopy to the instructor at or before the demo. Code. All code developed for the project. The code must be submitted to the project wiki. Each team shall create a separate sub-repository of the form Color-Name and store the code archive within the sub- repository. Include all developed code. Red Cohort teams shall include the entire snapshot of the web site developed by each team. Also, Red Cohort teams shall put a link to their sites on the project wiki. Submit softcopy to the wiki. Notify instructor via email when submission is made. 1 Documentation. Brief documentation outlining how to install the soft- ware developed by each team shall be included with the code submis- sion. Submit softcopy with the code. Submit hard copy to the instructor at or before the demo. Data. Each team shall ensure that there is a way to populate the database of their application with data. Use the NUTRITION dataset as the sample database. Provide instructions for how the sample database can be loaded. Generally speaking, this can be achieved via one of the following ways: You can embedd load sample database functionality into the front end of your software. (for example, accessbile only to the program administrator accounts). You can create a standalone script which creates the database and populates it with data. You can include SQL scripts for creating the database and for populating it with data. Submit softcopy of all materials with the code. Submit hardcopy of the database setup instructions to the instructor at or before the demo. Status Report. Each team shall prepare an assessment of the teams progress towards the full completion of the software. In particular, the status report shall indicate which functionality is completely im- plemented, which functionality is partially implemented, and which functionality is not implemented at all....
View Full Document
- Spring '08