Оригінал англійською Переклад українською

What is this book about?


Про що ця книга?

TSpell 1.12.16 в 17:02

This book is about conceptual models and conceptual design of interactive systems.


Ця книга про концептуальні моделі та концептуальний дизайн інтерактивних систем.

TSpell 1.12.16 в 17:02

There are so many attractively designed applications. Nevertheless, many leave the user frustrated. What do you need to consider before designing the screens in order to ensure that the application will provide a positive user experience?


І ній є багато гарно спроектованих додатків. Проте, багато з них залишають користувача в розчаруванні. Що ти маєш врахувати перед початком створення дизайну екранів, щоб переконатися що додаток покаже позитивний досвід користувача?

TSpell 1.12.16 в 17:07

Conceptual design is a key step in the process of user interface design that answers that question. And this book offers an effective methodology to do conceptual design.


Концептуальний дизайн - ключовий крок в процесі створення дизайну користувацьких інтерфейсів який дасть відповідь на запитання. Також ця книга пропонує ефективну методологію для створення концептуального дизайну.

TSpell 1.12.16 в 17:10

Let us examine a practical example to illustrate where you could encounter conceptual models in the overall context of designing and developing interactive systems. Imagine an application on a mobile device supporting physical workouts.


Дозвольте розглянути практичний приклад, щоб проілюструвати де ви зможете зустріти концептуальні моделі у загальному контексті дизайну та розробки інтерактивних систем. Уявіть додаток на мобільному пристрої, який підтримує фізичні тренування.

TSpell 13.12.16 в 16:04

Within such an application, imagine designing the future of reviewing previous workouts. We can envision a very straightforward 1-2-3 design process consisting of three major steps (Figure 1):


1. Take a few features;
2. Sketch a wireframe, test and revise; and then
3. Finalize the detailed design of the user interface.


However, how exactly did we get from the feature list in step 1 to the detailed wireframe in step 2? There are an un-aswered questions such as:


• How and when did we decide which items should be grouped? For example, should the "previous workouts" be a group?
• Did we define other groups of features? For example, should there be a group of planned workouts?


Figure 1:
A hypothetical three-step design process of a mobile application supporting physical workouts.

1 - Features
2 - A detailed wireframe
3 - Final detailed design

1. List previous workouts
2. Show some parameters for each
3. Allow selection of each


• Did we define the relations between the groups? For example, should the planned and previous workout groups be related somehow?
• Did we define if the user should be able to go from one group to another? For example, should the user be able to go from the previous workouts group to the planned workouts group?
• Did we determine where each of those groups would be? For example, would the previous workouts group be displayed on its own screen or together with planned workouts?
• And more...


These questions and the example reflect a gap in the methodical approach for designing and developing interactive systems. In particular, they reflect a gap between research and requirements (1 in Figure 1), on the one hand, and the detailed design (2 and 3 in Figure 1), on the other hand, and the detailed design (2 and 3 in Figure 1), on the other hand. However, there is another picture with the gap filled in (2 and 3 in Figure 2).


Conceptual design as the bridge between doing research and determining features, on the one hand, and detailed design, on the other hand.

1 - Features
4 - A detailed wireframe
5 - Final detailed designed

1. List previous workouts
2. Show some parameters for each
3. Allow selection of each


This book addresses the critical steps of the conceptual design process. The foundation for this process is effective methodology and good science rather than a magic leap involving more art than science. It fills the gap between research and analysis and design. In conceptual design, we define the logical model underlying the interactive system that we design and develop.


Is this book for you?


Ця книга для мене?

TSpell 1.12.16 в 17:11

This book is for you if:

• You design user interfaces.
• You are looking for ways to improve the usability of your product.
• You are looking for a systematic proven foundation to support the creative leap from requirements to design.


If you design user interfaces and are looking for ways to improve the usability of your designs, then this is for you. If you still experience the leap from functional requirements to screen design as a magical mystical experience and you want to introduce a systematic, proven approach, then this is for you.


If you review or test user interfaces designed by others and are looking for the words to share your feedback, then this is for you. It is for you whether you are (1) the product manager, (2) the UX or UI designer, (3) the programmer, (4) the marketing person, (5) the graphic designer, (6) an investor, or (7) any other person who has any stake in the product.


Is there any pre-requisite knowledge for using this book? Yes, some. The book focuses on a part of the entire user interface design process: conceptual design. That is why you should know something about the following:


• Fundamentals of user interface, usability, and user experience design
• User-centered or human-oriented design process
• User research


By studying and using this book, you will achieve two goals:

1. Understand conceptual models in terms of functional chunks, configuration, navigation & policy and in terms of how you can influence human performance, usability, and user experience by the way you define the conceptual model.
2. Implement a solid conceptual design methodology for developing conceptual models.


You can and should devote time to the construction of conceptual models even when you are engaged in an agile or learn development process aimed at expeditiously delivering something to clients and end users. This book challenges the tendency of some developers to think it could be a waste of time to do too much user research, or waste time engaging with wireframes or paper prototypes in exploring various ideas.


By engaging in conceptual design instead of skipping this critical phase, you will make the system more usable, saving significant time, money and goods as a result. You can avoid being part of the proliferation of unusable systems and suffer the costs of redesigning those systems to make them effective.


How is the book organized?


The book has two parts. The first part is a bit theoretical. It focuses on the concept of conceptual models and their impact on human performance, usability, and experience. You can view this part as a primer introducing and discussing this thing we call "a conceptual model."


The second part is a practical part. It focuses on the conceptual design process and the methodology with which we develop the conceptual model. The second part walks you through the steps in developing a conceptual model and you can use it as "how to" guide.