IBRI College of Technology Department of Information Technology. Intercollegiate Web Programming Contest On 12 March, 2013 (Tuesday)

Transcription

1 IBRI College of Technology Department of Information Technology Intercollegiate Web Programming Contest On 12 March, 2013 (Tuesday) Eligibility: Web Programming Contest Rules The contest is open to Diploma and Advance Diploma level students working in teams. Team members will be required to develop a website at Ibri College of Technology campus, and must be officially registered for the Web Programming Competition in IT Department. Contest Duration: Contest starts at 10 am and closes at 2pm (4 Hours). No.of Teams and Team Size: Team Size: 02 Students. 02 Teams per College Competition Purpose: The purpose of the competition is to produce a 5+ page website based on the competition topic (announced on the day of the competition) with permitted development tools, target web browsers, and teamwork, while applying HTML, CSS, JavaScript, PhP, MySql, attribution, accessibility, and user interface standards. Each team will be assigned to a computer. Team may make use of content (e.g. images, audio, and video) provided by IbriCT. Cheating: The emphasis is on the team creating the website. Therefore, any team determined to be cheating, interfering with another team, or interfering with competition servers/workstations, will suffer a severe point deduction or be immediately disqualified from the competition. Downloading, and/or installing software on the competition computer is treated as cheating. Prohibited Content: Each website should not contain material deemed objectionable. (e.g. no profanity, nothing offensive to a person s gender, ethnicity, or religious beliefs, no references to alcohol, tobacco, or drugs)

2 Requirements: The website must contain the following components: 1. Introductory article or overview 2. Menu or index of some type 3. Team contact information a. Team Name, College Name b. Department / Specialization c. Team member names and addresses Standards Compliance: Web pages must employ standards-based web design with well-formed HTML and CSS. The following will be applied in judging regardless of whether the HTML was hard-coded or created with an editor: 1. The expected DOCTYPE standard for building the web pages is: HTML Every HTML document should pass the W3C Markup Validation Service with 0 errors (warnings are acceptable). 3. Every HTML opening tag (i.e. <p>) must have a matching closing tag (i.e. </p>). Tags that have no closing tag should include a space and the closing slash at the end of the tag (i.e. <br />). 4. The document tags must be well formed. i.e. a. Well Formed: <p><b><i>ibri College</i></b><br />Car</p> b. Not Well Formed: <p><b><i>ibri College</b></i><br>Car 5. All tags must be in lower case. 6. Web pages must be fully functional in the Internet Explorer or Firefox or Chrome web browser.

3 Default Pages: The only default page filenames that will be honored on the contest web server are: index.html index.php (.php is the only extension that will be parsed for PHP Scripting) Templates: Templates must be created using any of the following methods: From scratch From creating custom template files with editable and non-editable zones From using PHP functions to produce a template system Use of any built-in template, template wizard, or template from the internet or any other source is not permitted, and is considered cheating. Cascading Style Sheets: Cascading Style Sheets must be created from scratch. Use of a cascading style sheet from the internet, or any other source is considered cheating. JavaScript: Each team may utilize JavaScript in their website, provided the team writes the code during the competition. Use of premade JavaScript code from the internet or any other source is considered cheating. Testing: It is recommended that each team regularly view the latest revision of their website using Internet Explorer / Firefox / Chrome and the URL provided for the team s website. This will ensure that the website files are named correctly, and operate as expected. Website Submission: Each team s website will be served from the competition web server, and will be viewed throughout the day by the judges in order to monitor development. At the end of the web design period, teams will upload their final website version for judging.

4 Reserved Rights: The decision of the judges is final. The judges reserve the right to modify the competition rules and/or submission procedures as deemed necessary when a technical issue arise during the competition. The judges reserve the right to view the workstation of each competing team either in person or via remote desktop monitoring software. The judges reserve the right to make clarifications with regards to the competition rules as deemed necessary.

5 Judging Criteria: 1. Content a. Relevance of content b. Accuracy of content c. Correct spelling and grammar d. Good use of content chunking e. Adherence to copyright laws (e.g. Content Attribution) 2. Aesthetics a. Visual appeal and style (color, contrast, fonts, white space) b. Consistent look and feel c. Readability d. Minimalist design (avoid extraneous information) 3. Design a. Adherence to HTML standards b. Effective navigation and working links c. Effective use of multimedia content (images, audio, video, animation, etc.) d. Browser compatibility 4. Usability and accessibility a. Written in user s language b. Minimize required user actions c. Progressive exposition of levels of detail d. Navigation feedback mechanism e. Effective user guidance (help and error messages) 5. Validations and Storage a. Effective validations b. User Control c. Database Schema d. Data storage and Retrieval e. Integrity Constraints