CIS 573 Classtime Scraper - Criteria CORRECT FUNCTIONING: (70%) 1. configurable options for scraper: * fall vs. spring vs. summer * URL's of the three websites (must be persistent) * output only to files (default) vs. output to files and database * staging vs. production database (if database output selected) 2. scraper GUI must remain responsive; must report progress to the GUI 3. scraper must be able to be stopped before completion (confirmation is advisable) 4. By default, scraper must deposit all info into .csv files 5. if in database-update mode, scraper clears old data 6. scraper finds at least as many sections as my scraper deduction if less, extra credit if more 7. scraper GUI, when scraping has completed, shows: --num departments, courses and sections found --the URL which was scraped --the location of the output files 8. ASP.NET application which queries the database (good as Pat's) 9. two copies of the ASP.NET app: --1st pulls from a staging database --2nd pulls from a production database production site should never be allowed to appear "broken", either due to ASP.NET code or database issues CODING STYLE: (30%) 1. try-catch, or not unhandled exceptions 3. avoid the use of tabs 4. method and field names descriptive 5. not multiple exit points to a program 6. source code, including comments, under 80 chars per line 7. no compile warnings 8. both debug and release modes compile 9. only constants appear in UPPER CASE 10. std. winapp behavior Minimum menus will usually include File...Exit and Help...About 11. prevent a program from running twice 12. icons and window titles --main form title --About form title --executable icon --About form picturebox (if present) 13. In menus, I try to use of the word Exit, which is the de facto 16. explicit public, private or protected modifiers 17. begin private fields and methods with a small letter, and public fields and methods with a capital letter 19. About form not hardcoded