We have a database of jobs. We need the jobs to be filtered in content and automatically posted and made available on our webpage in a certain format. The jobs are being put into the database by a piece of Java software. The web site already exists, and we have a presentation mechanism in mind.

We would like the posting software to used Java, Javascript

the existing site is www.avidtec.com, i want to pull out job postings out of our internal database and post them in a format that is available lke this website: http://www.wallach.org/jobs.htm ,

i want Java to pull the data out of the jobs database.There already exists a Hibernate model for this database.In terms of taking the data that is pulled out and posting it --The website is now hosted on a Linux-based platform,that now has extended capabilities to do things via CGI-BIN or you believe that I am possibly host JSPs/servlets,or we could use FTP to update the HTML files.We will have to discuss the best way to do this.

Your execution on this project must be exemplary. I demand quality and the following stipulations must be adhered to in order to insure a high-quality product:

1. There must be a design written up in an industry accepted tool (Visio, Powerpoint, Rational Rose, etc) and I need to approve this design in advance -- we want a graphical layout of your approach with clear titles and a sensible layout of components and functionalities -- I must see this format in either .JPG or .PDF

2. All source code, test code, build files, design diagrams, documentations will be delivered by you and owned by us;

3. For each milestone, I expect to see unit test code (preferably in JUnit or acceptable) that will continue to work as the project proceeds to successive milestones.
This test code should exercise important flows through the system in a way to exercise success and failure conditions of the key features of the algorithm or routines that you use.

4. I expect detailed, concise and understandable documentation to be generated in English and delivered by you for each milestone -- detail the parts of the code, the assumptions you made, the problems you encountered, the possibilities you considered and the way forward that you chose;

5. Source code comments where appropriate;

6. Tight, quality I mean quality with a capital Q source code.