ICTWEB513 Student Assessment Pack(1)

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Assessment Cover Sheet Please complete cover sheet clearly and accurately for assessment tasks and other types of evidence you submit for your course. All student assessment tasks submissions including any associated checklists where applicable, are to be attached to this cover sheet. Student Use Student ID No NTCA230483 Student Name Mandeep Kaur Unit Code ICTWEB513 Unit Title Build a dynamic website Assessment No. 1 Assessment Method Written Assessment  Initial Submission  Re-Submission Student Declaration I declare that:  These tasks are my own work.  None of this work has been completed by any other person  These tasks are not plagiarised or colluded with any other student/s.  I have correctly referenced all resources and reference texts throughout these assessment tasks.  I have read and understood NTCA’s policy on Plagiarism, cheating and collusion and understand that if I am found to be in breach of this policy, disciplinary action may be taken against me by NTCA.  I have a copy of my assessment work with me, which I can produce if the original is lost. Student Signature: Mandeep Kaur Submission Date: Assessor Use Only Outcome Satisfactory / Not Satisfactory Assessor Feedback: Assessor Name: Signature: Date: Student Submission Receipt: Your submission has been received. Please keep a copy of this record. Student ID & Name : ………………………………………. Submission Date: ………………..………………………………………………… Unit Code : …………………………… Assessment No & Method: ……………………………………..……………………………………..  Initial Submission  Re-Submission Received By (Name): ………………………………..…. Signature: ………………………….. Date: …………………………………. The results will be updated within twenty-one (21) days from your final submission . Please check your student portal regularly to make sure that your results are updated. If there are any discrepancies, please discuss with the Trainer/Student Support Officer. Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 3 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: 7.2. Describe the principal steps in the design phase. Explain each principal step in 40-90 words. Ans. Principal Steps in the Design Phase : The steps include conceptual design, architectural design, interface design, and database and data structure design. They focus on how the system will work internally and how it will interact with users and other systems. Question 8: Explain purpose of each of the following website elements, to ensure content is logical and accessible to the user, using one to two sentences. Elements Purpose Titles Serve as a brief and clear descriptor of the webpage content. Headings Organize content hierarchically and guide the reader through the document. Horizontal rules Visually separate content for better readability and structure. Paragraphs Group related sentences together, presenting one cohesive idea at a time. Lists Break down information into easily digestible points. Page length Ensures content is comprehensive yet not overwhelming, maintaining user engagement. Information Should be relevant, accurate, and useful to the intended audience. Other Any additional elements should contribute to the site's usability and aesthetic. Question 9: Give a real-life example to explain the importance of obtaining client feedback and adjusting web applications as appropriate in 50-100 words. Ans. In web development, client feedback is crucial as it ensures the final product aligns with the client's vision and user needs. For instance, if a user finds the checkout process on an e-commerce site confusing, developers can adjust the interface based on this feedback, which can lead to improved user experience and potentially higher sales. Question 10: Write a code using HTML, CSS and Java Script to create the following one webpage for students, answering a number of multiple-choice questions with a submit button. Question 11: What are the three (3) steps required to design a user interface and production processes? Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 6 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Assessor Checklist: Assessment Task 1 -Written Assessment Questions Satisfactory Q1.  Yes  No Q2.  Yes  No Q3.  Yes  No Q4.  Yes  No Q5.  Yes  No Q6.  Yes  No Q7.  Yes  No Q8.  Yes  No Q9.  Yes  No Q10.  Yes  No Q11.  Yes  No Q12.  Yes  No Q13.  Yes  No Q14.  Yes  No Q15.  Yes  No Q16.  Yes  No Q17.  Yes  No Q18.  Yes  No Q19.  Yes  No Q20.  Yes  No Q21.  Yes  No Q22.  Yes  No Q23.  Yes  No Q24.  Yes  No Q25.  Yes  No Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 9 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Assessment Task 2 – Project Assessment task description:  You must include the following particulars in the footer section of each page of the attached sheets:  Student ID or Student Name  Unit ID or Unit Code  Course ID or Course Code  Trainer and assessor name  Page numbers  You must staple the loose sheets together along with the cover page.  You must attach the loose sheets chronologically as per the page numbers.  Correction fluid and tape are not permitted. Please do any corrections by striking through the incorrect words with one or two lines and rewriting the correct words.  This submission must be well presented and follow the guidelines and instructions provided.  One of the most important steps that you can take: proofread your project.  Report must be of 1500-1800 words in length, using 11-point font, double-spaced, and must include a cover page, table of contents, introduction, body, summary, or conclusion, and works cited.  Appropriate citations are required. Scenario: Website “We are stars”. You as a website developer need to communicate to “We are stars” management team to develop their dynamic website. The management team has a communications manager and CEO. “We are stars” is to be a free platform aims to make sure that no talent goes unnoticed. Connecting the suitable talent with the perfect casting professionals is their motto. They have a member-based subscription available at the following price:  Six months - $550 plus GST  One year - $800 plus GST  Lifetime access - $3500 plus GST They guarantee to their members that potential candidates are selected by the most suitable agencies through sourcing only the strongest talent in Australia, and abroad, and extending their directory across a diverse range of talents from acting to influencing. Although “We are stars” are an Australian-based talent management group, they also work with some of the industry’s largest companies, globally. This allows all local talent to partake in both local and international productions. “We are stars” knows no borders. They are here to assist all talent in reaching new heights and supporting them in promoting themselves…no one should go undiscovered. At “We are stars”, they recognise the importance of people, but what makes them blush more is originality and commitment. For this reason, “We are stars”, too, is committed to clients and who they represent. “We are stars” promise to their talent and casting professionals includes, but is not limited to: Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 12 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: It is a company policy that written consent is required from parents where the individual is below 18 years of age to use their name, voice, image, likeness, and any and all attributes of his/her personality, in, on or in connection with any film, audio tape, video tape, audio-visual work, photograph, illustration, animation, or broadcast, in any media or embodiment, now known or unknown, including, without limitation, all formats of computer-readable media, produced by or distribute by the company website. This requires an additional functionality to ensure privacy and consent feature for all individuals below 18 years of age registering their interests on the website. The CEO has advised you that she wants the website to be mobile-friendly and may introduce “pay-per- view” feature where short videos and documentaries of the potential talent will be available on the website as pay-per-view. The service in which viewers are required to pay a fee to watch a specific programme at the comfort of their homes. A holistic review of what is involved in building a dynamic website can be found at the website below: http://www.adobe.com/devnet/dreamweaver/application_development.html Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 15 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Summary Overall Summary - The meeting successfully gathered the project team to discuss and plan the development of the "We are Stars" website. Key topics included defining the technical requirements, outlining software design specifications, discussing the development process, and planning for testing and finalization of the web application. Decision/s –  Adoption of Linux-based hosting for the project.  Design specifications to include a detailed site map and prototype screens.  A phased testing approach, starting with internal testing, followed by user testing. Action/s if any  Detailed design specifications to be developed and reviewed in the next meeting.  Development to commence based on the agreed specifications and standards.  A testing schedule to be prepared and resources allocated accordingly. Next Meeting time/date The team will reconvene on the specified date to review the design specifications in more detail and commence the development phase. In the interim, team members will begin preliminary tasks as per their assigned responsibilities. 20 July 2023 Meeting closed at: 5.00 PM Minutes are a true and accurate record of the Approved/confirmed by whom? Chairperson Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 18 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Signature of attendee 3: Signature of attendee 4: Sukhraj Kaur Gurmeet Singh Part 1: Roleplay This is a role-play activity based on the given below scenario. You are required to play the role of website developer and two of your classmates will play the roles of a communications manager and CEO, “We are stars”. Each student will swap the roles and get the chance to perform all the three roles. Students will be assessed individually for their participation for this assessment task. Findings: Each topic should have a compilation of all requirements from the interviewees. Each finding should be associated with the interviewees and the interview dates. Requirements are mentioned below:  Every process within the system identified (as either in scope or out of scope), and each process in scope described with a standardised task-level description of how information moves between people and/or within the system.  Trigger(s) to the process, post-conditions (what is true when the process ends) and process exceptions.  Business rules that support the process documented  Actor(s) of the process (i.e., who interacts with the system?)  Data required to support the process (data attributes) identified and objects or repositories with which these are associated.  Relationships among data required in the process  Functional requirements  Non-functional requirements The roles and their responsibilities are mentioned in the scenario. You must meet the below criteria in order to successfully complete this part of the assessment. 1. Roleplay activity 1. Perform a role play to gather information from CEO and Communications manager, such as: a. introduction/summary the website: i. discussion on the objective or purpose of the system ii. a high level of a system overview of key functionality and constraints (business, technically or both; even external) Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 21 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: b. the functionality of the website including: i. the key functional requirements ii. the key non-functional requirements c. technical architecture requirements i. specific detail about the technical environment in which the software will operate. Including but not necessarily limited to compatible operating systems ii. identify all elements of the development environment including versions of software iii. identify the database to be used including version iv. outline at least one (1) technical standard that will be adhered to and why it is relevant to this website e. user interface design which must include: i. a site map or hierarchy of navigation (with breadcrumbs); explanation of how this addresses at least two (2) relevant accessibility issues ii. detail about a suitable folder structure (both logical and physical) iii. prototype/mock-up screens for the proposed system accompanied by text description that details how the design addresses business requirements and design principles f. data storage requirements i. an estimate of the data storage requirements for the system and reasoning for this estimate g. a conceptual database design (ERD) including key relationships, if any i. Any assumptions made to complete this task must be clearly stated in a separate document, titled ‘Project Assumptions’ h. every process within the system identified (as either in scope or out of scope), and each process in scope described with a standardised task- level description of how information moves between people and/or within the system. i. Trigger (s) to the process, post-conditions (what is true when the process ends) and process exceptions. j. Business rules that support the process documented k. Actor(s) of the process (i.e., who interacts with the system?) l. Data required to support the process (data attributes) identified and objects or repositories with which these are associated. m. Relationships among data required in the process Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 22 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: a. Introduction/Summary of the Website Objective/Purpose: Establish a global platform for showcasing and connecting diverse talents with casting professionals. System Overview: A dynamic, subscription-based website providing talent portfolios, integration with social media, and global talent exposure opportunities. b. Website Functionality Functional Requirements: Talent registration and profile management. Subscription models (six months, one year, lifetime access) with payment integration. Talent discovery and search features. Social media integration (initially contact list, later expanding to Google Plus, Twitter, Facebook). Non-Functional Requirements: Performance metrics (response time, throughput). Scalability for growing user base. High availability and reliability. Strong security measures for data protection. c. Technical Architecture Requirements Operating System: Discussion on selecting Linux over Windows, considering the project's need for SSH and Apache modules. Development Environment: Identification of software tools and versions required for development (e.g., web frameworks, database management systems). Database: Selection of a database system (e.g., MySQL) and its version suitable for user data and content management. Technical Standard: Adherence to web accessibility standards (e.g., WCAG) to ensure the website is accessible to a diverse range of users. e. User Interface Design Site Map/Navigation: Outline a site map with a clear hierarchy and navigation paths. Discuss how it addresses accessibility concerns. Folder Structure: Define a logical and physical structure for efficient file organization and maintenance. Mock-ups: Present prototype screens with accompanying descriptions, detailing how they align with business objectives and design principles. f. Data Storage Requirements Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 23 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Estimate and Justification: Provide an estimated figure for data storage needs, justifying the estimate based on the expected number of profiles, multimedia content, and user interaction data. g. Conceptual Database Design (ERD) Present an ERD that showcases key data relationships, focusing on user profiles, subscriptions, and content management. h. System Process Analysis Identify and describe each in-scope process, detailing standardized task-level information flow. i. Process Triggers and Conditions Document triggers for each process and the conditions signifying their completion. j. Business Rules Documentation List and explain business rules that underpin the system's functionality. k. Actor Identification Identify all actors (e.g., talents, casting professionals, admin staff) who will interact with the system. l. Data Requirements Specify data attributes required for each process and associated data repositories or objects. m. Data Relationships Describe interrelationships among the required data within the system processes. Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 24 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Part 2: Report - Business Requirements Report This part of the assessment task is in continuation of previous assessment part 1. This assessment task requires the student to write a business requirements report on the given above case scenario. The report should include the findings, issues, opportunities, and recommendations. Findings: Student must present their findings as part 1 of the assessment task. Each topic should have a compilation of all requirements from the interviewees. Each finding should be associated with the interviewees and the interview dates. Requirements are mentioned below:  Every process within the system identified (as either in scope or out of scope), and each process in scope described with a standardised task-level description of how information moves between people and/or within the system.  Trigger(s) to the process, post-conditions (what is true when the process ends) and process exceptions.  Business rules that support the process documented  Actor(s) of the process (i.e., who interacts with the system?)  Data required to support the process (data attributes) identified and objects or repositories with which these are associated.  Relationships among data required in the process  Functional requirements  Non-functional requirements Feedback: Student must collect feedback from stakeholders and make changes in the website and its applications, as appropriate. Issues: A separate list should highlight critical business issues, so that these issues can be addressed immediately. Not all business issues require a solution. Opportunities: Obvious business opportunities should also be extracted and highlighted from the findings. Again, not all business opportunities will translate into requirements. Recommendations: After analysing the findings, issues and opportunities, a list of recommendations should be added. These can be recommendations for correcting a problem on the existing systems or for building a new solution. Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 25 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: You must meet the below criteria in order to successfully complete this part of the assessment. 1. Business Requirements Report 1. Submit a Business Requirements Report; the report must meet all the requirements outlined in the scenario and include: a. the following formatting requirements: i. a table of contents ii. a footer with the page numbers iii. a header with the logo for Memos Tonight b. introduction/summary the website: i. discussion on the objective or purpose of the system ii. a high level of a system overview of key functionality and constraints (business, technically or both; even external) c. the functionality of the website including: i. the key functional requirements ii. the key non-functional requirements d. technical architecture requirements i. specific detail about the technical environment in which the software will operate. Including but not necessarily limited to compatible operating systems v. identify all elements of the development environment including versions of software vi. identify the database to be used including version vii. outline at least one (1) technical standard that will be adhered to and why it is relevant to this website n. user interface design which must include: i. a site map or hierarchy of navigation (with breadcrumbs); explanation of how this addresses at least two (2) relevant accessibility issues ii. detail about a suitable folder structure (both logical and physical) iii. prototype/mock-up screens for the proposed system accompanied by text description that details how the design addresses business requirements and design principles o. data storage requirements i. an estimate of the data storage requirements for the system and reasoning for this estimate p. a conceptual database design (ERD) including key relationships, if any i. Any assumptions made to complete this task must be clearly Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 26 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: stated in a separate document, titled ‘Project Assumptions’ q. every process within the system identified (as either in scope or out of scope), and each process in scope described with a standardised task- level description of how information moves between people and/or within the system. r. Trigger (s) to the process, post-conditions (what is true when the process ends) and process exceptions. s. Business rules that support the process documented t. Actor(s) of the process (i.e., who interacts with the system?) u. Data required to support the process (data attributes) identified and objects or repositories with which these are associated. v. Relationships among data required in the process w. Feedback: Student must collect feedback from stakeholders and make changes in the website and its applications, as appropriate. x. Issues: A separate list should highlight critical business issues y. Opportunities: Obvious business opportunities should also be extracted and highlighted from the findings. z. Recommendations: After analysing the findings, issues and opportunities, a list of recommendations should be added. Business Requirements Report for 'We are Stars' Website Table of Contents 1. Executive Summary 2. Introduction 3. Website Functionality 4. Technical Architecture Requirements 5. User Interface Design 6. Data Storage Requirements 7. Conceptual Database Design (ERD) 8. System Process Analysis 9. Feedback Integration 10. Identified Issues 11. Business Opportunities 12. Recommendations 13. Appendices 14. References 1. Executive Summary A concise overview highlighting the project's objective to create a dynamic platform that connects Australian talents with global casting professionals, offering various subscription-based memberships. 2. Introduction Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 27 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: A description of the project's purpose, to develop a website that makes talent discovery seamless and global, aligning with the motto "no talent goes unnoticed". 3. Website Functionality Detail on membership options including prices and tax (GST), the guarantee of talent selection by top agencies, and the promise of 24/7 commitment to talent and casting professionals. 4. Technical Architecture Requirements Rationale for selecting a Linux-based server environment over Windows, given the project's need for SSH access and specific Apache modules, and despite the Communication Manager’s preference for Windows. 5. User Interface Design A site map reflecting the website's navigation structure, ensuring ease of use for talents and agencies, with mock-up screens demonstrating key functionalities. 6. Data Storage Requirements Estimate of storage needs, accounting for profiles, images, videos, and a growing global user base. 7. Conceptual Database Design (ERD) An ERD that illustrates the database schema, relationships between talents, memberships, and content. 8. System Process Analysis Descriptions of system processes, including registration, talent portfolio management, subscription services, and interaction with casting professionals. 9. Feedback Integration Summary of feedback from the management team and subsequent iterations made to the system's design. 10. Identified Issues Potential scalability concerns, integration challenges with social media, and considerations for under-18 user consent. 11. Business Opportunities Opportunities for the platform to expand its reach to international markets and integrate pay-per-view features. 12. Recommendations Strategies for system enhancements and marketing initiatives to promote the platform. 13. Appendices  A. Project Assumptions  B. Stakeholder Feedback Forms  C. Mock-up Screens Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 28 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Performance Criteria/Performance Checklist Trainer/ Assessor to complete Assessment activities to be completed  Gathering information about dynamic webpage  Prepare a report of business requirements.  For a full project outline, please refer to the student assessment instructions Resources required for the unit assessment task  Unit assessment guide template  Access to live or simulated working environment  Interaction with others Does the candidate meet the following criteria Yes No Trainer/Assessor Comments Undertake a stakeholder analysis Reviewed the organisational requirements relating website Discussed the objective of website design Discussed the functionality of website including:  Functional requirements  Non-functional requirements Discussed the technical requirements (versions, database) and environment mandatory for website operation. Discussed the hierarchy of navigation, storage location and prototype of website Included the table of content, header(logo), footer in report Summarised objective and overview of functionality of website Discussed about process triggers Explained about supportive business rules in report Asked for feedback on report to adjust webpage design accordingly Prepared a list of identified issues, opportunities and recommendations. Effectively acted in roleplay with good body language including:  Voice tone  Gestures  Eye contact Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 29 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Assessment Cover Sheet Please complete cover sheet clearly and accurately for assessment tasks and other types of evidence you submit for your course. All student assessment tasks submissions including any associated checklists where applicable, are to be attached to this cover sheet. Student Use Student ID No Student Name Unit Code ICTWEB513 Unit Title Build a dynamic website Assessment No. 3 Assessment Method Project  Initial Submission  Re-Submission Student Declaration I declare that:  These tasks are my own work.  None of this work has been completed by any other person  These tasks are not plagiarised or colluded with any other student/s.  I have correctly referenced all resources and reference texts throughout these assessment tasks.  I have read and understood NTCA’s policy on Plagiarism, cheating and collusion and understand that if I am found to be in breach of this policy, disciplinary action may be taken against me by NTCA.  I have a copy of my assessment work with me, which I can produce if the original is lost. Student Signature: Submission Date: Assessor Use Only Outcome Satisfactory / Not Satisfactory Assessor Feedback: Assessor Name: Signature: Date: Student Submission Receipt: Your submission has been received. Please keep a copy of this record. Student ID & Name : ……………………………………………… Submission Date: ..…………………………..……………………… Unit Code : ……………………………………… Assessment No & Method: …………………………………….…………………………  Initial Submission  Re-Submission Received By (Name): …………………………………………. Signature: …………………………….. Date: ………………………… The results will be updated within twenty-one (21) days from your final submission . Please check your student portal regularly to make sure that your results are updated. If there are any discrepancies, please discuss with the Trainer/Student Support Officer. Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 30 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Assessment Task 3 – Project Assessment task description:  This is the third (3) assessment task you have to successfully complete to be deemed competent in this unit of competency.  This assessment task is divided into two (2) parts.  Part 1 requires you to prepare a dynamic website and relevant documentation based on the given guidelines and feedback collected as part of assessment task 1.  Part 2 requires you to test the website to ensure it meets the technical requirements.  You must create a dynamic website and relevant documentation based on the given guidelines and also test the website to ensure that it meets the technical requirements in order to successfully complete this project.  You will receive your feedback within two weeks - you will be notified by your trainer/assessor when results are available.  You must attempt all activities of the project for your trainer/assessor to assess your competency in this assessment task. Assessment part 1 Creating a dynamic website and relevant documentation You are required to prepare and submit the following as part of this assessment activity: 1. Dynamic Website 2. Testing documentation 3. Sign-off document All project items should be completed according to the following criteria: 1. Website 1. Submit the website developed to meet all the requirements outlined in the scenario as detailed in the document produced in Assessment Task 2. The website must meet the following criteria: a. General features: i. the database must be implemented as per the design, any variation from the design must be detailed including reasons for the change ii. configuration file or equivalent file must be used and must contain all database, connection and possibly session information that will need to be used for the new site Tip: Web pages may be served from a single index.php page or may use a PHP page to launch other PHP files to handle the various Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 31 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: ‘pages’ based on the URL. b. Functional requirements implementation: i. CRUD functionality must be supported ii. user inputs must be sanitised in both GETs and POSTS iii. bind values to parameters with prepared statements iv. fetched data using query or execute. With query, escape user data seen v. all empty form fields and errors communicating with the database must be handled by the web application vi. provide all key features detailed in the Business Requirements Document. 2. Testing documentation 1. Submit a document as evidence that appropriate tests have been run for the website. The document must contain the following detail: a. an overview of the testing process to be undertaken b. specific tests that address all features detailed in the Business Requirements Report including: i. at least three (3) of the security requirements being addressed at the application level c. test results for all planned tests including a minimum of ten relevant screen captures, the screen captures must include: i. at least one (1) image of an error message being captured and handled by the site ii. evidence the website was tested in a minimum of three (3) major browsers d. if errors/issues were identified; the following must be provided for each: i. a description of troubleshooting performed ii. an explanation of cause of the error/issue Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 32 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: iii. a resolution 3. Sign-off document 1. Provide a Project Signoff Sheet with appropriate detail to identify the version of the software and enable acceptance of the completed website, as tested Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 33 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Assessment Part 2 Test the website to ensure it meets the technical requirements . This activity requires the student to test the website to ensure it meets the technical requirements. Students are required to test the website according to the following guidelines: 1. Functionality: 1.1 Links Objective is to check for all the links in the website. 1.1.1 All Internal Links 1.1.2 All External Links 1.1.3 All mail to links 1.1.4 Check for orphan Pages 1.1.5 Check for Broken Links 1.2 Forms Test for the integrity of submission of all forms. 1.2.1 All Field Level Checks 1.2.2 All Field Level Validations. 1.2.3 Functionality of Create, Modify, Delete & View. 1.2.4 Handling of Wrong inputs (Both client & Server) 1.2.5 Default Values if any 1.2.6 Optional versus Mandatory fields. 1.3 Cookies Check for the cookies that have to be enabled and how it has to be expired. 1.4 Web Indexing Depending on how the site is designed using Meta tags, frames, HTML syntax, dynamically created pages, passwords or different languages, our site will be searchable in different ways. 1.4.1 Meta Tags 1.4.2 Frames 1.4.3 HTML syntax. 1.5 Database Two types of errors that may occur in Web applications: A. Data Integrity: Missing or wrong data in the table. B. Output Error: Errors in writing, editing or reading operations in the tables. Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 34 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: The issue is to test the functionality of the database, not the content and the focus here is therefore on output errors. Verify that queries, writing, retrieving or editing in the database are performed correctly. 2. Usability: 2.1 Navigation Navigation describes the way users navigate within a page, between different user interface controls (buttons, boxes, lists, windows etc.), or between pages via, e.g. links. 2.1.1 Application navigation is proper through tab 2.1.2 Navigation through Mouse 2.1.3 Main features are accessible from the main/home page. 2.1.4 Any hotkeys, control keys to access menus. 2.2 Content Correctness is whether the information is truthful or contains misinformation. The accuracy of the information is whether it is without grammatical or spelling errors. Remove irrelevant information from your site. This may otherwise cause misunderstandings or confusion. 2.2.1 Spellings and Grammars 2.2.2 Updated information 2.3 General Appearance 2.3.1 Page appearance 2.3.2 Color, font and size 2.3.3 Frames 2.3.4 Consistent design 3. Server Side Interfaces: 3.1 Server Interface 3.1.1 Verify that communication is done correctly, Web server-application server, application server- database server and vice versa. 3.1.2 Compatibility of server software, hardware, network connections. 3.1.3 Database compatibility (SQL, Oracle etc.) 3.2 External Interface (if any) 4. Client Side Compatibility: 4.1 Platform Check for the compatibility of a. Windows (Different versions – any two latest) b. Unix (different sets) c. Macintosh (If applicable) d. Linux Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 35 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: e. Solaris (If applicable) 4.2 Browsers Check for the various combinations: Internet Explorer (latest version) Google Chrome (latest version) Firefox (latest version) Browser settings (security settings, graphics, Java etc.) Frames and Cascade Stylesheets Applets, ActiveX controls, DHTML, client-side scripting HTML specifications. Graphics: Loading of images, graphics, etc., 4.3 Printing Despite the paperless society the web was to introduce, printing is done more than ever. Verify that pages are printable with considerations on: a. Text and image alignment b. Colours of text, foreground and background c. Scalability to fit paper size d. Tables and borders 5. Performance: 5.1 Connection speed a. Try with Connection speed: 14.4, 28.8, 33.6, 56.6, ISDN, cable, DSL, T1, T3 b. Time-out 5.2 Load Check/Measure the following: a. What is the estimated number of users per time period and how will it be divided over the period? b. Will there be peak loads and how will the system react? c. Can your site handle a large amount of users requesting a certain page? d. Large amount of data from users. 5.3 Stress Stress testing is done in order to actually break a site or a certain feature to determine how the system reacts. Stress tests are designed to push and test system limitations and determine whether the system recovers gracefully from crashes. Hackers often stress systems by providing loads of wrong in-data until it crash and then gain access to it during start-up. a. Typical areas to test are forms, logins or other information transaction components. b. Performance of memory, CPU, file handling etc. c. Error in software, hardware, memory errors (leakage, overwrite or pointers) Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 36 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: 5.4 Continuous use a. Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week? b. Will downtime be allowed or is that out of the question? c. Verify that the application is able to meet the requirements and does not run out of memory or disk space. 6. Security: 6.1 Valid and Invalid Login 6.2 Limit defined for the number of tries. 6.3 Can it be bypassed by typing URL to a page inside directly in the browser? 6.4 Verify Log files are maintained to store the information for traceability. 6.5 Verify encryption is done correctly if SSL is used (If applicable) 6.6 No access to edit scripts on the server without authorization. You will be assessed based upon the following performance criteria: You must meet the below criteria in order to successfully complete this part of the assessment. 1. Functionality 1.1 Links Objective is to check for all the links in the website. 1.1.1 All Internal Links 1.1.2 All External Links 1.1.3 All mail to links 1.1.4 Check for orphan Pages 1.1.5 Check for Broken Links 1.2 Forms Test for the integrity of submission of all forms. 1.2.1 All Field Level Checks 1.2.2 All Field Level Validations. 1.2.3 Functionality of Create, Modify, Delete & View. 1.2.4 Handling of Wrong inputs (Both client & Server) 1.2.5 Default Values if any 1.2.6 Optional versus Mandatory fields. 1.3 Cookies Check for the cookies that have to be enabled and how it has to be expired. 1.4 Web Indexing Depending on how the site is designed using Meta tags, frames, HTML syntax, dynamically created pages, passwords or different languages, Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 37 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: our site will be searchable in different ways. 1.4.1 Meta Tags 1.4.2 Frames 1.4.3 HTML syntax. 1.5 Database Two types of errors that may occur in Web applications: A. Data Integrity: Missing or wrong data in the table. B. Output Error: Errors in writing, editing or reading operations in the tables. The issue is to test the functionality of the database, not the content and the focus here is therefore on output errors. Verify that queries, writing, retrieving or editing in the database are performed correctly. 2. Usability 2.1 Navigation Navigation describes the way users navigate within a page, between different user interface controls (buttons, boxes, lists, windows etc.), or between pages via, e.g. links. 2.1.1 Application navigation is proper through tab 2.1.2 Navigation through Mouse 2.1.3 Main features are accessible from the main/home page. 2.1.4 Any hotkeys, control keys to access menus. 2.2 Content Correctness is whether the information is truthful or contains misinformation. The accuracy of the information is whether it is without grammatical or spelling errors. Remove irrelevant information from your site. This may otherwise cause misunderstandings or confusion. 2.2.1 Spellings and Grammars 2.2.2 Updated information 2.3 General Appearance 2.3.1 Page appearance 2.3.2 Color, font and size 2.3.3 Frames 2.3.4 Consistent design 3. Server Side Interfaces 3.1 Server Interface 3.1.1 Verify that communication is done correctly, Web Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 38 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: server-application server, application server-database server and vice versa. 3.1.2 Compatibility of server software, hardware, network connections. 3.1.3 Database compatibility (SQL, Oracle etc.) 3.2 External Interface (if any) 4. Client side compatability 4.1 Platform Check for the compatibility of a. Windows (Different versions – any two latest) b. Unix (different sets) c. Macintosh (If applicable) d. Linux e. Solaris (If applicable) 4.2 Browsers Check for the various combinations: Internet Explorer (latest version) Google Chrome (latest version) Firefox (latest version) Browser settings (security settings, graphics, Java etc.) Frames and Cascade Stylesheets Applets, ActiveX controls, DHTML, client-side scripting HTML specifications. Graphics: Loading of images, graphics, etc., 4.3 Printing Despite the paperless society the web was to introduce, printing is done more than ever. Verify that pages are printable with considerations on: a. Text and image alignment b. Colours of text, foreground and background c. Scalability to fit paper size d. Tables and borders 5. Performance 5.1 Connection speed a. Try with Connection speed: 14.4, 28.8, 33.6, 56.6, ISDN, cable, DSL, T1, T3 b. Time-out 5.2 Load Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 39 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Check/Measure the following: e. What is the estimated number of users per time period and how will it be divided over the period? f. Will there be peak loads and how will the system react? g. Can your site handle a large amount of users requesting a certain page? h. Large amount of data from users. 5.3 Stress Stress testing is done in order to actually break a site or a certain feature to determine how the system reacts. Stress tests are designed to push and test system limitations and determine whether the system recovers gracefully from crashes. Hackers often stress systems by providing loads of wrong in-data until it crash and then gain access to it during start-up. a. Typical areas to test are forms, logins or other information transaction components. b. Performance of memory, CPU, file handling etc. c. Error in software, hardware, memory errors (leakage, overwrite or pointers) 5.4 Continuous use d. Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week? e. Will downtime be allowed or is that out of the question? f. Verify that the application is able to meet the requirements and does not run out of memory or disk space. 6. Security 6.1 Valid and Invalid Login 6.2 Limit defined for the number of tries. 6.3 Can it be bypassed by typing URL to a page inside directly in the browser? 6.4 Verify Log files are maintained to store the information for traceability. 6.5 Verify encryption is done correctly if SSL is used (If applicable) 6.6 No access to edit scripts on the server without authorization. Performance Criteria/Performance Checklist Trainer/ Assessor to complete Assessment activities to be completed  Creating a website and documenting relevant information  Testing website.  For a full project outline, please refer to the student assessment instructions Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 40 of 41

Level 11, 190 Queen St, Melbourne, 3000 Tel: 03 9606 0032 | Web: Resources required for the unit assessment task  Unit assessment guide template  Access to live or simulated working environment  Interaction with others Does the candidate meet the following criteria Yes No Trainer/Assessor Comments Created a dynamic website by following the instructions given Included database information in documentation Included the configuration file with information about database, database connection in website documentation Included the functionality of website in testing documentation including:  CRUD  REST  User Input values Discussed the technical requirements (versions, database) and environment mandatory for webpage operation. Test links associated with website operations like  External and Internal Links  Mail to links  Orphan Pages  Broken Links Test web forms functionality for creating, viewing, modifying and deleting the records Test webpage with wrong inputs, default values on both server and client end Test webpage for optional and mandatory fields. Test Cookies, web indexing for website. Test Database for integrity and output errors. Test website navigation using menus, hotkeys or control keys Test website for Page appearance, Frames, Spelling and grammar Test communication of website with server software and compatibility of database Test website for various platforms, browsers Printing Test connection speed, Load, Stress and continuous use of website Verify the security of website including  Valid, Invalid login  Number of tries  Webpage bypassing  Encryption  Access to page editing scripts Document the test results Include troubleshooting steps and cause of common error in documentation Provide a Project Signoff Sheet with appropriate detail to identify the version of the software and enable acceptance of the completed website Document: ICTWEB513 Student Assessment Pack | Version: 1.1 | Page 41 of 41