CSCI 311 Functional Prototype
Total Page:16
File Type:pdf, Size:1020Kb
CSCI 311 Functional Prototype What to hand in: • Submit the following to VIU Learn by February 16, 18:00 o .zip file containing all css and html for your site’s initial prototype o MidwayReport.pdf Functional Prototype Early in the term, your team will develop a crude functional prototype of your site. It should include, at minimum: • All main pages • All navigation between all pages (consistent) • Rough layout of all pages • Colour, style, and font choices for all text • Underlying structure of site (folders, files, naming conventions) • Image placeholders for all media At this stage, this is a mockup or rough prototype, so you are encouraged to do the following: • Use placeholder text (like Lorem Ipsum) o NOTE: do not use placeholder text for headings • Use placeholder images • Hardcode any validation (accounts) Your prototype will be evaluated by two of your peers using the following criteria: Criteria Level 2 Level 3 Level 1 Location of issues Links and No broken links. All Few broken links, Navigation Navigation navigation and navigation is inconsistent and consistent and no fairly consistent many broken dead ends. links Styling (font, Consistent styling Some inconsistent Inconsistent layout) and layout on all styling, and or style styling, and style pages. Styling in doesn’t match site doesn’t match keeping with site theme. site theme. theme. Clarity (visual Site is clearly laid Site is fairly clearly Site is poorly laid clarity and out, good use of laid out but could out, with weak grouping) white space and use better white grouping. grouping space and grouping Structure All pages use good All or most pages Pages lacks (underlying logical structure, use some logical logical structure. html including headings, structure, but structure) paragraphs, some elements are sections, and other not correctly used elements. or missing The prototype will also be evaluated by the instructor using the following criteria: • Links and navigation all working and consistent • Styling is consistent (internally) and consistent with purpose of site • Layout of site is well thought out and clear • Colour theme is consistent and appropriate • Appropriate HTML Structure (headings, sections, paragraphs, lists, …) • Underlying file structure is well thought out and will transfer well to future stages Midway Report: At this stage, review what was planned in the original team formation, and update as needed: • What tasks each team member will perform • Set internal deadlines for all stages of project • Identify your team’s stretch goal(s), including: o A brief description of the technology o A link to its source or documentation o Why it is interesting to you o What purpose it will serve in your project Stretch Goal Each team will choose up to three technologies that are not covered in this course to incorporate into the project. This is a chance to try something out that you’ve been meaning to investigate. Teams will give a brief presentation at the end of the term about this stretch goal. Some options: • Use a PHP framework o Laravel o Symfony o Phalcon o CakePHP • Use a JavaScript Framework: o Angular o Google Web Toolkit o Node.js o React o Vue.js • Use another language o Python (or Django framework) • JavaScript Library o Type Script o Three.js o Phaser (2D game framework/library) o Physics.js o Math Jax (math display) • API: o Google APIs: § YouTube § Geocoding APIs (location) o Social Media: § Flickr API § Twitter API § Instagram API o Other: § Soundcloud API § Bit.ly API § Dropbox API § OpenWeatherMap (weather forecast) § Dark Sky (weather forecast and historical data) o Here’s a curated list of open apis: § https://github.com/public-apis/public-apis .