In this lesson, you will learn how to test and evaluate your project, document your work, and prepare for presentation.

You'll also get guidance on report structure, including the design process and ethics, plus tips for presentations. Activities include debugging, peer review, and uploading to a digital portfolio. By the end, you'll have a self-assessment rubric to review your work. It should take about 240 minutes over several sessions. Work at your own pace, and remember to collaborate with your team where needed.

Now that you've built your frontend, it's crucial to test it for usability. This means checking how easy and enjoyable it is for others to use. Usability testing helps identify any issues early, ensuring your interactive information system is user-friendly, creative, and functional. You'll ask peers to try it out and gather their feedback, then make improvements based on what you learn.

Why Usability Testing Matters: It simulates real users interacting with your system, revealing problems you might not notice yourself, like confusing navigation or slow-loading elements. This step aligns with good UI principles by focusing on accessibility, simplicity, and engagement.

Testing Steps:

• Prepare Your Test: Set up your frontend on a device or share a link if it's hosted. Create a list of tasks for testers, such as 'Search for a book' or 'Add an item to a list', based on your system's features.
• Check Responsiveness: Test how your site looks and works on different devices, like mobiles, tablets, and desktops. Resize your browser window or use developer tools to simulate various screen sizes.
• Verify Interactivity: Ensure all interactive elements, like buttons, forms, and dynamic updates, work without errors. Click through everything yourself first to catch obvious bugs.
• Gather Feedback: Ask at least two peers (classmates or friends) to use your system while you observe. Have them think aloud about what they're doing and any difficulties. Afterwards, ask questions like: 'Was it easy to navigate?', 'Did the design feel creative and engaging?', 'What would you improve?' Focus on ease of use, creativity, and functionality.
• Analyse and Iterate: Note down all feedback, positive and negative. Prioritise fixes, such as adjusting layouts for better responsiveness or adding clearer instructions. Make changes to your HTML, CSS, or JavaScript, then retest if needed.

Peer review involves getting feedback from classmates to improve your project. By sharing your work and incorporating suggestions, you'll enhance usability, address ethical concerns, and boost creativity in your interactive information system.

Why Peer Review Matters: It provides fresh perspectives on your project, helping identify issues like confusing interfaces or overlooked ethical problems that you might miss. This collaborative process encourages iterative improvements, ensuring your system is functional, user-friendly, and aligned with best practices in design and ethics.

Peer Review Steps:

• Prepare Your System: Ensure your interactive information system is ready for testing, with all features integrated (database, backend, frontend). Share access via a link or demo setup.
• Select Reviewers: Choose 2-3 peers (classmates or team members) to review your project. Explain the purpose and provide any necessary instructions.
• Conduct the Review: Ask them to test key features, noting strengths and weaknesses. Encourage them to focus on usability (e.g., ease of navigation), ethics (e.g., data privacy), and creativity (e.g., engaging design elements).
• Gather Feedback: Observe their interactions and have them provide input on specific aspects, such as intuitive interfaces or potential ethical issues.
• Analyse and Iterate: Review all feedback, prioritise changes, and apply iterative problem-solving to make improvements, such as refining UI elements or enhancing data security.

Documenting your project in a structured report is essential for communicating your work effectively. This emphasises ethical considerations in your interactive information system.

Why Report Structure Matters: A well-structured report demonstrates your understanding of the project, from planning to implementation, and highlights how you've addressed ethics like data privacy and accessibility. It helps evaluators see your problem-solving skills, creativity, and adherence to best practices, making your work more professional and comprehensive.

Report Structure Steps:

• Introduction: Provide a project overview and identify user needs.
• Design Process: Detail your planning, including database building, backend and frontend development. Reference concepts from the Algorithms and Pseudocode unit.
• Implementation: Include code snippets and explanations of how features were built.
• Testing and Evaluation: Describe the tests conducted and results obtained.
• Ethics: Discuss issues such as data protection, accessibility, and societal impacts, drawing from the Networking and Society unit.
• Conclusion: Reflect on your work and suggest future improvements.

Presenting your project effectively showcases your interactive information system, highlighting your design process, problem-solving skills, and ethical considerations. This helps you articulate your work clearly and confidently.

Why Presentation Matters: A strong presentation demonstrates your understanding of the project, from concept to completion, and allows you to explain how you've incorporated ethics, creativity, and iterative improvements. It engages your audience, whether peers or evaluators, and reinforces your ability to communicate technical ideas in an accessible way, making your project stand out.

Presentation Preparation Steps:

• Plan Your Content: Outline the key sections: introduction to the project, design process (including database, backend, and frontend), implementation details, testing results, and ethical discussions (e.g., data privacy).
• Create Visual Aids: Design slides with diagrams, screenshots, and minimal text. Use tools like Google Slides to illustrate system architecture or user flows.
• Highlight Key Elements: Emphasise problem-solving (e.g., using heuristics for debugging), creativity in UI design, and how your system addresses user needs ethically.
• Practice Delivery: Rehearse multiple times, timing yourself to fit 5-10 minutes. Practice speaking clearly, making eye contact, and handling potential questions.
• Engage Your Audience: Start with a hook like a live demo, and end with reflections on challenges overcome and future improvements.