itec 80
🇬🇧
In Inglés
In Inglés
Practique preguntas conocidas
Manténgase al día con sus preguntas pendientes
Completa 5 preguntas para habilitar la práctica
Exámenes
Examen: pon a prueba tus habilidades
Pon a prueba tus habilidades en el modo de examen
Aprenda nuevas preguntas
Modos dinámicos
InteligenteMezcla inteligente de todos los modos
PersonalizadoUtilice la configuración para ponderar los modos dinámicos
Modo manual [beta]
Seleccione sus propios tipos de preguntas y respuestas
Otros modos disponibles
Aprende con fichas
Completa la oración
Escuchar y deletrearOrtografía: escribe lo que escuchas
Expresión oralResponde con voz
Expresión oral y comprensión auditivaPractica la pronunciación
EscrituraModo de solo escritura
itec 80 - Marcador
itec 80 - Detalles
Niveles:
Preguntas:
88 preguntas
| 🇬🇧 | 🇬🇧 |
| When the model changes, the view is notified and updates its display to reflect the changes. | View Update |
| Types and number of people evaluating, how formal the evaluation is, and where the evaluation takes place. | Factors in Evaluation |
| Things should be placed where you'd expect them to be | Intuitive Layout |
| Effective Feedback | Visual Cues Audio Signals Haptic Feedback |
| Buttons and menus should be easy to understand. | Clear and Simple |
| Things should be placed where you'd expect them to be | Intuitive Layout |
| Similar elements should look and behave the same way throughout the app or website. | Consistent Design |
| User-Friendly Interface | Clear and Simple Intuitive Layout Consistent Design |
| Effective Feedback | Visual Cues Audio Signals Haptic Feedback |
| Efficient Interaction | Quick Response Times Minimal Effort Easy Navigation |
| The technology should respond promptly to user input. | Quick Response Times |
| Error Prevention and Recovery | Clear Error Messages Undo/Redo Functionality Input Validation Contextual Help |
| When errors occur, provide informative and actionable error messages. | Clear Error Messages |
| Allow users to reverse actions and recover from mistakes. | Undo/Redo Functionality |
| Prevent invalid input by providing real-time feedback or blocking incorrect entries. | Input Validation |
| Why Good HCI Design matters? | Enhanced User Experience Increased Productivity Improved Accessibility |
| How to evaluate HCI Design? | Is it easy to understand? Is it easy to navigate? Does it respond quickly to my actions? Does it look visually appealing? |
| Touching an app icon, scrolling through your social media feed, and typing a message are all interactions made possible by the Ul layer. | Using Smartphone |
| Clicking on links, filling out online forms, and watching videos involve various Ul elements and event handling behind the scenes. | Browsing the Internet |
| Game controllers, on-screen buttons, and visual feedback are all part of the Ul layer that creates an interactive gaming experience. | Playing Video Games |
| Even modern cars utilize Ul principles in their dashboards, navigation systems, touchscreens. and | Driving a Car |
| Key Roles of the UI Layer | Handling Input and Output Event-Driven Architecture UI Objects and Event Handlers Window Manager |
| Examples of Events in User Interface Layer | Mouse Events Keyboard Events Window Events Touch Events Other Events |
| Happens when a mouse button is pressed and released twice in quick succession over a Ul object. | Double-click |
| These events detect when the mouse cursor moves into or out of a specific Ul object, like hovering over a button or leaving a window. | Mouse Enter/Exit |
| These events are triggered by specific combinations of keys pressed simultaneously, like Ctrl+C for copying text or Alt+Tab for switching between windows. | Keyboard Shortcuts |
| Happens when a user closes a window, usually by clicking the close button or using a keyboard shortcut. | Window Close |
| Involves two fingers moving closer together or farther apart on the screen, often used for zooming. | Pinch |
| Why use Frameworks? | More Organized More Flexible More Productive Easier to Maintain |
| Frameworks help manage the different parts of the program, like how it looks and how it works. | More Organized |
| Developers can build things faster because they're not starting from scratch every time. | More Productive |
| It's simpler to fix problems and update the program later on. | Easier to Maintain |
| How MVC Works Together? | User Interaction Controller's Role Model Update View Update |
| The user interacts with the view (e.g., clicks a button). | User Interaction |
| The controller receives this input and interprets it. | Controller's Role |
| When the model changes, the view is notified and updates its display to reflect the changes. | View Update |
| Why MVC is Helpful? | Separation of Concerns Flexibility Faster Development |
| Examples of ISO's | ISO 25010 ISO 9001 Android Core App Quality |
| Refers to a set of guidelines and best practices established by Google to ensure that Android apps provide a consistent, reliable, and enjoyable user experience. | Android Core App Quality: |
| What is User Interface? | It is the way a person interacts with a computer or device. It includes everything from screens and buttons to voice commands. The goal is to make these interactions as smooth and intuitive as possible. |
| How do we evaluate User Interface? | Observation Expert Heuristic Evaluation Measurement Factors in Evaluation |
| Instead of users, experts in human-computer interaction (HCI) review your interface. They use a checklist of guidelines, called heuristics, to identify potential issues. | Expert Heuristic Evaluation |
| Expert Heuristic Evaluation | Nielsen's Ten Heuristics Visibility of System Status Match Between System and the Real World |
| General principles of digital interface design based on the problems real users face when using digital systems. | Nielsen's Ten Heuristics |
| The system should always let users know what's happening. | Visibility of System Status |
| The system should use language users understand. | Match Between System and the Real World |
| Users need an easy way to undo mistakes. | User Control and Freedom |
| Things should work the same way across the interface. | Consistency and Standards |
| Design the interface to prevent mistakes. | Error Prevention |
| Make it easy for users to find options rather than having to remember them. | Recognition Rather Than Recall |
| Allow experienced users to speed up their work. | Flexibility and Efficiency of Use |
| Don't clutter the interface with unnecessary information. | Aesthetic and Minimalist Design |
| Error messages should be clear and helpful. | Help Users Recognize, Diagnose, and Recover from Errors |
| If needed, help should be easy to find and use. | Help and Documentation |
| This can include the time it takes to complete a task, how many tasks can be completed in a given time, and how many errors are made. | Quantitative Measurement |
| Gathering opinions from users using questionnaires. | Qualitative Measurement |