Making use : (Record no. 1221)

MARC details
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 090714s2000 maua b 001 0 eng
010 ## - LIBRARY OF CONGRESS CONTROL NUMBER
LC control number 00021621
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9780262032797
035 ## - SYSTEM CONTROL NUMBER
System control number (Sirsi) u2123
040 ## - CATALOGING SOURCE
Original cataloging agency EG-CaNU
Transcribing agency EG-CaNU
Modifying agency EG-CaNU
042 ## - AUTHENTICATION CODE
Authentication code ncode
082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 004.019
Edition number 21
100 1# - MAIN ENTRY--PERSONAL NAME
Personal name Carroll, John M.
Fuller form of name (John Millar),
Dates associated with a name 1950-
9 (RLIN) 23
245 10 - TITLE STATEMENT
Title Making use :
Remainder of title scenario-based design of human-computer interactions /
Statement of responsibility, etc. John M. Carroll.
260 ## - PUBLICATION, DISTRIBUTION, ETC.
Place of publication, distribution, etc. Cambridge, Mass. :
Name of publisher, distributor, etc. MIT Press,
Date of publication, distribution, etc. 2000.
300 ## - PHYSICAL DESCRIPTION
Extent xiv, 368 p. :
Other physical details ill. ;
Dimensions 24 cm.
504 ## - BIBLIOGRAPHY, ETC. NOTE
Bibliography, etc. note Includes bibliographical references and index.
520 ## - SUMMARY, ETC.
Summary, etc. 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 the 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.
505 #0 - FORMATTED CONTENTS NOTE
Formatted contents note The Sorcerers Apprentice -- What Is Design? -- ScenarioBased Design -- Video Information System -- programming Tutorial and Tools -- Usability Rationale -- Cumulative Design -- Evaluation and Theory Building -- Software Development -- Finding Scenarios and Making Claims -- Getting Around the TaskArtifact Cycle -- The Scenario Dilemma -- References
596 ## -
-- 1
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Human-computer interaction.
9 (RLIN) 1667
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Damaged status Not for loan Home library Current library Shelving location Date acquired Source of acquisition Total Checkouts Full call number Barcode Date last seen Copy number Price effective from Koha item type
    Dewey Decimal Classification     Main library Main library General Stacks 01/26/2020 GIFT   004.019 / CA.M 2000 004210 11/24/2019 1 11/24/2019 Books