Difference between revisions of "Complexity"
Jump to navigation
Jump to search
Line 31: | Line 31: | ||
If you want to contribute, click [https://lehmannmax.de/Survey/survey.html here]. | If you want to contribute, click [https://lehmannmax.de/Survey/survey.html here]. | ||
− | ==[[Complexity_References| | + | ==[[Complexity_References|References for Complexity]]== |
===[[Compatibility_References#General|General]]=== | ===[[Compatibility_References#General|General]]=== | ||
===[[Compatibility_References#Dividing_Processes|Dividing Processes]]=== | ===[[Compatibility_References#Dividing_Processes|Dividing Processes]]=== | ||
</div> | </div> |
Revision as of 13: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.