- 浏览: 482323 次
- 性别:
- 来自: 北京
文章分类
最新评论
-
alvin198761:
renzhengzhi 写道我参与过12306余票查询系统的开 ...
别给12306 辩解了 -
renzhengzhi:
我参与过12306余票查询系统的开发,用户请求被前面3层缓存拦 ...
别给12306 辩解了 -
renzhengzhi:
写的很好。
JAVA线程dump的分析 -
liyonghui160com:
说好的附件呢
分布式服务框架 Zookeeper -- 管理分布式环境中的数据 -
ghpaas:
orbeon作为xforms标准的实现,不论其设计器还是运行时 ...
XForms 1.1 中文翻译—第1章 关于XForms标准
9 and how we measured (and continue to measure) our progress toward these goals throughout the development cycle. We set experience goals for all of the products we ship. These goals are at the product and “experience” (i.e., a meaningful unit of experience for people, not at the feature level) levels of analysis. We think about these goals in what we call a “Confidence Model.” This is a model that evaluates the product experiences across four dimensions – Useful, Usable, Desirable, and Principled. For each experience across each dimension, we have a “confidence rating” of how close we are to meeting (or exceeding) the experience goals. The dimensions of useful, usable, and desirable are common measures of experience across industries. In addition to those standards, we also evaluate our experiences in light of the Windows Experience Principles (more on these later). This is all an evolution of our process that we described in the Windows 7 Engineering Blog. When we think of experiences on these four dimensions, we have specific definitions in mind: “Useful” is the notion of value to people. We want the experiences in IE9 to help people do something they couldn’t do before, save them time, energy, and/or effort, and have things get noticeably better in a way that matters to people. “Usable” is what people typically think about when considering the “usability” of a product, site, device, etc. We measure how Usable an experience is on the standard factors – task success, time to completion, ease of use/setup, comprehension, confidence, security, etc. “Desirable” is how an experience evokes the intended emotional response and perception. We have general aspirations for any experience (e.g., love) but then choose specific emotions each experience should elicit (e.g., feelings of control, efficiency, connectedness, clean). “Principled” is how an experience expresses the Windows Experience Principles. We review each experience at regular points in the development cycle to make sure it is expressing our Principles. These principles are inspired by data, informed by our values, and tweaked by experience. They are not strict rules, but rather values we aspire to and shape all the experiences we design in our products. We first talked about our “design principles” for Windows 7 back atPDC 2008. Since then, we have evolved these into our current Experience Principles. Later in this post, we’ll cover how we used one of the principles to inform a design decision in IE9. Across those four dimensions, we set goals for each of a set of experiences. These goals have multiple inputs including previous experience research, design explorations, and technical investigations. The goals are generated, iterated on, and agreed upon by the entire engineering team. They become the team-wide agreement of “what success looks like” for an experience and the bar we all hold ourselves to. We then establish specific metrics for tracking progress toward each goal. For example, we had specific Useful goals for some of the general browsing experiences: People articulate the value of having a fast and fluid browsing experience as: Progress toward these goals is measured primarily through qualitative feedback from participants in our research labs and also through community feedback. After goals for each experience are set, we track them throughout the development cycle. For IE9, as with all our products, we used a large set of methods in our research, but there are three we rely on the most – lab studies, field research (e.g., visits to people’s homes) and usage instrumentation. Each of these methods has their own strengths and they give us different lenses to look at and understand the experiences we are building. During IE9 development, we conducted six different lab studies with about 60 different participants. These lab studies are great for understanding experiences as we moved from prototypes to working code and allowed us to control for whatever influences may bias our results. In addition to the lab studies, we also went on many site visits to people’s homes to give us a look at their experiences over time, in everyday settings (e.g., their living rooms), and produce specific examples of how people actually use our products in their lives. The insights we gained on our initial site visits in the summer of 2009 around how people were using web sites like their other applications was highly influential on our plans to build what eventually became Pinned Sites. Lastly, usage instrumentation of how people are currently using IE8 and IE7 gave us the huge datasets (tens of millions of people, hundreds of millions of sessions as Dean mentioned in his post) required to know what the common and frequent behaviors and patterns of usage are with our products. This data informed our decisions about which behaviors we optimized for in IE9. We are constantly evaluating our experiences with these methods and the team always has a pulse on if we are on the right trajectory to meet our goals. We make adjustments to our products and experiences based on our research, something we call “data-informed decision making.” As Jane described in her post, we started with three overarching goals for the experiences in Internet Explorer 9 – Sites Shine, A Natural Extension of Windows 7, and Fast, Safe, and Reliable. Throughout development, we evaluated our progress against these goals in general and specific goals for different experiences. For example, here are some of the specific Usable goals for our navigation experiences: People can get to where the way to go fast. This means people: It’s important to note that these goals are not for a specific feature. They span many features including Address bar, New Tab Page, Pinned Sites, and progress indication, because all of these contribute to the experience of navigation to sites with the browser. For the last goal of “Successfully pin sites,” we originally had problems with the design. You could pin by dragging the icon from the Address bar to the Taskbar and dragging the site from the New Tab Page, but not by dragging the tab the site was in to the Taskbar. Through our research, it became clear that this was one of the top ways people attempted to pin sites when trying the feature. This video clip shows one representative participant whose first instinct was to drag tabs to the Taskbar to pin them (you’ll also see the red dot of some eye-tracking research we were doing during that study as well): Based on this research, we knew that enabling pinning sites by dragging the tab to the Taskbar would meet people’s expectations and remove one more hurdle to people having the sites they love, need, and want at their fingertips. We then verified this decision with further research. Here is a participant pinning a site by dragging a tab to the Taskbar in a later build: Over the course of these studies, our confidence that we were on track increased as we made changes to the design and verified we were improving the experience. This occurred across most of the features of the product. This is just one example. For another example, here are some of the specific Usable goals for our fluid browsing experiences (different from the ones for the navigation experiences above): People can fluidly move among sites . This means people: For the first goal of “Successfully see sites side-by-side (with or without tabs),” we evaluated many different designs to accomplish this goal. One of the tools we used to choose the design we built is the Experience Principle of “Reduce concepts to increase confidence.” This Principle is about taking advantage of what people already know and introducing new concepts only when necessary. We try to make only meaningful distinctions among concepts that people will understand and get value from. As described in Jane’s earlier post, you can drag tabs out of Internet Explorer windows and directly Snap them to one side of the screen or the other on Windows 7. We deliberately built on what people were already using in Windows 7 and extend that experience to Internet Explorer 9. No relearning, no new concepts. People who use Windows 7 Snap already know how to use Snap with Internet Explorer 9. These are just two examples of how we set goals for experiences and then evaluate their progress on the dimensions of Useful, Usable, Desirable, and Principled. We do this for all of the experiences and products across Internet Explorer, Windows, and Windows Live. Setting goals for experiences across the four dimensions – Useful, Usable, Desirable, and Principled – and tracking our progress toward these goals across the development cycle is an important part of shipping the experiences we believe in. We hope you enjoy using IE9 beta. Please send your feedback in the comments and onConnect. Jess Holbrook http://blogs.msdn.com/b/ie/archive/2010/09/28/how-we-evaluate-the-experiences-we-engineer.aspxWhat we mean by “Useful, Usable, Desirable, and Principled”
How we set and track goals
Goals for Internet Explorer 9
User Experience Research Lead
Internet Explorer
发表评论
-
高性能、高流量Java Web站点打造的最佳实践
2013-12-24 11:23 2812从2005年-2013年,Ashwanth Fernando ... -
高性能、高流量Java Web站点打造的最佳实践
2013-12-24 11:01 4从2005年-2013年,Ashwanth ... -
20行实现javascript模板引擎
2013-12-23 10:35 150920行实现javascript模板引擎 我仍然在用Abs ... -
标题怎么办
2012-03-25 23:50 21.首先在这里 下载Selenium RC,解压到C盘。 ... -
Google Page Speed应用上线,移动设备也在支持之列
2011-04-05 21:23 855Google已经将Page Speed应用到线上,并且加强 ... -
浏览器的加载与页面性能优化
2011-02-16 11:23 1317本文将探讨浏览器渲染的loading过程,主要有2 ... -
门户网站负载均衡技术的六大新挑战
2010-12-23 11:25 995文 / 李晓栋 记得上 ... -
使用 JAWS 测试 Web 应用的技巧
2010-10-31 23:34 1633屏幕阅读器简介 屏幕阅读器(S ... -
研究显示:众多网上零售商未遵循Web优化基本准则
2010-10-26 10:25 696Web优化专家Joshua Bixby最近在博客中披露,在 ... -
Testing sites with Browser Mode vs. Doc Mode
2010-10-22 10:07 1066With site developers verifying ... -
Common Security Mistakes in Web Applications
2010-10-22 10:02 1693Web application developers toda ... -
A (somewhat) brief history of the performance landscape
2010-10-21 10:44 1712I’d like to enlist your help. ... -
Best Practices for Speeding Up Your Web Site
2010-10-20 10:40 1205Minimize HTTP Requests tag: ... -
Web Performance Optimization Use Cases – Part 1 Benchmarking
2010-10-19 14:40 939Web Performance Optimizatio ... -
Google WebP——让图片更小,让页面访问速度更快
2010-10-12 13:14 1587Google日前对外宣布了一种新的图片压缩格式WebP,可 ... -
剖析IE浏览器子系统的性能权重
2010-09-02 13:23 874最近,InfoQ中文站报道了Web 2.0应用客户端性能问 ... -
Performance: Profiling how different web sites use browser subsystems
2010-09-02 00:41 1206When we first showed IE9 at t ... -
Measuring Browser Performance: Understanding issues in benchmarking and performa
2010-09-02 00:40 945Measuring Browse ... -
Ajax应用开发:实践者指南
2010-08-10 21:13 977目前的Web应用开发基本上都是围绕富互联网应用(Rich ... -
全面提升 Web 2.0 应用程序的性能,第 3 部分: 浏览器渲染时间分析
2010-08-03 11:10 1039谁在调用运行时间最长的方法? 简化的浏览器响应时间 ...
相关推荐
labview程序代码参考学习使用,希望对你有所帮助。
毕设和企业适用springboot生鲜鲜花类及数据处理平台源码+论文+视频.zip
毕设和企业适用springboot企业数据智能分析平台类及汽车管理平台源码+论文+视频
毕设和企业适用springboot社区物业类及企业创新研发平台源码+论文+视频
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>Floating Text Example</title> <style> .floating-text { font-size: 24px; position: relative; animation: float 3s ease-in-out infinite; } @keyframes float { 0%, 100% { transform: translateY(0); } 50% { transform: translateY(-20px); } } </style> </head> <body> <div class="floating-text">Hello, I'm floating!</div> <script> document.addEventListener('DOMContentLoaded', function() {
毕设和企业适用springboot社交媒体分析平台类及智慧医疗管理平台源码+论文+视频
毕设和企业适用springboot生鲜鲜花类及餐饮管理平台源码+论文+视频
毕设和企业适用springboot人工智能客服系统类及用户行为分析平台源码+论文+视频
毕设和企业适用springboot全渠道电商平台类及个性化广告平台源码+论文+视频
毕设和企业适用springboot社交互动平台类及线上图书馆源码+论文+视频
毕设和企业适用springboot企业知识管理平台类及供应链优化平台源码+论文+视频
毕设和企业适用springboot企业健康管理平台类及数据处理平台源码+论文+视频.zip
内容概要:本文档是一份面向初学者的详细指南,重点介绍如何利用Vue.js 2.0快速创建和运行简单的Todo List应用。首先指导安装必需的Node.js、npm/yarn等环境准备,接着通过Vue CLI工具生成新的Vue项目,再详细介绍项目目录和组件的构建方式。最后提供了具体的方法实现添加和删除待办事项,并指导如何使用命令启动应用,查看结果。 适合人群:具备基础Web开发技能的前端开发新手,尤其是对Vue框架感兴趣的学习者。 使用场景及目标:作为初学者入门级的学习资料,本文档的目标是让读者能够在最短时间内掌握Vue.js的基础概念和技术栈的应用方式,以便日后可以独立地构建更加复杂的Vue应用。 其他说明:除了学习如何构建应用程序之外,本文档还涵盖了Vue的基本语法和数据绑定、事件处理机制等重要概念,对于理解Vue框架的工作原理十分有帮助。
毕设和企业适用springboot企业健康管理平台类及智能化系统源码+论文+视频.zip
毕设和企业适用springboot企业健康管理平台类及远程医疗平台源码+论文+视频.zip
毕设和企业适用springboot数据可视化类及数据智能化平台源码+论文+视频
毕设和企业适用springboot生鲜鲜花类及用户体验优化平台源码+论文+视频.zip
毕设和企业适用springboot人工智能客服系统类及虚拟银行平台源码+论文+视频
毕设和企业适用springboot社交应用平台类及云计算资源管理平台源码+论文+视频
毕设和企业适用springboot企业数据监控平台类及线上图书馆源码+论文+视频