Team Deliverable 1: Building The Skeleton Of The Website

Team Deliverable 1this Is A Bout Building The Skeleton Of The Function

Develop a functional prototype by creating the interaction flows or 'click streams' for your project. Provide your project or design brief, summarizing relevant prior material or ethnographical data if available. Conduct a context analysis to identify main themes such as user needs, utility, information goals, and desired user experiences. Generate user stories based on response categories like user experience, task types, duration, utility, information, outcomes, proto-personas, risks, and future feasibility considerations.

Discuss measures of success for your app, considering insights from your context analysis. Create a product canvas that depicts a mental model of your system; this can be visual, using diagrams, tables, or images. Develop wireframes representing your design for the semester, with accessible links for review. Conduct heuristic or UX evaluation of the prototype, summarizing issues and potential improvements. Outline an implementation plan to guide future development.

As part of your team, specify your role and contribution areas, whether as content strategist, visual designer, UX researcher, front-end developer, or interaction designer. Acknowledge shared roles and encourage team members to seek assistance when needed, leveraging diverse skills and experience.

Establish a team meeting schedule, including days, times, locations, and agenda topics such as progress updates, review of lecture materials, and collaborative work sessions. Be flexible with meeting times, allowing for asynchronous work. During meetings, collect observations from contextual enquiry, storyboards, task decisions for prototype development, heuristic analysis results, and identified areas for improvement. Share wireframes and documentation via accessible links, and prepare supporting files including ethics applications, information sheets, and presentation slides.

Paper For Above instruction

The process of building a functional prototype begins with a clear understanding of user needs and system requirements, which are derived from comprehensive contextual and ethnographical research. This foundational phase involves analyzing previous user data to identify core themes such as utility, ease of use, informational needs, and outcome expectations. These themes inform the development of user stories that capture users’ goals, tasks, and potential risks, providing a narrative framework for designing interactions.

Designing the prototype involves creating interaction flows or 'click streams' that simulate the user journey through the system. These flows must align with identified user needs and goals, ensuring a seamless experience that minimizes task complexity and enhances usability. To visualize this, wireframes serve as simplified representations of the interface, illustrating layout, functionality, and navigation. These wireframes should be accessible via shareable links for team review and iterative refinement.

Conducting heuristic or UX evaluations allows the team to identify usability issues within the prototype. Common issues may encompass unclear navigation, inconsistent interface elements, or inadequate feedback mechanisms. Summarizing these issues assists in prioritizing improvements and guiding subsequent iterations of the prototype.

An essential component of the development process is planning for future implementation. This involves assessing technical feasibility, resource requirements, and potential challenges. A well-structured implementation plan ensures that design concepts can transition smoothly into functional development, with clear milestones and responsibilities.

Team collaboration is facilitated by regular meetings, which serve to synchronize efforts, share observations, and make informed decisions based on collected data—such as storyboards, prototype evaluations, and heuristic analysis results. Clear communication and shared documentation underpin effective teamwork, leading to continuous improvement and alignment with project goals.

Finally, documenting the entire process—through wireframes, evaluation reports, and presentations—provides a comprehensive record of development, facilitating ongoing refinement. Supporting files such as ethics applications and informational materials ensure responsible and transparent design practice, positioning the project for successful future development and deployment.

References

• Cooper, A., Reimann, R., & Cronin, D. (2014). About Face: The Essentials of Interaction Design. Morgan Kaufmann.
• Baxter, G., & Sommerville, I. (2011). Socio-technical systems: From design methods to systems engineering. Interacting with Computers, 23(1), 4–17.
• Norman, D. A. (2013). The Design of Everyday Things: Revised and Expanded Edition. Basic Books.
• Rogers, Y., Sharp, H., & Preece, J. (2015). Interaction Design: Beyond Human-Computer Interaction. Wiley.
• Krug, S. (2014). Don’t Make Me Think, Revisited: A Common Sense Approach to Web Usability. New Riders.
• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design. Rockport Publishers.
• Hassenzahl, M., & Tractinsky, N. (2006). User Experience - A research agenda. Behaviour & Information Technology, 25(2), 91-97.
• Rubin, J., & Chisnell, D. (2008). Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests. Wiley.
• Morville, P., & Rosenfeld, L. (2006). Information Architecture for the World Wide Web. O'Reilly Media.
• Gulliksen, J., et al. (2003). Key principles for user-centred systems design. Behaviour & Information Technology, 22(6), 397–409.