Car Classified website

Website description & specification Car classified website(For example of similar website please visit www. [login to view URL] [login to view URL]) There will be four types of user for this website. 1. The visitor/or buyer who will be able to search for used car and if they find a suitable car they will be able to contact the seller. 2. Private customer/seller- individuals who want to sell their car. They should be able to place an advert in the site. (both paid and free) 3. Trader- they are car dealers/agents. They should be able to post an advert as well. 4. We the admin, should be able to do what the above user can do and have overall control over the system. Other Features Auto match email reminder -Find a car you are looking for Short list car up to 15 cars Bulk posting for trader Promotional code for free ads Admin should be able to place advert Admin should be able to add credit into trader account 1. The system should be developed using the PHP programming platform. 2. The system should be deployed using the MYSQL database Management system 3. The MYSQL database should be deployed using the provided Database Model (Please refer to the provided .mdl file which has been included with this document.) Use of a good and Robust templating system – so that scripts/controllers/objects and template files are easier to maintain frontend and backend. A Very good template system is SAVANT 3 – PHP templating system (or any other tamplating system you are comfortable with ) 4. The system should be built using complete error logging and debugging mechanisms. 5. All scripts and files should be carefully managed and placed in the correct and relevant locations (*directories) 6. Good use of MVC framework (classes/controllers/viewers) 7. Use of global declarations where possible – this enables future changes simpler 8. Centralized snippets which are used to handle core system parts such as database configurations, good use of Constants files which allow future changes to be made quite simply – in the case where table names are altered...etc.. 9. Use of separate database table name(s) constant files (such as [login to view URL]) 10. The above file can be used to make reference to tables in SQL statements* 11. To make system loggings much simpler and easier to maintain even in the near future it is recommended that a simplified logging system is developed, example – create a [login to view URL] -> file which holds two parts the name of the type of logging and the path to the folder which maintains this sort of errors in a structured manner. – now to accomplish the final part which is how the system/scripts will determine where the path lies, build a Logger object which opens the [login to view URL] file and searches for the name of the type of logging and then does the real logging, obviously use good file naming conventions to keep errors trapping simple and effective* 12. Setup of cron scripts which are scheduled scripts that will run on a timed basis such as the backup of the entire database and individual tables. 13. Complete and function banner management system. 14. Image files should be stored in relevant folders, this also includes all the motoring advertisement pictures refer to the design view of the tables of the database model files which has been attached with this document. 15. Validations should be an intense process and carefully considered as both client and server site validation is a must* e.g. Registrion process, advert placement, etc. 16. In brief some of the common web technologies that should be used during the development of the frontend are – AJAX,JavaScript,JQUERY,CSS,XHTML use of other common open source libraries such as mootools, scriptaculas, tinyMCEeditors libraries. 17. Browser side scripting should be carefully deployed so that all scripts are compatible with commonly used browsers including various versions*