Auction Listing Manager

The following system is an existing Auction management system is in place using Spring Framework, Hibernate, and Ebay API that needs to be enhanced to the point where teh coder will need to make the attached use case scenario work. The project is about existing the existing work to include the following modules. Registration, Inventory Manager, Auction Lister, Customer Support Manager. The project features how to sell an item as well as how to manage an inventory and how to communicate between the buyer and the seller. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform • Programming Languages: Java, HTML, JavaScript, CSS, • Java Libraries: Spring Framework, Struts, Log4J, Ebay API, Hibernate, Jasper Reports, Velocity • Database: MySQL 4.1 • Application Server: JBoss 4.0 • Build Tool: Ant Targets  Build  Deploy  Javadoc  JUnit test  Jalopy/Jindent Source code formatter  FTP Upload  Send Email Design/Development Process Standards to be followed: 1.) All code must conform to the coding standards document. 2.) Every class much have a JUnit test associated with it. 3.) All builds must be down through Ant. 4.) Every build must be dependent on the JUnit tests passing. 5.) JUnit tests must be executed through Ant as part of the normal build. 6.) Every test script in the test plan needs to be tested and the test must successfully pass. 7.) Every subcomponent must have an accompanied technical detailed design with it.