Differential D15395 Diff 42581 source/introduction/concept.rst

Changeset View

Standalone View

View Options

source/introduction/concept.rst

1Concept 1​Concept
2======= 2​=======
3 3​
4The conceptual model is the most fundamental aspect of the interface, 4​The conceptual model is the most fundamental aspect of the interface,
5describing the relationship between the interface and the outside world. 5​describing the relationship between the interface and the outside world.
6The purpose of the conceptual model is to draw on the user’s past 6​The purpose of the conceptual model is to draw on the user’s past
7experiences so they can readily understand basic operations and 7​experiences so they can readily understand basic operations and
8naturally predict functionality in an application. 8​naturally predict functionality in an application.
9 9​
10Project vision 10​Project vision
11-------------- 11​--------------
12 12​
13A vision describes the goal of the project. It can be emotive and a 13​A vision describes the goal of the project. It can be emotive and a
14source of inspiration. For instance, by outlining how the final product 14​source of inspiration. For instance, by outlining how the final product
15makes the world a better place you can draw upon inspiration to create 15​makes the world a better place you can draw upon inspiration to create
16the end goal of your project. Describe the project's final goals. 16​the end goal of your project. Describe the project's end goals.
17Explain who will use the product, and how he or she will take advantage 17​Explain who will use the product, and how he or she will take advantage
18from it. Make sure your vision is shared between all project 18​from it. Make sure your vision is shared between all project's
ngrahamUnsubmitted
Not Done

This change isn't grammatically correct. "All project stakeholders" is okay already, just a little terse. If you want to change this, it would need to become "all of the project's stakeholders".

ngraham: This change isn't grammatically correct. "All project stakeholders" is okay already, just a…
19stakeholders. Leave room in your vision for creativity and changes. Keep 19​stakeholders. Leave room in your vision for creativity and changes. Keep
20it short. 20​it short.
21 21​
22A good starting-point is the *elevator pitch*: 22​A good starting point is the typical *elevator pitch*:
23 23​
24- FOR *target customer* 24​- **FOR** *target customer*
25- WHO *statement of the need* 25​- **WHO** *statement of the need*
26- THE *product name* 26​- **THE** *product name*
27- IS A *product category* 27​- **IS A** *product category*
28- THAT *key benefit* 28​- **THAT** *key benefit*
29- UNLIKE *primary competitor* 29​- **UNLIKE** *primary competitor*
30- OUR PRODUCT *further differentiation* 30​- **OUR PRODUCT** *further differentiation*
31 31​
32Personas 32​Personas
33-------- 33​--------
34 34​
35Personas can help identify the target users of your application and 35​Personas can help identify the target users of your application and
36provide a common understanding among the design and development team. A 36​provide a common understanding among the design and development team. A
37persona is the representation of a user, based on empirical data. 37​persona is the representation of a user based on empirical data.
38Personas describe the target users, giving a clear picture of how 38​Personas describe target users, providing a clear picture of how
39they're likely to use the system, and what they’ll expect from it. The 39​they are likely to use the system, and what they should expect from it. The
40description includes a concise summary of characteristics of the user, 40​description includes a brief summary of user characteristics,
41their experience, goals and tasks, pain points, environmental conditions 41​their experience, tasks, goals, pain points, environmental conditions
42and even name. 42​and even name.
43 43​
44​Using a persona name will help you further identify your target user easier.
45​
44The KDE usability team has created :doc:`predefined personas <personas>` which we 46​The KDE usability team has created :doc:`predefined personas <personas>` which we
45highly recommended using for your project. 47​highly recommended using for your project.
46 48​
47If you choose to create your own personas, consider the following: 49​If you choose to create your own personas, consider the following:
48 50​
49- Always try to define personas based on empirical data. Feel free to 51​- Always try to define personas based on empirical data. Feel free to
50 ask the KDE user experience team (kde-usability at kde.org) for 52​ ask the KDE user experience team (kde-usability at kde.org) for
51 assistance with the collection of empirical data. 53​ assistance with the collection of empirical data. If empirical data is not available, still reach out to the usability team for guidance.
52- Add enough information to establish a good impression of the target 54​- Add enough information to establish a good representation of the target
53 user and stay concise. 55​ user and stay concise.
54- Common elements are name, job titles and major responsibilities, 56​- Use common elements to describe your persona such as name, job titles and major responsibilities,
55 demographics such as age, education, ethnicity, and family status, 57​ demographics such as age, education, ethnicity, family status,
56 goals and tasks they are trying to complete using the application, 58​ goals and tasks they are trying to complete using the application,
57 physical, social, and technological environment. 59​ physical, social, and technological environment.
58- Add a quote that sums up what matters most to the persona and a 60​- Add a quote that sums up what matters most to the persona and a
59 casual picture representing that user group. 61​ casual picture representing that user group. Like a motto.
60- Discriminate between primary (the basic user) and secondary 62​- Draw differences between primary (the basic user) and secondary
ngrahamUnsubmitted
Not Done

"Like a motto." is a sentence fragment.

ngraham: "Like a motto." is a sentence fragment.
61 (additional users) persona. If it makes sense, describe the group of 63​ (additional users) persona. If it makes sense, describe the group of
62 users that is explicitly not supported by an anti-persona. Respect 64​ detractors by creating an anti-persona. Respect
63 the law of parsimony and have as few personas as possible. 65​ the law of parsimony [#] and have as few personas as possible.
64- Make sure your persona can act in different scenarios. 66​- Make sure your persona can work in different scenarios.
65 67​
66User Stories 68​User Stories
67------------ 69​------------
68 70​
69Scenarios illustrate how the users achieve their goals by means of 71​Scenarios illustrate how the users achieve their goals by means of using
70task-orientated examples. It is supplementary to a persona, providing 72​task-orientated examples. These examples help develop a persona by providing an efficient methods applicable in a wide variety of applications.
71together an efficient method applicable in a wide range of applications. ​
72 73​
73Use the following guide to help create scenarios: 74​Use the following steps to create scenarios:
74 75​
75- Always try to create scenarios based on empirical data. Feel free to 76​- Always create scenarios based on empirical data. Feel free to
76 ask the KDE user experience team (kde-usability at kde.org) for 77​ ask the KDE user experience team (kde-usability at kde.org) for
fabianrUnsubmitted
Not Done

Does that still exist kde-usability at kde.org ?

fabianr: Does that still exist kde-usability at kde.org ?
ngrahamUnsubmitted
Not Done

Yeah, at this point VDG has taken over that role so we should direct people there instead.

ngraham: Yeah, at this point VDG has taken over that role so we should direct people there instead.
77 assistance with the collection of empirical data. 78​ assistance with the collection of empirical data.
78- Take technical configuration, environmental condition, organizational 79​- Take technical configurations, environmental conditions, organizational
79 and social aspects into consideration. 80​ and social aspects into consideration.
80- If available, use real world images to support imagination. 81​- Use real world images to support imagination.
81- Try to include problem situations that will test the system concept, 82​- Include problem situations that will test the system concept,
82 not just straightforward scenarios. 83​ not just straightforward scenarios.
83 84​
84Target Device Classes 85​Target Device Classes
85--------------------- 86​---------------------
86 87​
87While thinking about the scenarios, also consider devices of which 88​While thinking about the scenarios, think also of possible devices that such persona would use. Plasma and
88class(es) the personas would use in that scenario. Currently, Plasma and 89​(some) KDE applications target the following device categories:
ngrahamUnsubmitted
Not Done

"that such persona" is not grammatically correct. "that your persona" or "that the persona" would work, though.

ngraham: "that such persona" is not grammatically correct. "that your persona" or "that the persona"…
89(some) KDE applications target the following device classes: ​
90Desktop/laptop, media center (TV), phone and tablet/convertible. Your 90​Desktop/laptop, media center (TV), phone and tablet/convertible. Your
91application may target other device classes (like eg. in-vehicle 91​application may target other device categories (like eg. in-vehicle
92entertainment systems, kiosk systems, ...) as well. 92​entertainment systems, kiosk systems, points of sale...) as well.
93 93​
94Documenting Your Concept 94​Documenting Your Concept
95------------------------ 95​------------------------
96 96​
97A useful template for documenting your personas and scenarios is the 97​A useful template for documenting your personas and scenarios is the
98:doc:`Project User Research Template <research>`. 98​:doc:`Project User Research Template <research>`.
99​
100​.. [#] a principle according to which an explanation of a thing or event is made with the fewest possible assumptions.