Prof. Janhavi N, Dept. of CSD, ATMECE JN 1 Design

Transcript:Prof. Janhavi N, Dept. of CSD, ATMECE JN 1 Design:
Prof. Janhavi N, Dept. of CSD, ATMECE JN 1 Design Processes and Perspectives – BCG602 Course Coordinator: Janhavi Nandish Assistant Professor Dept. of CSD ATMECE, Mysuru Prof. Janhavi N, Dept. of CSD, ATMECE JN 2 Module 4 : Design tools and technologies The golden rules In his book on interface design, Theo Mandel [Man97] coins three golden rules: 1. Place the user in control. 2. Reduce the user’s memory load. 3. Make the interface consistent. 1. Place the user in control. User interface design should prioritize user control, ensuring that users feel in command rather than restricted by the system. Poorly designed interfaces often force users into rigid workflows, leading to frustration and inefficiency. By following principles that empower users, software can enhance usability, efficiency, and satisfaction. Key Principles for Placing the User in Control 1. Define Interaction Modes Without Forcing Unnecessary Actions Users should be able to perform tasks without being locked into a specific mode unless necessary. Example: A word processor should allow users to correct a spelling mistake while still in spell-check mode. A photo editor should let users adjust an image without requiring multiple confirmation dialogs. 2. Provide Flexible Interaction Different users prefer different interaction styles (e.g., keyboard shortcuts, mouse clicks, touch gestures). The interface should accommodate various input methods. Example: A file explorer should allow users to drag and drop files, right-click for context menus, or use shortcut keys to move files. 3. Allow Interruptible and Undoable Actions Users should have the ability to interrupt ongoing processes (e.g., canceling a file download). A robust undo/redo system prevents irreversible mistakes. Example: A spreadsheet program should allow users to undo multiple changes rather than just the last action. 4. Streamline Interaction for Experienced Users Advanced users should be able to customize workflows and use shortcuts. Personalization options should be available without overwhelming novice users. Example: A developer’s text editor (e.g., VS Code) allows users to create macros, define custom key bindings, and install plugins. 5. Hide System Internals from Casual Users The interface should shield users from technical complexities. Error messages should be clear and actionable, avoiding technical jargon. Example: Instead of “Error 404: File Not Found”, a browser could display “The page you are looking for doesn’t exist. Try searching for it.” 6. Allow Direct Manipulation of Objects Users should be able to interact with objects directly rather than through complex commands. Example: In a graphical