User Modeling
CS408 Human Computer Interaction Lecture 22 provides an exhaustive, authoritative examination of user modeling and Alan Cooper's persona methodology, serving as a cornerstone of the Virtual University interaction design syllabus. Modeling bridges qualitative ethnographic research and concrete interface architecture by structuring raw, unstructured observational data into precise descriptive representations. Without user models, engineering teams drown in fragmented interview transcripts, lacking an organizing principle to determine system behavior. Alan Cooper introduced personas as composite user archetypes synthesized from behavioral patterns observed across actual field subjects. Though fictional individuals with specific names, demographics, and lifestyles, personas represent real behavioral clusters and authentic human motivations. The lecture emphasizes that personas are archetypes, not stereotypes; while stereotypes stem from designer biases and cultural prejudices, valid personas derive strictly from rigorous empirical field data. Personas fundamentally resolve three debilitating software design traps: the elastic user, self-referential design, and designing for edge cases. The elastic user phenomenon occurs when developers subconsciously bend user capabilities to match programming convenience, assuming a novice when justifying clumsy wizards but expecting an expert when omitting explanatory cues. Self-referential design arises when engineers project their own cognitive styles, technical dexterity, and mental models onto end-users. Designing for edge cases leads teams to waste excessive resources catering to bizarre scenarios at the expense of mainstream usability. Personas also differ fundamentally from user roles, generic user profiles, and marketing segments, because personas capture contextual behaviors, goals, and mental models rather than mere demographic buying power. A central contribution of the module is Cooper's goal taxonomy, which categorizes human motivation into three tiers: Life Goals, Experience Goals, and End Goals. Life Goals represent deep personal aspirations and self-identity, such as living a fulfilling life or maintaining professional integrity; while rarely dictating specific interface widgets, they inspire long-term product loyalty. Experience Goals express how a user desires to feel while interacting with the software—such as feeling competent, smart, and never feeling stupid or humiliated; these universal goals dictate software etiquette, responsiveness, and considerate behavior. End Goals represent tangible, task-oriented outcomes, such as processing a sales invoice or booking a flight; they directly shape functional requirements and interaction frameworks. The lecture delineates the systematic seven-step persona construction process: identifying behavioral variables; mapping interview subjects across continuous variable axes; discovering discrete behavioral clusters; synthesizing salient characteristics and goals; verifying narrative completeness; constructing vivid narrative walk-throughs; and designating persona types. Teams classify personas into Primary (the central design target whose needs cannot be satisfied by an interface designed for another), Secondary (accommodated with minor interface tweaks), Supplemental, Customer, Served, and Negative personas (explicitly excluded anti-targets). Mastering this user modeling framework is essential for excelling in CS408 midterm examinations, solved past papers by Moaaz, and Waqar Siddhu quiz files.
No questions available yet.
There are currently no examination questions published for User Modeling. Explore other curriculum units or build a custom quiz with the practice builder.