000 03459nam a22004335i 4500
999 _c387396
_d387396
001 387396
003 ES-MaUEC
005 20230319113434.0
006 a||||fo|||| 00| 0
007 cr nn 008mamaa
008 220601s2012 sz | s |||| 0|eng d
020 _a9783031021954
024 7 _a10.1007/978-3-031-02195-4
_2doi
040 _aES-MaUEC
_bspa
_cES-MaUEC
_dES-MaUEC
050 4 _aQ387.2
_b2012 EB
100 1 _aJohnson, Jeff
_eautor
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_9687468
_c(Consultant)
245 1 0 _aConceptual Models :
_bCore to Good Design
_cby Jeff Johnson, Austin Henderson
250 _a1st edition 2012
264 1 _aCham
_bSpringer International Publishing
_c2012
300 _a1 recurso en línea (XIII, 96 páginas)
336 _atexto
_btxt
_2rdacontent
337 _aelectrónico
_bc
_2rdamedia
338 _arecurso electrónico
_bcr
_2rdacarrier
347 _aarchivo de texto
_bPDF
490 0 _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.
988 _aSynthesis Collection of Technology_2012
650 7 _2embne
_9149839
_aInterfaces de usuario
_xDiseño
650 7 _2embne
_9139824
_aProgramas de ordenador
_xDiseño
650 7 _2embne
_9686599
_aOntologías (Recuperación de la información)
700 1 _aHenderson, Austin
_eautor
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_9687467
776 0 8 _iPrinted edition:
_z9783031010675
776 0 8 _iPrinted edition:
_z9783031033230
856 4 0 _uhttps://go.openathens.net/redirector/universidadeuropea.es?url=https://doi.org/10.1007/978-3-031-02195-4
_zAcceso a este recurso digital (usuarios Universidad Europea de Madrid)
942 _2lcc
_cLE
998 _b03/2023
_dz
_esc
_zSI