Notes on User Interface and System Design

1.1 Introduction
  • Overview: This chapter discusses the importance of designing user-friendly interfaces for effective communication between users and computers in the ICT field.
  • Goals: To empower users to create digital experiences that are efficient and enjoyable.
1.2 User and System Interfaces
  • Definition of System: A system consists of multiple components working towards a common goal, especially within the context of ICT.
  • Software Types:
    • Systems Software: It provides a platform for other software to run, acting as a bridge between the user and computer hardware. Key function: Managing hardware resources.
      • Examples: Operating Systems (Windows, macOS, Linux), Device Drivers.
    • Applications Software: Designed for specific user tasks or problems, focused on user needs.
      • Examples: Word processing (Microsoft Word), Graphic Design (Adobe Photoshop), Web Browsers (Google Chrome).
  • Key Differences: Systems software is system-oriented, while applications software is user-oriented.
1.3 Interaction and User Interfaces
  • Types of Interfaces:
    • System Interfaces: Require minimal human involvement (e.g., data processing from scanners).
    • User Interfaces: Focus on user interactions; need to be tailored for internal vs. external users.
  • Design Considerations: User interfaces must be designed for the specific needs of the user group, whether internal (e.g., employees) or external (e.g., customers).
1.4 Understanding User Interfaces
  • User-Centered Design (UCD):
    • Principles:
    • Focus on users early in design.
    • Evaluate designs for usability.
    • Utilize iterative development for constant improvement.
    • Importance: The user's perspective is critical in ensuring that the interface meets their needs and expectations.
1.5 User Interface Design Concepts
  • Key Guidelines:
    • Metaphors: Familiar analogies to aid user understanding.
    • Affordance: Controls should imply their function.
    • Consistency: Design should be uniform in appearance and behavior.
    • Feedback: Provide responses to user actions.
    • Dialogs: Structure interactions clearly with a recognizable flow.
    • Error Handling: Provide clear error messages and guidance for correction.
    • Easy Reversal: Users should be able to undo actions easily.
    • Short-term Memory Load: Minimize cognitive load through design.
1.6 Transition from Analysis to User Interface Design
  • Use Cases: Direct user interactions shape dialog design.
  • Design Approach: Decisions can follow a top-down or bottom-up approach.
  • Dialogs and Storyboarding: Visual tools to map user interactions and facilitate feedback on concepts.
1.7 Designing System Interfaces
  • System Interfaces: Include all aspects of automated data processing with minimal human intervention.
  • Input Types: Includes automated devices (e.g., barcode scanners) and electronic data interchange (EDI).
  • Challenges of EDI: Complexity in defining transaction formats and ensuring compatibility across systems.
1.8 Designing System Inputs
  • Input Design Focus: Identifying devices, mechanisms, and strategies for error reduction.
  • Automated Input Devices: Aim to minimize human error through electronic input methods.
  • Error Reduction Principles: Focus on mechanisms to avoid input mistakes and streamline the data entry process.
1.9 Designing System Outputs
  • Output Design Tasks: Identify output types, layout, and necessary safeguards for information security.
  • Types of Output Reports: Detailed, summary, exception, and executive reports, each serving different organizational needs.
  • Internal vs External Outputs: Recognizing the distinction is crucial for design.
1.10 Conclusion
  • Interface Types: User vs. System Interfaces encompass a variety of interaction elements.
  • Design Process: Involves thorough planning for both inputs and outputs, accounting for user engagement.
  • Lesson Learned: A user-centric approach is essential for developing effective interfaces across all types of systems.