Final Project Deliverable/Review
Vision
We envision an intranet-based Employment Application Review System for Lehigh University’s Department of Computer Science. The system shall be designed so that department faculty members can review applicants and collaborate asynchronously in order to find the best applicant for a given job opening. This system will reduce the overhead of the process and lighten the workload for the search chairperson.
Stakeholders
- Bryan Hodgson (customer)
- Matt Brophy (Project Manager/Developer)
- Saptarshi Kar (Librarian, Programmer/Analyst)
- Tat Phadhana-Anake (Programmer/Analyst)
- Mike Sands (Database Administrator)
- Greg Bosch (Prior Programmer/Analyst)
- Jeremy Tallman (Prior Programmer/Analyst)
- Jian (Maggie) Wang (Prior Programmer/Analyst)
In the third and final iteration of the EARS Project, we aimed to completed the following use cases:
- Chairman assigns users to Committee
- Chairman assigns Faculty Review to EARS User
- EARS User performs Faculty Review
- Chairman changes status of Applicant
- EARS User changes active Faculty Search
We also wanted to add security constraints into the system which would prevent users from accessing data they are unauthorized to see. These access levels were broken down into the administrative user, the chairman of each faculty search, and committee members of a faculty search.
Finally, we focused a lot more on testing during the third iteration, using JUnit for backend unit testing, and Selenium IDE for front end testing.
The following are a number of document produced as a result of this iteration:
Class Diagram
System Sequence Diagrams
Testing
- Unit Testing - JUnit
- Front End Testing - Selenium IDE
- Acceptance Testing (Link)
User Manual (Download)
JavaDocs (Link)
Some final statistics (Link to TAR file of code)
- Lines of Java Application Code: 4,334
- Lines of Java Test Code: 669
- Lines of JSP Code: 1,325
- Lines of JavaScript: 370
- Lines of CSS: 283
- Total Lines of Code: 6,981
Future Work
It is hoped that this project will continue in the future, either through an independent study, or as a project for another class. From the beginning, the Application portion of the project was scoped out, so this is something that will need to be accomplished in the future. Additionally, due to many factors, including a JSP learning curve, as well as re-factoring of code, there were a few user friendliness features that were left out of this release, including:
- Ability for chairmen to add custom Status and Rating levels for their faculty search. The code is written to support this, however an interface was not designed to give the chairman an easy way to accomplish this.
- The ability to search/sort users based on name, rating, etc.
- A dashboard page notifying users of recent faculty search news, or outstanding reviews.