12/3/2008 Deliverable
Tuesday, December 2nd, 2008During Iteration two, we aimed to complete the following use cases:
- Administrator creates Faculty Search
- Chairman assigns EARS Users to Faculty Search Committee
- EARSUser views list of Applicants
- EARSUser views Applicant profile
- EARSUser posts Comment about Applicant
In addition, we did some code refactoring from Iteration 1, and decided to begin using stored procedures in our database, rather than SQL queries in our Java Code. We ran into a couple snags with the database stored procedures and are in the process of swapping from a PostgreSQL database to a MySQL database due to it’s enhanced Stored Procedure capabilities.
Class Diagram
System Sequence Diagram
System Sequence Diagram
During Iteration three, we are hoping to complete the following remaining use cases:
- Chairman assigns Faculty Review
- EARSUser reviews Applicant
- Chairman changes Applicant status
- EARSUser changes active Faculty Search