[kde-guidelines] Styleguide: Destinata

[Heiko Tietze]

Structure > Conceptual Model 
* Specify requirements considering destinata and animata of users.
http://techbase.kde.org/Projects/Usability/HIG/Destinata


== Purpose ==
Any application has a certain goal that users want to achieve with it. Usually this goal can be subdivided into a bunch of requirements, i.e. features that have to be implemented by the developers. From the usability's point of view, features that concerns users only can be called ''destinata''.
Destinatas are explicit goals, for instance the task to write an email. How well this goal is being accomplished in terms of easiness, suitability, error tolerance etc. is discussed in respect to [[Projects/Usability/HIG/Animata|animata]].

== Guidelines ==
* Define users goal clear in advance to the development process,
* Keep persona and scenario in mind. 
* Requirements should be complete, confine, and comprehensible.
* Prove all requirements.

== Example ==

[[Category:Usability]][[Category:Structure]][[Category:Task_Flow]]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-guidelines/attachments/20140130/782defb7/attachment.html>