Difference between revisions of "Complexity"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
[[File:Complexity.png|400px|none|Illustration Complexity]] | [[File:Complexity.png|400px|none|Illustration Complexity]] | ||
<div class="text_content"> | <div class="text_content"> | ||
| − | == | + | ==Overview== |
* How to handle complex processes or content. | * How to handle complex processes or content. | ||
* Extensive or complex content can be better understood if it is broken down into parts. | * Extensive or complex content can be better understood if it is broken down into parts. | ||
| Line 26: | Line 26: | ||
* A saving function should allow users to pause long processes and resume them later without losses. | * A saving function should allow users to pause long processes and resume them later without losses. | ||
| − | == | + | ==User story== |
There is no user story for this topic yet. | There is no user story for this topic yet. | ||
Revision as of 14:37, 3 June 2021
| headline | Complexity |
|---|---|
| headline coordinates | 1.000, 290.903, 0.000 |
| image | /wiki/images/Complexity.png |
| image coordinates | 0, 0, 0 |
| simple introduction |
|
| simple introduction coordinates | 0, 0, 0 |
| testimonial | It seems that there is no testimonial for this topic yet. <a href="https://lehmannmax.de/Survey/survey.html">If you want to contribute, click here to get in touch.</a> |
| testimonial coordinates | 0, 0, 0 |
| links to | |
| belongs to | Attention |
| contains | Complexity_References |
Overview
- How to handle complex processes or content.
- Extensive or complex content can be better understood if it is broken down into parts.
- Long processes that need user input should be split into several simpler processes.
- A saving function should allow users to pause long processes and resume them later without losses.
User story
There is no user story for this topic yet.
If you want to contribute, click here.