Final Year Project: Create an Application That Compares Two Databases and Provides Feedback to the User about the Differences in Structure and Content (2007)

The overall aim of this project is to create an application that compares two databases and provides feedback to the user about the differences in structure, content and options to update either of the databases to match. An agile methodology and test driven design will be used to write the application, this is to compare an agile methodology to traditional methodologies to assess the viability of an agile and test driven approach.

After a year working with web clients and back-end databases, it became clear that a large amount of time was being wasted by finding similar bugs within the databases; the problem was recreating these problems on the development server, over time the schemas of the development server and the live server had changed, for example the development server contained stored procedures that had been deprecated on the live server which meant that tracking bugs on the development server was almost impossible without ensuring that the up-to-date stored procedures had been copied over.

Some of the issues also arose from data stored in the database that was hard to recreate on the development server, such as mimicking users and their details within the company’s Intranet site as systems company wide are tied to Windows Authentication so developers couldn’t simply change their access levels on the live systems without having to stop another developer and ask to reset their permission. The ideal application would have been inexpensive and would have simply compared the two databases, highlighted any differences and allowed developers to simply click and sync the databases together.

• 12,000 words – 60 pages in length
• Good use of literature
• Well written throughout
• Include coding standards
• Ideal for IT and computing students

1: Introduction
The Concept: Snow
The Aims and objectives

2: Analysis
Current Methods
The market
Lifecycle
Test Driven Design1
Best Practices
The User Interface

3: Design Chapter
Design needs
Case Studies & Personas
Type of application
Programming Language
Testing framework

4: Implementation
Milestone 1
Milestone 2
Milestone 3
Milestone 4

5: Evaluation
EXtreme Programming
Test Driven Design
SMO
UI Elements
Future Improvements
Overview

6: Conclusion

Bibliography

Appendix Section