SNC ESL Database System
This project focused on redesigning the ESL Database system originally built on Access 2000. The previous system suffered from non-normalized and "dirty" data, creating usability challenges, especially in managing rosters and grades. The updated system, primarily developed in C#, aimed to improve information retrieval through user-friendly DataGridViews and a modular design. Major enhancements included better enforcement of referential integrity, quick student searches, and the ability to edit rosters seamlessly, laying the groundwork for future development and feature expansion.
SNC ESL Database System
E N D
Presentation Transcript
SNC ESLDatabaseSystem Paul McEnaney Spring 2010
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
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
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
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
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
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
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
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
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
