The document discusses the process of usability engineering and its relationship to software engineering. It describes how adding a user interface changes software development by requiring additional support areas. It then outlines the typical activities in both software engineering and usability engineering processes. The document also discusses different development team structures and the benefits of participatory design.
The document discusses the process of usability engineering and its relationship to software engineering. It describes how adding a user interface changes software development by requiring additional support areas. It then outlines the typical activities in both software engineering and usability engineering processes. The document also discusses different development team structures and the benefits of participatory design.
The document discusses the process of usability engineering and its relationship to software engineering. It describes how adding a user interface changes software development by requiring additional support areas. It then outlines the typical activities in both software engineering and usability engineering processes. The document also discusses different development team structures and the benefits of participatory design.
The document discusses the process of usability engineering and its relationship to software engineering. It describes how adding a user interface changes software development by requiring additional support areas. It then outlines the typical activities in both software engineering and usability engineering processes. The document also discusses different development team structures and the benefits of participatory design.
Download as PPT, PDF, TXT or read online from Scribd
Download as ppt, pdf, or txt
You are on page 1of 16
THE PROCESS OF USABILITY
ENGINEERING Usability Engineering: Process, Products, and Examples Chapter 4
11/28/21 Akash Deo 1
BUILDING A USER INTERFACE
Building a User Interface is part of the larger problem of building
a software system. Software development is hard. Software development is an example of a wicked problem.
11/28/21 Akash Deo 2
USER INTERFACE DEVELOPMENT CHANGES SOFTWARE DEVELOPMENT Adding a significant user interface to a software development project adds challenges. Support for connectivity. Support for media. Support for user-tailoring.
11/28/21 Akash Deo 3
ACTIVITIES IN SOFTWARE ENGINEERING Understanding and documenting the context of the project. Understanding and documenting the problem to be solved Designing and documenting a solution in the context. Implementing the solution. Testing and evaluating the solution.
11/28/21 Akash Deo 4
THE WATERFALL MODEL OF SOFTWARE DEVELOPMENT
11/28/21 Akash Deo 5
PHASES OF THE WATERFALL MODEL Systems engineering and analysis Software requirements analysis Software design Code Testing Maintenance
11/28/21 Akash Deo 6
BENEFITS OF EXACTLY FOLLOWING THE WATERFALL MODEL Following any methodology imposes discipline on the software development process. Following a phased model improves cost and resource forecasting.
11/28/21 Akash Deo 7
PROBLEMS OF FOLLOWING THE WATERFALL MODEL Does not inherently support iteration. Requires customer to completely elaborate requirements at the beginning of the project. Customer will not see an artifact until late in the development cycle.
11/28/21 Akash Deo 8
ACTIVITIES OF USABILITY ENGINEERING Understanding and documenting the context of the project. Understanding and documenting the problem to be solved. Designing and documenting a solution in the context. Implementing the solution. Testing and evaluating the solution.
11/28/21 Akash Deo 9
USABILITY AND SOFTWARE ENGINEERING In the abstract, the steps for both tasks are the same. We can set up parallel flows of activities for both usability and software engineering. The model supports iteration.
11/28/21 Akash Deo 10
USABILITY AND SOFTWARE ENGINEERING ACTIVITIES
11/28/21 Akash Deo 11
USABILITY AND SOFTWARE ENGINEERING ACTIVITIES
11/28/21 Akash Deo 12
THE DEVELOPMENT TEAM
Building a good interface is often the result of the efforts of a
team.
11/28/21 Akash Deo 13
DEVELOPMENT TEAM STRUCTURE Distribution of activities and communications Chief programmer team Egoless programming
Choice depends on group dynamic and type of
problem Exploratory problems may work better with egoless programming where familiar well-structured problems may be better with a chief programmer structure.
11/28/21 Akash Deo 14
PARTICIPATORY DESIGN
Users are members of the development team and work closely
with the designers. Advocates of participatory design stress that the participatory aspect leads to greater buy-in from users and hence higher user satisfaction.
11/28/21 Akash Deo 15
CONCLUSIONS
Usability and software engineering always follow a process.
Usability engineering often takes place in the larger context of software engineering.