000 03540nam a22005055i 4500
001 978-3-031-02195-4
003 DE-He213
005 20240730165219.0
007 cr nn 008mamaa
008 220601s2012 sz | s |||| 0|eng d
020 _a9783031021954
_9978-3-031-02195-4
024 7 _a10.1007/978-3-031-02195-4
_2doi
050 4 _aQA76.9.U83
050 4 _aQA76.9.H85
072 7 _aUYZ
_2bicssc
072 7 _aCOM079010
_2bisacsh
072 7 _aUYZ
_2thema
082 0 4 _a005.437
_223
082 0 4 _a004.019
_223
100 1 _aJohnson, Jeff.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_987878
245 1 0 _aConceptual Models
_h[electronic resource] :
_bCore to Good Design /
_cby Jeff Johnson, Austin Henderson.
250 _a1st ed. 2012.
264 1 _aCham :
_bSpringer International Publishing :
_bImprint: Springer,
_c2012.
300 _aXIII, 96 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
490 1 _aSynthesis Lectures on Human-Centered Informatics,
_x1946-7699
505 0 _aUsing Tools -- Start with the Conceptual Model -- Definition -- Structure -- Example -- Essential Modeling -- Optional Modeling -- Process -- Value -- Epilogue.
520 _aPeople make use of software applications in their activities, applying them as tools in carrying out tasks. That this use should be good for people--easy, effective, efficient, and enjoyable--is a principal goal of design. In this book, we present the notion of Conceptual Models, and argue that Conceptual Models are core to achieving good design. From years of helping companies create software applications, we have come to believe that building applications without Conceptual Models is just asking for designs that will be confusing and difficult to learn, remember, and use. We show how Conceptual Models are the central link between the elements involved in application use: people's tasks (task domains), the use of tools to perform the tasks, the conceptual structure of those tools, the presentation of the conceptual model (i.e., the user interface), the language used to describe it, its implementation, and the learning that people must do to use the application. We further show that putting a Conceptual Model at the center of the design and development process can pay rich dividends: designs that are simpler and mesh better with users' tasks, avoidance of unnecessary features, easier documentation, faster development, improved customer uptake, and decreased need for training and customer support. Table of Contents: Using Tools / Start with the Conceptual Model / Definition / Structure / Example / Essential Modeling / Optional Modeling / Process / Value / Epilogue.
650 0 _aUser interfaces (Computer systems).
_911681
650 0 _aHuman-computer interaction.
_96196
650 1 4 _aUser Interfaces and Human Computer Interaction.
_931632
700 1 _aHenderson, Austin.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_987880
710 2 _aSpringerLink (Online service)
_987882
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783031010675
776 0 8 _iPrinted edition:
_z9783031033230
830 0 _aSynthesis Lectures on Human-Centered Informatics,
_x1946-7699
_987883
856 4 0 _uhttps://doi.org/10.1007/978-3-031-02195-4
912 _aZDB-2-SXSC
942 _cEBK
999 _c86165
_d86165