|
|
|
|
| LEADER |
02334nmm a2200289 u 4500 |
| 001 |
EB002070616 |
| 003 |
EBX01000000000000001210706 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
220922 ||| eng |
| 020 |
|
|
|a 9780262269926
|
| 020 |
|
|
|a 0262269929
|
| 050 |
|
4 |
|a QA76.9.H85
|
| 100 |
1 |
|
|a Carroll, John M.
|
| 245 |
0 |
0 |
|a Making use
|h Elektronische Ressource
|b scenario-based design of human-computer interactions
|c John M. Carroll
|
| 260 |
|
|
|a Cambridge, Mass.
|b MIT Press
|c 2000
|
| 300 |
|
|
|a xiv, 368 pages
|b illustrations
|
| 653 |
|
|
|a COMPUTER SCIENCE/Human Computer Interaction
|
| 653 |
|
|
|a Human-computer interaction
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b MITArchiv
|a MIT Press eBook Archive
|
| 028 |
5 |
0 |
|a 10.7551/mitpress/4398.001.0001
|
| 776 |
|
|
|z 0262032791
|
| 776 |
|
|
|z 9780262032797
|
| 856 |
4 |
0 |
|u https://doi.org/10.7551/mitpress/4398.001.0001?locatt=mode:legacy
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 004/.01/9
|
| 520 |
|
|
|a "Difficult to learn and awkward to use, today's information systems often change our activities in ways that we do not need or want. The problem lies in the software development process. In this book John Carroll shows how a pervasive but underused element of design practice, the scenario, can transform information systems design.Traditional textbook approaches manage the complexity of the design process via abstraction, treating design problems as if they were composites of puzzles. Scenario-based design uses concretization. A scenario is a concrete story about use. For example: "A person turned on a computer; the screen displayed a button labeled Start; the person used the mouse to select the button." Scenarios are a vocabulary for coordinating the central tasks of system development--understanding people's needs, envisioning new activities and technologies, designing effective systems and software, and drawing general lessons from systems as they are developed and used. Instead of designing software by listing requirements, functions, and code modules, the designer focuses first on the activities that need to be supported and then allows descriptions of those activities to drive everything else.In addition to a comprehensive discussion of the principles of scenario-based design, the book includes in-depth examples of its application."
|