dido:public:ra:xapend:xapend.a_glossary:u:use_case
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.a_glossary:u:use_case [2021/10/04 13:40] 50.19.247.197 ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.a_glossary:u:use_case [2021/10/12 18:11] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Use Case ===== | + | ===== Use-Case ===== |
| [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] | ||
| - | ===== What is a use case? ===== | + | : //A **Use-Case** is a description of how a system responds to a request from an external source. This is written with reference to the technical steps that happen for the task to be completed.// |
| - | : //A use case is a description of how a system responds to a request from an external source. This is written with reference to the technical steps that happen for the task to be completed.// | + | ===== 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 [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]]. Unlike a [[dido:public:ra:xapend:xapend.a_glossary:u:uscenario|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 [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]]. Unlike a [[dido:public:ra:xapend:xapend.a_glossary:u:uscenario|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 ===== | + | : //In a Use-Case a list of goals can be defined and an analysis can be made of how complex and expensive it is for these goals to be met. In team projects, Use-Cases are useful to see which areas of a system need to be developed and what obstacles could arise in performing a task.// |
| - | : //In a use case a list of goals can be defined and an analysis can be made of how complex and expensive it is for these goals to be met. In team projects, use cases are useful to see which areas of a system need to be developed and what obstacles could arise in performing a task.// | + | Source: [[https://pidoco.com/en/help/ux/use-case ]] |
| - | + | ||
| - | Source: [[https://pidoco.com/en/help/ux/use-case | Use Case ]] | + | |
dido/public/ra/xapend/xapend.a_glossary/u/use_case.1633369215.txt.gz · Last modified: 2021/10/04 13:40 by 50.19.247.197
