Author: Austina De Bonte
Publisher: Pearson Education
ISBN: 0735679339
Category : Computers
Languages : en
Pages : 574
Book Description
Annotation Great technology alone is rarely sufficient today to ensure a products success. At Microsoft, scenario-focused engineering is a customer-centric, iterative approach used to design and deliver the deeper experiences and emotional engagement customers demand in new products. In this book, youll discover the proven practices and lessons learned from real-world implementations of this approach, including:Why design matters: Understand a competitive landscape where customers are no longer satisfied by products that are merely useful, but respond instead to products they crave using. What it means to be customer focused: Recognize that you are not the customer, understand customers can have difficulty articulating what they want, and apply techniques that uncover their unspoken needs. How to iterate effectively: Implement a development system that is flexible enough to respond to early and continuous feedback, and enables experimentation with multiple ideas and feedback loops simultaneously. How to bridge the culture gap: In an engineering environment traditionally rooted in strong analytics, the ideas and practices for scenario-focused engineering may not be intuitive. Learn how to change team mindset from deciding what a product, service, or device will do, to discovering what customers actually want and what will work for them in real-life scenarios. Connections with Lean and Agile approaches: See the connections, gaps, and overlaps among the Lean, Agile, and Scenario-Focused Engineering methodologies, and achieve a more holistic view of software development.
Scenario-focused Engineering
Author: Austina De Bonte
Publisher: Pearson Education
ISBN: 0735679339
Category : Computers
Languages : en
Pages : 574
Book Description
Annotation Great technology alone is rarely sufficient today to ensure a products success. At Microsoft, scenario-focused engineering is a customer-centric, iterative approach used to design and deliver the deeper experiences and emotional engagement customers demand in new products. In this book, youll discover the proven practices and lessons learned from real-world implementations of this approach, including:Why design matters: Understand a competitive landscape where customers are no longer satisfied by products that are merely useful, but respond instead to products they crave using. What it means to be customer focused: Recognize that you are not the customer, understand customers can have difficulty articulating what they want, and apply techniques that uncover their unspoken needs. How to iterate effectively: Implement a development system that is flexible enough to respond to early and continuous feedback, and enables experimentation with multiple ideas and feedback loops simultaneously. How to bridge the culture gap: In an engineering environment traditionally rooted in strong analytics, the ideas and practices for scenario-focused engineering may not be intuitive. Learn how to change team mindset from deciding what a product, service, or device will do, to discovering what customers actually want and what will work for them in real-life scenarios. Connections with Lean and Agile approaches: See the connections, gaps, and overlaps among the Lean, Agile, and Scenario-Focused Engineering methodologies, and achieve a more holistic view of software development.
Publisher: Pearson Education
ISBN: 0735679339
Category : Computers
Languages : en
Pages : 574
Book Description
Annotation Great technology alone is rarely sufficient today to ensure a products success. At Microsoft, scenario-focused engineering is a customer-centric, iterative approach used to design and deliver the deeper experiences and emotional engagement customers demand in new products. In this book, youll discover the proven practices and lessons learned from real-world implementations of this approach, including:Why design matters: Understand a competitive landscape where customers are no longer satisfied by products that are merely useful, but respond instead to products they crave using. What it means to be customer focused: Recognize that you are not the customer, understand customers can have difficulty articulating what they want, and apply techniques that uncover their unspoken needs. How to iterate effectively: Implement a development system that is flexible enough to respond to early and continuous feedback, and enables experimentation with multiple ideas and feedback loops simultaneously. How to bridge the culture gap: In an engineering environment traditionally rooted in strong analytics, the ideas and practices for scenario-focused engineering may not be intuitive. Learn how to change team mindset from deciding what a product, service, or device will do, to discovering what customers actually want and what will work for them in real-life scenarios. Connections with Lean and Agile approaches: See the connections, gaps, and overlaps among the Lean, Agile, and Scenario-Focused Engineering methodologies, and achieve a more holistic view of software development.
Usability Engineering
Author: Mary Beth Rosson
Publisher: Morgan Kaufmann
ISBN: 1558607129
Category : Computers
Languages : en
Pages : 456
Book Description
Usability engineering is about designing products that are easy to use. This text provides an introduction to human computer interaction principles, and how to apply them in ways that make software and hardware more effective and easier to use.
Publisher: Morgan Kaufmann
ISBN: 1558607129
Category : Computers
Languages : en
Pages : 456
Book Description
Usability engineering is about designing products that are easy to use. This text provides an introduction to human computer interaction principles, and how to apply them in ways that make software and hardware more effective and easier to use.
Making Use
Author: John M. Carroll
Publisher: MIT Press
ISBN: 0262513889
Category : Computers
Languages : en
Pages : 766
Book Description
John Carroll shows how a pervasive but underused element of design practice, the scenario, can transform information systems design. 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.
Publisher: MIT Press
ISBN: 0262513889
Category : Computers
Languages : en
Pages : 766
Book Description
John Carroll shows how a pervasive but underused element of design practice, the scenario, can transform information systems design. 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.
Scenario-Based Design
Author: John Millar Carroll
Publisher:
ISBN:
Category : Computers
Languages : en
Pages : 426
Book Description
This volume is based on a workshop sponsored by the editor at IBM, and includes contributions from an international group of researchers in the field of human computer interaction.
Publisher:
ISBN:
Category : Computers
Languages : en
Pages : 426
Book Description
This volume is based on a workshop sponsored by the editor at IBM, and includes contributions from an international group of researchers in the field of human computer interaction.
Scenarios, Stories, Use Cases
Author: Ian F. Alexander
Publisher: John Wiley & Sons
ISBN: 0470861959
Category : Computers
Languages : en
Pages : 544
Book Description
Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems
Publisher: John Wiley & Sons
ISBN: 0470861959
Category : Computers
Languages : en
Pages : 544
Book Description
Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems
An Elegant Puzzle
Author: Will Larson
Publisher: Stripe Press
ISBN: 1953953336
Category : Computers
Languages : en
Pages : 281
Book Description
A human-centric guide to solving complex problems in engineering management, from sizing teams to handling technical debt. There’s a saying that people don’t leave companies, they leave managers. Management is a key part of any organization, yet the discipline is often self-taught and unstructured. Getting to the good solutions for complex management challenges can make the difference between fulfillment and frustration for teams—and, ultimately, between the success and failure of companies. Will Larson’s An Elegant Puzzle focuses on the particular challenges of engineering management—from sizing teams to handling technical debt to performing succession planning—and provides a path to the good solutions. Drawing from his experience at Digg, Uber, and Stripe, Larson has developed a thoughtful approach to engineering management for leaders of all levels at companies of all sizes. An Elegant Puzzle balances structured principles and human-centric thinking to help any leader create more effective and rewarding organizations for engineers to thrive in.
Publisher: Stripe Press
ISBN: 1953953336
Category : Computers
Languages : en
Pages : 281
Book Description
A human-centric guide to solving complex problems in engineering management, from sizing teams to handling technical debt. There’s a saying that people don’t leave companies, they leave managers. Management is a key part of any organization, yet the discipline is often self-taught and unstructured. Getting to the good solutions for complex management challenges can make the difference between fulfillment and frustration for teams—and, ultimately, between the success and failure of companies. Will Larson’s An Elegant Puzzle focuses on the particular challenges of engineering management—from sizing teams to handling technical debt to performing succession planning—and provides a path to the good solutions. Drawing from his experience at Digg, Uber, and Stripe, Larson has developed a thoughtful approach to engineering management for leaders of all levels at companies of all sizes. An Elegant Puzzle balances structured principles and human-centric thinking to help any leader create more effective and rewarding organizations for engineers to thrive in.
Adaptive Code
Author: Gary McLean Hall
Publisher: Microsoft Press
ISBN: 1509302611
Category : Computers
Languages : en
Pages : 854
Book Description
Write code that can adapt to changes. By applying this book’s principles, you can create code that accommodates new requirements and unforeseen scenarios without significant rewrites. Gary McLean Hall describes Agile best practices, principles, and patterns for designing and writing code that can evolve more quickly and easily, with fewer errors, because it doesn’t impede change. Now revised, updated, and expanded, Adaptive Code, Second Edition adds indispensable practical insights on Kanban, dependency inversion, and creating reusable abstractions. Drawing on over a decade of Agile consulting and development experience, McLean Hall has updated his best-seller with deeper coverage of unit testing, refactoring, pure dependency injection, and more. Master powerful new ways to: • Write code that enables and complements Scrum, Kanban, or any other Agile framework • Develop code that can survive major changes in requirements • Plan for adaptability by using dependencies, layering, interfaces, and design patterns • Perform unit testing and refactoring in tandem, gaining more value from both • Use the “golden master” technique to make legacy code adaptive • Build SOLID code with single-responsibility, open/closed, and Liskov substitution principles • Create smaller interfaces to support more-diverse client and architectural needs • Leverage dependency injection best practices to improve code adaptability • Apply dependency inversion with the Stairway pattern, and avoid related anti-patterns About You This book is for programmers of all skill levels seeking more-practical insight into design patterns, SOLID principles, unit testing, refactoring, and related topics. Most readers will have programmed in C#, Java, C++, or similar object-oriented languages, and will be familiar with core procedural programming techniques.
Publisher: Microsoft Press
ISBN: 1509302611
Category : Computers
Languages : en
Pages : 854
Book Description
Write code that can adapt to changes. By applying this book’s principles, you can create code that accommodates new requirements and unforeseen scenarios without significant rewrites. Gary McLean Hall describes Agile best practices, principles, and patterns for designing and writing code that can evolve more quickly and easily, with fewer errors, because it doesn’t impede change. Now revised, updated, and expanded, Adaptive Code, Second Edition adds indispensable practical insights on Kanban, dependency inversion, and creating reusable abstractions. Drawing on over a decade of Agile consulting and development experience, McLean Hall has updated his best-seller with deeper coverage of unit testing, refactoring, pure dependency injection, and more. Master powerful new ways to: • Write code that enables and complements Scrum, Kanban, or any other Agile framework • Develop code that can survive major changes in requirements • Plan for adaptability by using dependencies, layering, interfaces, and design patterns • Perform unit testing and refactoring in tandem, gaining more value from both • Use the “golden master” technique to make legacy code adaptive • Build SOLID code with single-responsibility, open/closed, and Liskov substitution principles • Create smaller interfaces to support more-diverse client and architectural needs • Leverage dependency injection best practices to improve code adaptability • Apply dependency inversion with the Stairway pattern, and avoid related anti-patterns About You This book is for programmers of all skill levels seeking more-practical insight into design patterns, SOLID principles, unit testing, refactoring, and related topics. Most readers will have programmed in C#, Java, C++, or similar object-oriented languages, and will be familiar with core procedural programming techniques.
User-Centred Requirements Engineering
Author: Alistair Sutcliffe
Publisher: Springer Science & Business Media
ISBN: 1447102177
Category : Computers
Languages : en
Pages : 224
Book Description
If you have picked up this book and are browsing the Preface, you may well be asking yourself"What makes this book different from the large number I can find on amazon. com?". Well, the answer is a blend of the academic and the practical, and views of the subject you won't get from anybody else: how psychology and linguistics influence the field of requirements engineering (RE). The title might seem to be a bit of a conundrum; after all, surely requirements come from people so all requirements should be user-centred. Sadly, that is not always so; many system disasters have been caused simply because requirements engineering was not user-centred or, worse still, was not practised at all. So this book is about putting the people back into com puting, although not simply from the HCI (human-computer interaction) sense; instead, the focus is on how to understand what people want and then build appropriate computer systems.
Publisher: Springer Science & Business Media
ISBN: 1447102177
Category : Computers
Languages : en
Pages : 224
Book Description
If you have picked up this book and are browsing the Preface, you may well be asking yourself"What makes this book different from the large number I can find on amazon. com?". Well, the answer is a blend of the academic and the practical, and views of the subject you won't get from anybody else: how psychology and linguistics influence the field of requirements engineering (RE). The title might seem to be a bit of a conundrum; after all, surely requirements come from people so all requirements should be user-centred. Sadly, that is not always so; many system disasters have been caused simply because requirements engineering was not user-centred or, worse still, was not practised at all. So this book is about putting the people back into com puting, although not simply from the HCI (human-computer interaction) sense; instead, the focus is on how to understand what people want and then build appropriate computer systems.
Come, Let’s Play
Author: David Harel
Publisher: Springer Science & Business Media
ISBN: 3642190294
Category : Computers
Languages : en
Pages : 377
Book Description
This book does not tell a story. Instead, it is about stories. Or rather, in technical terms, it is about scenarios. Scenarios of system behavior. It con centrates on reactive systems, be they software or hardware, or combined computer-embedded systems, including distributed and real-time systems. We propose a different way to program such systems, centered on inter object scenario-based behavior. The book describes a language, two tech niques, and a supporting tool. The language is a rather broad extension of live sequence charts (LSCs), the original version of which was proposed in 1998 by W. Damm and the first-listed author of this book. The first of the two techniques, called play-in, is a convenient way to 'play in' scenario based behavior directly from the system's graphical user interface (QUI). The second technique, play-out, makes it possible to execute, or 'play out', the behavior on the QUI as if it were programmed in a conventional intra object state-based fashion. All this is implemented in full in our tool, the Play-Engine. The book can be viewed as offering improvements in some ofthe phases of known system development life cycles, e.g., requirements capture and anal ysis, prototyping, and testing. However, there is a more radical way to view the book, namely, as proposing an alternative way to program reactivity, which, being based on inter-object scenarios, is a lot closer to how people think about systems and their behavior.
Publisher: Springer Science & Business Media
ISBN: 3642190294
Category : Computers
Languages : en
Pages : 377
Book Description
This book does not tell a story. Instead, it is about stories. Or rather, in technical terms, it is about scenarios. Scenarios of system behavior. It con centrates on reactive systems, be they software or hardware, or combined computer-embedded systems, including distributed and real-time systems. We propose a different way to program such systems, centered on inter object scenario-based behavior. The book describes a language, two tech niques, and a supporting tool. The language is a rather broad extension of live sequence charts (LSCs), the original version of which was proposed in 1998 by W. Damm and the first-listed author of this book. The first of the two techniques, called play-in, is a convenient way to 'play in' scenario based behavior directly from the system's graphical user interface (QUI). The second technique, play-out, makes it possible to execute, or 'play out', the behavior on the QUI as if it were programmed in a conventional intra object state-based fashion. All this is implemented in full in our tool, the Play-Engine. The book can be viewed as offering improvements in some ofthe phases of known system development life cycles, e.g., requirements capture and anal ysis, prototyping, and testing. However, there is a more radical way to view the book, namely, as proposing an alternative way to program reactivity, which, being based on inter-object scenarios, is a lot closer to how people think about systems and their behavior.
Experimentation in Software Engineering
Author: Claes Wohlin
Publisher: Springer Science & Business Media
ISBN: 3642290442
Category : Computers
Languages : en
Pages : 249
Book Description
Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors’ book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a “cookbook” when evaluating new methods or techniques before implementing them in their organization.
Publisher: Springer Science & Business Media
ISBN: 3642290442
Category : Computers
Languages : en
Pages : 249
Book Description
Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors’ book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a “cookbook” when evaluating new methods or techniques before implementing them in their organization.