The presentation should address the following aspects:

• What host server-side factors can affect the performance of the site
• What issues clients visiting the site may have
• What sort of pictures, videos and other files would be suitable for use on the site
• (and why others might not be appropriate)
• What laws and guidelines you will need to consider when developing the site and when he and his clients will be using the site;
• How the website can be protected, as client details will be entered when completing the request form
• How his system can be protected in the shop.

Prepare a presentation that provides Marcus with the answers to all these questions. If you can provide a audio transcript or notes pages for the presentation then you may not have to deliver the presentaion yourself.

Time Allowance

Marcus has arranged to visit the company in four weeks to listen to the presentation. That gives you 8 hours plus any overtime (homework) you need to do.
Grading Criteria

P5: Describe the various factors that influence the performance of a website.

Evidence for this should address: each of the file types – image files (from bitmap, vector, jpg, gif); sound files (from wav, mp3); video and animation files (from avi, swf); as well as techniques for conversion between formats. Evidence is also necessary for both user-side factors, such as modem connection speed, PC performance factors (from cache memory, process speed); and server-side factors, especially web server capacity (from available bandwidth, executions to be performed before page load).

P7: Identify the potential security issues and legal constraints involved in a particular website.

Evidence for this should address the content and pick up at least one security risk (from hacking, viruses, identity theft). It should also discuss firewalls, SSLs and passwords. It must also highlight the W3C guidelines and one law (from Data Protection Act 1998, Computer Misuse Act 1990, Health and Safety Act 1984, Copyright, Designs and Patents Act 1988). It would also be appropriate to highlight user perception, such as concerns over privacy of information or security of financial transactions.

M3: Explain techniques that can be used to minimise security risks to websites.

Evidence for this should build on that for P7, but must address ways in which the problems can be overcome, NOT just what the problems are.

D3: Compare ‘user side’ and ‘server side’ factors that can influence website performance.

Evidence for this should build on that for P5, but must compare the different issues for user and server side, e.g. efficient website but slow download speed and so on.

Submitting Your Work:

Any work you submit must be your OWN. We understand the temptation to copy and paste large amounts of text is very high – but you must not do it. Remember:

Everything must be in your own words.
You must credit those site, books and images you use as sources of information.

Make sure your name, course (including unit, assignment and task) and date of printing are included on any task you hand in. Master slides or headers and footers are a good way to achieve this if it possible.

For this task we recommend you submit a printout of the slides as a handout with two slides per sheet plus either notes pages from Powerpoint or an audio transcript.

You have 24 hours to complete this task but it WILL require lots of overtime (homework).

Grading Criteria

P1: Define the specific purpose and requirements for a website.

The evidence for this will come in the form of a detailed list of all the requirements including aspects related to the design, compliance, timescales, etc.

P2: Design a multi-page website to meet stated requirements.

The evidence for this will come in the form of at least one multi-page website design with a concept design, use of layout techniques and screen designs, mention of colour scheme and content. The learner should also mention the proposed development environment from both client and host server perspectives.

P3: Using a design, build a functional multi-page, two-way interactive website.

The evidence for this will come in the form of an observation statement from the assessor stating that the build website has been seen in action (not yet uploaded). The website should display evidence of interaction and good structure, easy navigation with the use of CSS if possible or reasons given if not.

P4: Review a website.

Using the list of objectives produced for P1, the learner can provide evidence of identifying the objectives met and those not met, stating why they are not met. It is possible to achieve this through the use of a viva and an observation record rather than making the learner produce additional written evidence (a separate observation record for this has not been supplied with the materials for this unit).

P6: Successfully upload a website to a web server.

Evidence for this can come in the form of an observation record from the assessor stating that s/he has seen the website in action on the internet. The observation record could include a review of the operations seen and results of a quick Q&A session with the learner about how and why operations were carried out.

M1: Explain the tools and techniques used in the creation of a website.

This can be evidenced on the design sheets where the learner can list what they are proposing to use and why. It will build on the evidence for P2 and perhaps P3 if the learner has not supplied quite enough design evidence.

M2: Adapt and improve the effectiveness of a website on the basis of a formal review.

Following a review with the client the learner needs to make some alteration(s) to the website – this should be done prior to the upload so that improvements can be checked out before the website becomes operational. The learner may also identify areas of their own through P4.

M4: Demonstrate that a created website meets the defined requirements and achieves the defined purpose.

The evidence to be provided here needs to be an in-depth examination of the functionality. The assessor can contribute to this following on from evidence supplied for P3. The learner can contribute to it following on from evidence provided for P4. In both instances the objectives highlighted in P1 need to be considered.

D1: Compare and evaluate two different designs created to meet a particular specification and justify the one chosen for implementation.

To even think of achieving this, the learner must produce two quite different proposals for the design using different tools and techniques. The justification for choice should be based on more than just the learner’s skills level.

D2: produce a website that is W3C compliant.

The learner or assessor can produce a list of factors that would ensure the site is compliant and check the site against this list. The learner can check which aspects are met and which not; the assessor can use the checklist when undertaking assessment for P3, M2 and M4. Some latitude ought to be allowed as it is unlikely in the time scale that a novice will be able to produce a site that is truly compliant – even professionals do not always achieve this. Learners could run their site through the W3C online checking system for some feedback.

Submitting Your Work:

Any work you submit must be your OWN. We understand the temptation to copy and paste large amounts of text is very high – but you must not do it. Remember:

Everything must be in your own words.
You must credit those site, books and images you use as sources of information.

Make sure your name, course (including unit, assignment and task) and date of printing are included on any task you hand in. Master slides or headers and footers are a good way to achieve this if it possible.

For this task we recommend you submit:

• Task 1 – email with overview and bullet point list of requirements
• Task 2 – two annotated designs and a justification of choice memo
• Task 3 – soft copy of website and observation record
• Task 4 – report and observation record
• Task 5 – website address and observation record