1 / 15

SNC ESL Database System

SNC ESL Database System. Paul McEnaney Spring 2010. Project Description. Previous System(s). Access 2000 Database Non-normalized / “dirty” data Difficult to use Roster issues CSCI 330 Version Stronger database design Good starting foundation. Older Systems. Access 2000. CSCI 330.

ion
Download Presentation

SNC ESL Database System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SNC ESLDatabaseSystem Paul McEnaney Spring 2010

  2. Project Description

  3. Previous System(s) • Access 2000 Database • Non-normalized / “dirty” data • Difficult to use • Roster issues • CSCI 330 Version • Stronger database design • Good starting foundation

  4. Older Systems Access 2000 CSCI 330

  5. Project Goals • Redesign the ESL Database • Mostly done in the CSCI 330 version • Upgrade ESL Database to Access 2007 • Develop a client application in C# • Focus on easy retrieval of information • Emphasis on rosters and grades

  6. Solutions • DataGridViews to present information • Quick search for students • Edit classes at the roster level • Not possible in the previous system • Remove “incremental indexes” from DB • Better enforcement of referential integrity

  7. What didn’t get done… • Application support for all database features • Student tests • Student pickups • Support for database path changes • Easier addition of students to rosters

  8. Approach • Start the application from scratch • Highly modular design • Easy for a later project to improve upon the code/design • Rapid prototyping, and frequent meetings with the client • Edit/Refine the prototype • Only throw away irreparable parts

  9. Demonstration

  10. Learning and Development

  11. Strategies • Think before you code • Does fixing this break something ELSE? • Don’t procrastinate • If you find a better way, go back and fix it • Understand WHY things work • Google EVERYTHING • You’ll find lots of “better ways”, some work

  12. Concepts • /*Documentation!*/ • ModularCode(& TESTING); • Efficient Code • If it doesn’t have to be in a loop, don’t put it in a loop • Handle Errors

  13. Future Direction • Editing/Adding to rosters • Data input could be simplified • Support more features already included in the database • Maintenance feature • Edit database lookup tables • Edit database file path

  14. A Word to the Wise • Calm down – we were ALL scared • Eating and sleep are IMPORTANT • Take breaks – stress will hurt your life • Start Early, test often • Write down brilliant ideas • Fix that “one more thing” tomorrow, when you’re actually awake and coherent

  15. Questions

More Related