Page 5 of 5
Title / Create an interactive website for a stakeholder using client-side scripting
Level / 4 / Credits / 10
Purpose / People credited with this unit standard are able to: plan and design an interactive website for a stakeholder; develop a prototype and create an interactive website for a stakeholder using client side scripting; test and modify, operate and evaluate the website.
Classification / Computing > Generic Computing
Available grade / Achieved
Entry information
Recommended skills and knowledge / Unit 25657, Create a website for a stakeholder using a mark-up language, or demonstrate equivalent knowledge and skills.
Explanatory notes
1 An interactive website is one which responds to user input in different ways, depending on the nature of the input. Such response may include but is not limited to – completing and submitting an online form, accessing a menu, creating a shopping cart. For the purposes of assessment the interactive website and stakeholder must be authentic.
2 Definitions
Accessibility means the web pages are able to be opened and viewed on a variety of browsers and configured to be viewed by people with disabilities such as visual impairment.
A brief is defined as a clear description of both the desirable outcomes sought and the constraints to be met by the solution. It contains design specifications against which the success or otherwise of the website can be evaluated. The brief can be either created as part of the candidate’s employment (in the case of workplace assessment) or in response to the needs of a stakeholder.
Client-side scripting refers to computer programs on the web that are executed by running scripts on the user's web browser.
Conceptual design is a representation clearly indicative of the final product.
Data validation means data that is input by the user is checked for errors and an error message posted when errors are found. Validation may include but is not limited to – interactive or post-validation. Errors may be processed as field-by-field or batch errors.
End-user document is a short description of the purpose of the website, and instructions on how to access and navigate the website. The end-user document must use consistent font and layout, be legible, and should either avoid the use of undefined jargon or acronyms, or provide a glossary for these. The document must be saved in a format that is accessible to users.
A plan outlines how the requirements of the brief will be realised. For this unit standard, the plan is produced in conjunction with the conceptual design and will include pre-task documented components. Evidence of planning may be oral, written, and/or graphic.
Sitemap is a graphical representation of the architecture of a website that shows the relationship between pages of a website, usually in a hierarchical layout. A site map is used by search engines and users to find information in a website, and is part of the website.
3 The prototype website created in outcome 2 does not need to be fully functioning, but must be representative of the layout and design proposed within the brief and conceptual design.
4 The assessment context for this unit standard must be suitable to meet the criteria for level 4 in the NZQF Level Descriptors, which are available by searching for “level descriptors” at www.nzqa.govt.nz.
5 Legislation relevant to this unit standard may include but is not limited to the:
Copyright Act 1994;
Copyright (New Technologies) Amendment Act 2008;
Health and Safety in Employment Act 1992;
Privacy Act 1993;
Unsolicited Electronic Messages Act 2007;
and any subsequent amendments.
6 An assessment resource to support computing unit standards (levels 1 to 4) can be found on the NZQA website at www.nzqa.govt.nz/asm.
An overview of web design unit standards and comparison of requirements, and ‘The Computing Process - a clarification document’ contain further information and can be found on the NZQA website.
A reference source for web development W3Schools.com is available at http://www.w3schools.com/default.asp
Outcomes and evidence requirements
Outcome 1
Plan and design an interactive website for a stakeholder.
Evidence requirements
1.1 A brief is formulated that describes the stakeholder's requirements for the website in terms of purpose and target users.
1.2 The brief defines the design specifications to be met by the website in order to provide a solution.
Range includes but is not limited to – scripting language, enhancements, placement of media, interactivity, accessibility, navigation, data validation, data constraints.
1.3 A plan for the development of the website is produced and modified at each project milestone.
Range project milestones, resources requirements, stakeholder consultation, testing procedures, sitemap, directory structure.
1.4 A conceptual design of each page of the interactive website is produced and modified at each project milestone.
Outcome 2
Develop a prototype interactive website for the stakeholder using client-side scripting.
Evidence requirements
2.1 Model web pages are produced in accordance with the design specifications.
2.2 Website prototype is presented to stakeholder for feedback, revised if necessary and signed off in accordance with the project milestones.
Outcome 3
Create an interactive website for the stakeholder using client-side scripting.
Evidence requirements
3.1 Web pages are produced in accordance with the design specifications and coding standards.
3.2 Documents and supporting data are entered, edited, and formatted in accordance with the design specifications.
Range includes but is not limited to – elements, attributes, event handlers.
3.3 Elements that allow data to be inputted by users are added to the website and are consistent with the design specifications.
Range elements may include but are not limited to – form, input, control, button.
A minimum of two elements are required.
3.4 A customised response to data input is generated according to the design specifications.
3.5 Website navigation is consistent with the requirements of the design specifications.
Range may include but is not limited to – navigation bar, breadcrumbs, table, search engine.
Outcome 4
Test and modify the website.
Range all changes are documented.
Evidence requirements
4.1 Testing follows documented procedure contained in the plan.
4.2 Testing reviews the website for accessibility, readability, legibility, presentation, links and sequence, and accuracy, and any needed improvements are made.
4.3 Testing verifies that the website realises the design specifications.
Outcome 5
Operate and evaluate the website.
Evidence requirements
5.1 Operation of the website verifies that the website’s interactive components are functional.
5.2 Operation of the website is evaluated against the site’s ability to meet the requirements of the brief.
5.3 An evaluation report is prepared that identifies strengths and limitations of the website and recommends possible improvements for future developments.
5.4 An end-user document is created to facilitate use of the website.
Range sitemap, maintenance proposal.
Replacement information / This unit standard and unit standards 26230 and 26746 were replaced by unit standard 29812.This unit standard is expiring. Assessment against the standard must take place by the last date for assessment set out below.
Status information and last date for assessment for superseded versions
Process / Version / Date / Last Date for Assessment /Registration / 1 / 19 March 2010 / 31 December 2015
Rollover and Revision / 2 / 19 September 2013 / 31 December 2019
Review / 3 / 19 January 2017 / 31 December 2019
Consent and Moderation Requirements (CMR) reference / 0226
This CMR can be accessed at http://www.nzqa.govt.nz/framework/search/index.do.
Please note
Providers must be granted consent to assess against standards (accredited) by NZQA, before they can report credits from assessment against unit standards or deliver courses of study leading to that assessment.
Industry Training Organisations must be granted consent to assess against standards by NZQA before they can register credits from assessment against unit standards.
Providers and Industry Training Organisations, which have been granted consent and which are assessing against unit standards must engage with the moderation system that applies to those standards.
Requirements for consent to assess and an outline of the moderation system that applies to this standard are outlined in the Consent and Moderation Requirements (CMR). The CMR also includes useful information about special requirements for organisations wishing to develop education and training programmes, such as minimum qualifications for tutors and assessors, and special resource requirements.
NZQA National Qualifications ServicesSSB Code 130301 / Ó New Zealand Qualifications Authority 2017 / / New Zealand Qualifications Aut