Overhauling system design
The first phase of our team's work will be to overhaul the overall design for the system. As it stands, the code suffers poor documentation, low functionality, and very tight coupling (too many inter-class dependencies). Since we will be switching to a new platform (see about AJAX below), it is both convenient and necessary at this time to restructure and reorganize the code.
Reimplementing the System in Ajax While we'll be able to re-use much of the code already in place, the older models are not fully functional. We will therefore be looking to implement core functionality for the TA, including file management and basic editing tools. We are also hoping to be able to begin implementation on the back-end of the system, including the CA, the AA and the databases with which they interact.
What is Ajax, Why use it
"Ajax represents an architecture for the software that is designed to be used with any web browser, but that includes an interface with the responsive feel of a desktop application. This means that, for example, a grid component such as a spreadsheet that appears in the web page responds instantly to the user's manipulation of the data, without the time delays or visual disruptions caused by the page "refreshing" or being rebuilt with new HTTP requests. Google's Gmail and Calendar, and Yahoo! Maps, are three examples of typical Ajax applications."
-Google Web Toolkit for Ajax
by Bruce W. Perry
Ajax offers an accessible and fast front-end that, unlike Java, doesn't require any user installations or downloads.
For more detail, please see our Methodology page.
![[ WPI Logo ]](images/wpi_logo.gif){kind=logo}