MODULE 1 CHAPTER 1.pptx

USER INTERFACE AND USER EXPERIENCE(UI/U X) Mr Arun P Assistant Professor Department of Computer Science & Engineering Department of Computer Science & Engineering www.cambri...

USER INTERFACE AND USER EXPERIENCE(UI/U X) Mr Arun P Assistant Professor Department of Computer Science & Engineering Department of Computer Science & Engineering www.cambridge.ed u.in  MODULE 1 - SYLLABUS Introduction: Usability to user experience, Emotional impact as part of user experience, User experience needs a business case. Extracting Interaction Design Requirements: Needs & Requirements, Formal requirement extraction, Methods for requirement extraction..  CHAPTER 1 INTRODUCTION OF USER EXPERIENCE  WHAT IS UI?  User Interface.  A Bridge between a human  How people interact with being and a systems other products services.  Used in Web & Mobile Applications.  WHAT IS UX?  User Experience.  Plays a crucial role in web  What a person feels as he and mobile applications experiences a product or  A Bridge between a service. product and its targeted audience.  Important role in all kinds of marketing.  STRUCTURE OF WEBSITE LAYOUT .  What is UI? A digital medium user interacts with(usually a screen). Basically a visual element. It can be websites, Mobile interface Sketch, Experience design,Figma,Invision,Framer(TOOLS) 30/10/2014 7  USER INTERFACE It means by which the user and a computer system interact, in particular the use of input devices and software. User interface design is a subset of a field of study called human-computer interaction(HCI). Human-computer interaction is the study, planning, and design of how people and computers work together so that a person’s needs are satisfied in the most effective way.  USER INTERFACE HCI designers must consider a variety of factors: what people want and expect. what physical limitations and abilities people possess, how their perceptual and information processing systems work, and what people find enjoyable and attractive.  USABILITY TO USER EXPERIENCE  Human–computer interaction is what happens when a human user and a computer system, in the broadest sense, get together to accomplish something..  The goal of contextual inquiry is to improve work practice and construct and/or improve system designs to support it. Contextual inquiry includes both interviews of customers and users and observations of work practice occurring in its real-world context.  So usability includes characteristics such as ease of use, productivity, efficiency, effectiveness, learnability, retain ability, and user satisfaction  USABILITY TO USER EXPERIENCE  Usability is that aspect of HCI devoted to ensuring that human–computer interaction is, among other things, effective, efficient, and satisfying for the Contextual Inquiry.  Contextual inquiry is an early system or product UX lifecycle activity to gather detailed descriptions of customer or user work practice for the purpose of understanding work activities and underlying rationale.  So usability includes characteristics such as ease of use, productivity, efficiency, effectiveness, learnability, retain ability, and user satisfaction (ISO 9241-11, 1997).  EMOTIONAL IMPACT AS PART OF THE USER EXPERIENCE The emotional aspects of user experience are just what the term implies. We are talking about pleasure, fun, aesthetics, novelty, originality, sensations, and experiential features—the affective parts of interaction. In particular, it is about the emotional impact of interaction on the user.  USER EXPERIENCE NEEDS A BUSINESS CASE Ingenious by design; hassle-free connectivity Is the Fuss over Usability or User Experience Real? As practitioners in this field, one of the frequent challenges we face is getting buy-in toward user experience processes from upper management and business stakeholders. So what is the business case for UX? That computer software of all kinds is in need of better design, including better user interaction design, is indisputable EXTRACTING INTERACTION DESIGN REQUIREMENTS  Extracting interaction requirements, within understanding user work and needs in the context of the overall Wheel lifecycle template. We now are going to attempt to identify the needs and design requirements for a proposed new system to optimize, support, and facilitate work in that domain. It is now our job to comb through the WAAD and any preliminary design-informing models, such as the flow model, and deductively extract those user needs and requirements and thereby construct the first span of the bridge.  NEEDS AND REQUIREMENTS: FIRST SPAN OF THE BRIDGE What Are “Requirements”? Almost everyone understands the basic meaning. The term refers to a statement of what is needed to design a system that will fulfill user and customer goals. But when you start getting specific everyone In the UX domain, interaction design requirements describe what is required to support user or customer work activity needs To that end we are also concerned with functional requirements to ensure the usefulness component of the user experience  NEEDS AND REQUIREMENTS: FIRST SPAN OF THE BRIDGE Requirements “Specifications” Before we get into extracting requirements from contextual data, let us look briefly at the forms interaction design requirements can take. One term we often think of when coupled with “requirements” is “specifications.” In past software engineering traditions, a formal written requirements document was be regular and could even designate details about how the corresponding software is to be implemented, including such software stuff as  NEEDS AND REQUIREMENTS: FIRST SPAN OF THE BRIDGE Object models, pseudo-code, use cases, and software structure. However, currently in software engineering and software requirements engineering there is an increasing recognition that: Detailed formal requirements cannot ever be complete. Detailed formal requirements cannot ever be 100% correct. Detailed formal requirements cannot be prevented from changing throughout the lifecycle.  FORMAL REQUIREMENTS EXTRACTION This process of extracting needs and requirements is similar to data interpretation and consolidation sessions of contextual analysis in that it involves a group sitting down together and going over a large amount of data, including the WAAD and evolving design-informing models. But here it is actually easier because much of the hard work is already done.