HCI Process and Models

Welcome to CS408 Human Computer Interaction Lecture 16 on HCI Process and Models at Virtual University. This comprehensive educational guide investigates the systemic software engineering crisis and establishes the commercial justification for integrating user-centered design methodologies into digital product development. Emphasizing the adage that 'to err is human, to really screw up requires a computer,' the lecture contrasts mechanical manufacturing waste with catastrophic software failures that bankrupt entire enterprises, citing the high-profile collapse of Boo.com. Students examine startling empirical research documenting the usability crisis: Jared Spool's finding that web users locate information only 42% of the time, Zona Research's evidence that 62% of shoppers abandon e-commerce sites, and Forrester Research's data showing 50% of online sales are lost due to unfindable products while 40% of users never return after a frustrating experience. Crucially, IEEE Software reveals that 80% of software lifecycle costs occur post-release during maintenance, with 80% of that effort driven by unmet user requirements rather than technical bugs. Furthermore, ACM studies indicate 63% of software projects exceed cost estimates due to frequent change requests and poor user-analyst communication. The lecture demonstrates that software quality demands not only functionality and reliability, but also efficiency, maintainability, portability, and usability. Usability is analyzed across both strategic dimensions (interaction idioms and mental models) and tactical dimensions (control widgets and dialog design). Students explore the inherent conflict of interest when programmers design software: judged by code efficiency and strict delivery deadlines, developers naturally build implementation-centric systems and cannot simultaneously advocate for end users. The chapter refutes the common fallacy of treating users as designers, noting that domain knowledge differs fundamentally from interaction design expertise. Tracing the evolution of software development from early coder-centric models and managerial feature checklists to separate testing disciplines, the curriculum introduces Alan Cooper's Goal-Directed Design principle: design must precede programming. Grounded in Victor Papanek's definition of design as the conscious effort to impose meaningful order, the lecture explores the three dimensions of design—form, meaning, and behavior—establishing interaction design as the discipline that shapes dynamic artifact behavior. For VU students preparing for examinations, reviewing CS408 solved MCQs, handouts, and Moaaz past papers ensures mastery of these vital software lifecycle concepts.