This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
ddsf:public:guidebook:06_append:glossary:u:use_case [2020/06/04 21:40] admin ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:glossary:u:use_case [2021/07/14 16:46] (current) murphy ↷ Links adapted because of a move operation |
||
---|---|---|---|
Line 1: | Line 1: | ||
===== Use Case ===== | ===== Use Case ===== | ||
- | [[ddsf:private:cookbook:03_append:glossary| Return to Glossary ]] | + | [[ddsf:public:guidebook:06_append:glossary:start| Return to Glossary ]] |
===== What is a use case? ===== | ===== What is a use case? ===== | ||
Line 8: | Line 8: | ||
===== Why are use cases important? ===== | ===== Why are use cases important? ===== | ||
- | : //Use cases are important, because they will show how systems respond when they are used. A use case describes how a system helps a user achieve their goal. Unlike a user scenario, a use case is more orientated towards the system’s behavior rather than the user. The language in which a use case is written should be simple and the writer of a use case should avoid technical terminology. A use case should not include too much context about the user or their emotional response to an interaction.// | + | : //Use cases are important, because they will show how systems respond when they are used. A use case describes how a system helps a user achieve their [[ddsf:public:guidebook:06_append:glossary:g:goal|goal]]. Unlike a [[ddsf:public:guidebook:06_append:glossary:u:user_scenario|user scenario]], a use case is more orientated towards the system’s behavior rather than the user. The language in which a use case is written should be simple and the writer of a use case should avoid technical terminology. A use case should not include too much context about the user or their emotional response to an interaction.// |
===== The purpose of use cases ===== | ===== The purpose of use cases ===== |