Difference between revisions of "Complexity"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
<li>A saving function should allow users to pause long processes and resume them later without losses.</li></ul> | <li>A saving function should allow users to pause long processes and resume them later without losses.</li></ul> | ||
|coordsimplo=0, 0, 0 | |coordsimplo=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 | + | |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.</a> |
|coordtesti=0, 0, 0 | |coordtesti=0, 0, 0 | ||
|belongsto=Attention | |belongsto=Attention |
Revision as of 16:19, 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.</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.