Creating Effective GUI Rules for Client Meetings
Develop minimalist and consistent GUI rules for client meetings to ensure a modern and user-friendly design approach. Form a cross-team collaboration to establish rules and present paper prototypes to the client for feedback.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Left What the client likely doesn t want something that looks really old-fashioned. The GUI Challenge CSSE 371, Fall, 2013 What to do for the client meeting Week 4
Last Friday, you showed 5 GUIs Your client liked them But, how do you decide what the overall rules of the GUI will be. For now, make these minimalist rules. But also try for consistency. Assume we ll change it all later! Right Something else they may not want a GUI that assumes you are familiar with something unrelated.
The method Like last week, let s form a cross-team team New people, this time They will create a set of rules by tomorrow night, and post these on Google Groups. Sound doable? Then everyone will try to follow these for this coming Friday s client meeting. What kind of prototype will we do this week?
The GUI prototype A paper prototype of your part of the system, from each team. You ll take turns showing this to the client, on Friday. It should allow you to step through all your team s key use cases with them. The Friday meeting will have to be efficient, because it covers more territory.
This is described in ID book, Ch 11 See pp 423-425. The YouTube video at https://www.youtube.com/watch?v=GrV2SZu RPv0 is really good! Shows how fast you can go through it, guiding the client through the steps. How many of these would you need for your part of the system?
