软件工程视角下的用户界面设计

3星 · 超过75%的资源需积分: 10 48 浏览量更新于2024-07-29 收藏 9.82MB PDF 举报

《用户界面设计：软件工程视角》是一本由Soren Lauesen编著的专业书籍，从软件工程的角度深度探讨了用户界面设计的重要性和实践策略。该书针对全球计算机科学教育市场，汇集了顶尖作者的智慧，提供了最新、最前沿的设计思想和最佳学习方法，旨在帮助读者深入理解和应用这一领域的知识，无论是在学术研究还是实际工作中都能发挥关键作用。作为系列出版的一部分，这本书可能隶属于Addison Wesley等知名出版社，他们致力于制作高质量的纸质和电子教材，以适应不同的学习需求。通过Pearson Education Limited发行，覆盖全球多个主要城市，如英国的Harlow、伦敦、纽约等地，以及世界各地的分公司。读者可以通过访问www.pearsoned.co.uk了解完整的出版范围和更多详情。书中，作者Soren Lauesen可能系统地阐述了用户界面设计的各个方面，包括但不限于交互设计原则、用户体验（UX）设计、界面布局、响应式设计、人机交互理论等。它可能会涉及如何在软件开发过程中将用户中心的设计理念融入到产品生命周期的各个阶段，强调了设计与工程之间的紧密联系。此外，作为软件工程的一部分，书中可能还会讨论如何通过工程化的方法论进行用户界面设计，包括需求分析、原型制作、测试与迭代优化等，确保设计既满足功能需求又符合用户期待。书中可能还包含实用案例研究和最佳实践，以帮助读者提升技能并应用于实际项目中。《用户界面设计：软件工程视角》是一本深入浅出的指南，不仅适用于学生的学习，也对软件工程师、产品经理和设计师的职业发展具有指导意义。对于任何希望在用户体验领域取得突破或深化理解的人来说，这本书都是不可或缺的参考资料。

P1: FYX

PE040-FM PE040/Lauesen September 28, 2004 18:16 Char Count= 0

usability requirements, make a data model and design screens for a real-life case.

They may bring whatever books they like to the exam. Chapter 17 contains sample

exam questions.

IT-convert course. In recent years we have had many students that come from

humanities or social sciences and want to become IT professionals. This book has

worked amazingly well with this audience. The students are mature and learn fast.

They appreciate very much the real-life attitude of the whole thing, and they feel

motivated to enter also the hard technical part of the course (the Access booklet).

Courses for mature IT-students.

The book makes excellent courses for software

engineering or information systems students who know about programming and the

technical aspects of design. Parts A and B of the book are suited for such courses. If

the students have followed a traditional HCI course already, we treat part A lightly.

In these courses the data model part need not be included, and the Access booklet

might be replaced by programming the user interface for any other platform the

students might know.

Professional courses. We have used parts A and B of the book for professional

courses taking 2–3 days. The participants are systems developers and expert users

participating in development. Data modelling is not essential here; the professional

developers usually know it already, and the expert users don’t have to learn it when

they cooperate with developers. Actually, we invented the novel parts of the book

through such courses. We observed that some professional design teams produced

excellent user interfaces, while others ended up with a messy interface that users

found hard to use and understand. By comparing their work, we learned the cause of

these differences and used it to improve the systematic design approach.

Course material

Overheads corresponding to all the ﬁgures of the book, and solutions to most of the

exercises, are available for teachers. See www.booksites.net/lauesen or e-mail the

author at slauesen@itu.dk.

The Access booklet is free for download from www.booksites.net/lauesen. The

package includes a handy reference card for Access and Visual Basic, plus the hotel

system application in various stages of completeness corresponding to the exercises

in the Access booklet.

The author’s background

At the age of 19, I started to work in the software industry for the Danish computer

manufacturer Regnecentralen. At that time user interfaces were extremely primitive.

We fed data into the system through punched cards or paper tape, and output was

printed reports. When we later began to talk about on-line computing, input/output

............................................................................................................................................................................................................................................................................................................

Preface

P1: FYX

PE040-FM PE040/Lauesen September 28, 2004 18:16 Char Count= 0

was through typewriter-like equipment. Renting a computer for an hour cost the

same as paying someone to work for 30 hours; and computers were 5000 times

slower than they are today.

Nobody thought of usability. The customer paid until he had a program that printed

results he could use with some effort. Everything to do with computers was a

specialist’s job.

My ﬁrst project in 1962 was to develop a program that made the computer play a

game invented by the Danish poet and designer Piet Hein. Neither he nor anybody

else knew how to win the game. I had never programmed before, so I had to learn

that too. And of course I didn’t know that it was difﬁcult to make such a program, so

it took me a couple of weeks to solve the problem. Piet Hein wanted to have people

play the game against the computer at exhibitions, but how could the user interact

with the computer? Our hardware developers found a way to connect a bunch of

buttons and lamps directly to the multiplier register of the CPU, and I made the

program without multiplying anything. We then designed a nice user interface that

people could use immediately. I didn’t realize that this was the only good user

interface I would make until 1973.

In the period until 1973, I developed many kinds of systems, for instance

computation of molecule shapes based on X-ray diffraction, administration of

pension contributions, optimization of tram schedules and rosters. Later I moved to

another department in the company, where we developed compilers and operating

systems. These systems became extremely fast, compact and reliable technical

wonders. It took me many years to realize that we had made these miracles without

understanding that the customers had other interests than speed and reliability. They

also wanted usability – efﬁcient task support – which we didn’t provide and didn’t

understand.

In 1973, I moved to Brown Boveri, now part of ABB (Asea Brown Boveri). We were a

new department and our ﬁrst project was to develop a new line of process control

systems with colour screens and special-purpose keyboards that could be operated

by users with big, insulating gloves. Our ﬁrst delivery was power distribution

control for a part of Denmark. We knew how to make reliable, fast and compact code,

but this was the ﬁrst time I realized that ease of use was also important. If our system

failed technically, 300,000 people wouldn’t have power. But if the user couldn’t ﬁgure

out how to operate the system, the consequences might be the same. I had never

been involved in anything as serious before. We made it, and usability became very

good because we were inspired by the way users had controlled the power

before.

In 1974–1975, I took temporary leave from Brown Boveri and worked for ILO in

Ghana, helping with management consultancy in IT issues. This was the most

fascinating year of my life. I learned how different other cultures and value systems

could be, and that our own society had gained much in economic welfare and

security, but lost a lot in other aspects of life quality. I also learned that I didn’t know

xvi

Preface

P1: FYX

PE040-FM PE040/Lauesen September 28, 2004 18:16 Char Count= 0

anything about management and that such knowledge was important. Returning

home, I took a business diploma as fast as possible.

In 1979–1984, I moved to a new software division established by NCR in

Copenhagen. For some reason I became a manager, but kept being involved in

software development – even on the programming level. I soon got two management

responsibilities: (1) developing experimental technology for the next generation of

products, and (2) assuring that the rest of the division delivered adequate quality in

the present products. My main lesson in these years was that there was a very, very

long way from proving a new technology to having a multinational company accept

it for new products.

Now, where did I learn about usability? Not in industry! In 1984, I became a full

professor at the Copenhagen Business School. They had decided to establish a new

degree program – Business and Software Engineering. I found it an excellent idea

since I had seen so many bright IT people who didn’t understand business; and I had

seen so many excellent managers who didn’t understand technology. There was a

communication gap, and educating young people in both areas at the same time

seemed a great idea. I was willing to take responsibility for the IT side of the new

education.

Working here without the daily pressure of ﬁnishing new products gave me time to

wonder why the users and customers of all the technical wonders we had made over

the years didn’t like our systems as much as we did ourselves. I started to study

usability and wondered whether users tried to understand what the computer did, or

whether they just thought of carrying out their tasks, as most researchers assumed.

I ran several experiments and concluded that if the system has a certain complexity,

users form a mental model of how it works. They do so unconsciously, and often

their model doesn’t match with what the system actually does. This is the source

of many usability problems. (Norman, 1988, found similar results in the same

period.)

At that time, user manuals was a big issue, and I used the mental-model insights to

develop ways to write manuals that combined two things at the same time: learning

how to carry out the tasks, and understanding – at a non-technical level – what

happens in the system. The approach was quite successful, and I served as a

consultant for many technical writers and gave courses on writing user

documentation.

Later I became more interested in designing good user interfaces – where manuals

weren’t necessary. During a long cooperation with Morten Borup Harning and

varying master’s students, we developed the approach that is central to this book.

I had expected that I would return to industry after about ﬁve years, but found that

the combination of IT and business was fascinating, and that working at a business

school helped me open the doors to a wide range of companies. Gradually I became

a researcher who worked closely with industry.

Preface

xvii

P1: JYS

PE040-01 PE040/Lauesen September 29, 2004 13:43 Char Count= 0

Part A

Best of the classics

In part A of the book we look at some classical techniques in user interface

design:



How to detect what users ﬁnd difﬁcult or inconvenient when they use a

system, and how to measure the goodness of the system (Chapter 1).



How to use prototypes and iterative design to come up with a good user

interface (Chapter 2).



How users perceive the contents of a screen and how we can present data

to them (Chapter 3).



What users believe goes on in the system and how it relates to various kinds

of user interfaces (Chapter 4).

The classical approaches to user interface design are to a large extent based

on trial and error. The designers compose the user interface with their intuition

and general understanding of users, and then measure how good the user

interface is. If it isn’t satisfactory – and they have time to improve it – they revise

their design and measure once again how good it is. They will usually have to

revise the design many times to get an adequate user interface.

There is one more important classical technique: How to study and describe

the users, their tasks and the data they use. In part A of the book, we assume

that this is part of an analysis and requirements phase that precedes the user

interface design work. In part B of the book, we will expand our perspective

and treat parts of the analysis phase together with a more systematic design

approach.

Best of the classics

剩余622页未读，继续阅读

neuvincent

粉丝: 1
资源: 129

软件工程视角下的用户界面设计

数据库ion-course-desig笔记

我的封装库（ATK-OV7670摄像头模块、MP3模块、STM32芯片、MDK_Kei等）altium Desig（AD）封装库

读书笔记：基于环信sdk开发的即时通讯聊天客户端使用了mvp架构设计全局material desig实现.zip

vue2.0如何使用 Ant Desig 的 table

Modern C++ Design Generic Programming and Desig

_This_course_gives_an_introduction_to_digital_desig_FPGA-Design-

API 686 Recommended Practice for Machinery Installation and Installation Desig

Altium Designer 教程

Altium Designer License Generator.zip_AD LicenseGen_Altium Desig

Open Radio Access Network (O-RAN) Systems Architecture and Desig

最新资源