Calendar

From MWCSWiki

By the end of this semester we should have an executable architecture. This will be a working prototype that includes all of the basic features of Collex. By the end of the semester we will be able to use this prototype to test our design, populate our database and collect user feedback. Next semester we will pick up where we left off, implement more advanced features, fix bugs, and respond to user feedback (revisiting our initial design and planned features when appropriate).

early design stage: (we should be done with this section by mid September)
- explore similar applications and other approaches to this problem
- write literature review
- evaluate the existing needs in this area
- identify target users
- determine key features of this application (which belong in the prototype and which will be deferred to next semester)
- develop key objectives of this application

design stage: (we should be done with this section by mid October)
- decide which technologies to use (LAMP?, Java?, CSS?, a web content manager?)
- determine specifications and requirements
- design web interface and application behaviors
- design the OO model
- design the database
- determine specifications and requirements

implementation: (we should be done with this section by mid November)
- build the database
- implement the OO model (write the code)
- build the web interface
- write web content (there may be a significant amount of instructions, explanation, data dictionaries, and links to outside resources regarding linguistics)

data population and testing: (will continue with these tasks until the end of the semester)
- find users (to populate the database and provide testing and feedback)
- ideally these are people who speak an under-documented language. It might be hard to find many such users, so we will have to plan ahead of time get in contact with them and arrange everything.
- respond to initial user feedback
- general debugging and tweaking of features, display, and behavior