1. MSDE 2000 database
1a. Design Database schema based on all available export fields from MS Project.
1b. Compatible with MS Project 2000.
1c. accommodate master and sub projects. (multiple projects inserted into a master project).
1d. Develop Script to create database schema and indicies.
2. Develop script to import/Upload MS Project Files to Database.
2a. MS Project 2000 files
2b. Parameterize import script to accept directory location and .mpp file name -or- directory name only ( to import multiple Files with .mpp extension.)
2c. When a .mpp file is imported that contains links to sub-projects then import linked subprojects.
2d. Parameterize input script with option to overwrite existing projects or (default: update existing projects).
2e. Accommodate and syncronise the database with any add/delete/changes that occured in any exportable field in .mpp file since last update.
2f. create optional parameter to log event, progress, timestamp and diagnostics to .txt file.
2g. Save last log to Database table.
2h. Make the Log table generic to be able to log progress and errors for different scripts, events and activities.
2i. Provide option to overwrite or append to the log.
3. Develop parameterized utility script to export selected tables.
3a. Accomodate export selected table(s) schema and metadata only.
3b. export selected table(s) data only
3c. export selected table(s) schema, metadata, and Data.
3d. Export to MS access 2000 database.
3e. Export selected schema and data to MSDE database.
3f. Ability to log export event, progress, timestamp, and diagnostics to Log table.
4. Produce .Net web site control panel to administer utility scripts.
4a. Create new, empty database
4b. Import/Export to existing database
4c. Select file or directory for import/export
4e. Select tables for import/export
4f. Select schema, schema & metadata, or data for export.
4g. Toggle logging on or off.
5. Provide graphical utility to manage and administer MSDE database.
5a. Research and select the best free msde administrator utility.
6. Provide detailed deployment instructions for web deployment and desktop deployment ( win2k/win XP)
6a. Provide suggestions for future improvements.
6b. Provide "lessons learned"
7. Critical to Quality:
7a. Time to delivery.
7b. Flexible DB design for future enhancements.
7c. Parameterized scripts
7d. Table driven parameters.
7e. Simple, Easy to use interface.
7f. Must run on desktop as standalone (with command line or graphical utility) if no webserver is available.
[url removed, login to view]?frame=true