G053 Lecture 22 Coursework Feedback 2010

1. G053 Lecture 22Coursework Feedback 2010 Mr C Johnston ICT Teacher www.computechedu.co.uk

2. Session Objectives • To receive further guidance on common misunderstandings after the first hand in..

3. FINAL DEADLINE • 3.10 on Friday 8th January. • Final marks will be prepared over the weekend and sent on Monday • Mr J’s normal remark policy applies • Tell me what you have changed wont go looking • Do not renumber pages • If you need to add extra pages do so … but number pages as letters e.g. if you need extra pages between 10 and 11 use 10a, 10b 10c etc • Loose your mark sheet and tough – no marks…. not marking work again!

4. Overview • As usual lots of candidates chose not hand in their work by the given deadline.. Some were given extensions if they were not quite finished as we jabe a little leeway this year • Most of the work handed in this year was complete and of a good standard showing commitment and hard work – those candidates will be rewarded. • At time of writing (06th January) 5 candidates had still not uploaded their websites – why??? • Folders were excessively bulky this year due to the volume of testing.

5. Task A and B • Both these tasks were marked ages ago and feedback received thank you to those who bothered to make adjustments some didn’t… • Ensure you have evidence to complete task b of: • A site index • Evidence of uploading and your site is actually published online – this was missing from many portfolios • Screen shots of the upload process, then a screen shot of your website showing the www.etc is appropriate.

6. Task Ci • Your finished website needs to have used a wide range of techniques and features to create a website of professional standard. • CSS, Javascript, CGI/ASP, Flash, templates, animated gifs, rollovers, time/date, multimedia will be included. • Annotation of website screen shots needs to identify the features used (especially sound, flash, rollovers and dropdown) as its not always obvious what they are.

7. Task Cii • Tables are a good way of explaining the features used and how they add impact BUT often no evidence was inlcuded and entries became generic • HYPERLINKS is not good enough – need to tell me hyperlink to what….. And show me a picture of it • Some people included step by step on how things were made – not necessary but still was good evidence for this task • Most people forgot to include: • ASP, DATABASE, VALIDATION, TEMPLATE and DROP DOWN MENUs within their features

8. Task D • The code annotation was poor – you must explain fully 3 TAGS • highlighting bits of CSS or JavaScript is not appropriate • the html, head and body tag are not good selections either • Highlighting only the close part of the tag is again not good • Select three tags and explain exactly what they do and when they close (include all the properties of the tag) – a table and all its associated tags (tr, td etc) would be good, image tag and its properties, hyperlink tag and all its properties • Use the notes from the HTML lecture or an online resource to help • Remember to edit as well as add html code and don’t try to blag it – Dreamweaver writes code which you haven't been taught and I can tell

9. Task E • Very extensive by most people • Ensure you have clear evidence of testing – a table is not always sufficient on its own. The inclusion of screen shots within your test table will make testing more overt rather than implied. • Include clear evidence of testing within two different browsers: • Rollovers • Validation • Database connection (see www.computechedu.co.uk/resources/agce/G053/general/testingProcessASP.pdf)

10. Task F (1) • You need to provide a detailed and critical analysis of each page of your website and the components within them, as well as the website as a whole. • Explain why each component was used and whether it worked well or not. • Incorporate comments from visitors into analysis – (graphs are good at showing this and include questionnaires as appendices). • Suggest possible improvements that could be made to the site, justifying these in terms of the identified weaknesses and visitor feedback.

11. Task F (2) • A detailed and critical analysis of what worked well and what did not work well in terms of the tools, techniques and methods they used when designing, implementing and testing your website. • You will use the identified weaknesses in the methods used to suggest ways in which you could improve the website production process if you were to attempt a similar task in the future.

12. Task F (3) These questions may help with the second part… • What worked well in the way you implemented your project? • What did not go well in the implementation of your project? • What have you learnt about the process of implementing a project? • Did you take account of problems and revise your methods accordingly? • Were tasks completed in the correct order? • How would you overcome any weaknesses in your implementation you have identified? • How would this make things better? • For MB3 there must be a clear link between the weaknesses which you have identified and the improvements which can be made.