Good user manual and easy-to-use software Theory

Good User Manual: You can use the software after reading it. You do not need to transfer it many times. Simply put, you can understand it at a glance.

Easy-to-use software: dummies can complete almost all functions without having to look at the user manual.

This is my understanding of the ease of use of user manuals and software.

At first glance, the two seem to be in conflict. It cannot help but make people have such questions. If a user manual is well written, it indirectly indicates that the software is not easy to use? Or can easy-to-use software be out of user manual?

None. The two are essentially the unity of contradictions. I understand it as follows:
The ease of use of software is a process of constant pursuit. We need to pursue from tourb C to vs2005 (which is better to use DOS to Vista ?) Constantly Improve the ease-of-use attempts and efforts. It may include all the processes from requirement function division, system architecture design, detailed design, coding, etc. The most direct feeling is the definition and uidesign of the workflow. This goal should be pursued throughout the entire process of each software. Fully complies with the user habits and regional habits of the public (or professional users.

User Manual is the reference material of end users, which makes necessary steps and products in the system R & D process. As a document that explains the functions and usage details of the software system to the terminal, it should be concise, smooth, compliant with reading habits and comprehensive coverage.

Contradictions:
Limit (easy to use software) = target users do not need user manual

Uniformity:
The ease of use of software is always relative. We do not have to aim for everyone-including those who do not use Windows or do not use the foundation of the application software at all-they will be able to use all the functions at a glance, this makes it unnecessary to query user manuals.

The user manual should be a useful supplement to the software to remove text instructions, tips floating prompts, etc, this allows people without computer operation experience to read and view the functions, operations, convenient methods, and skills involved in the system.

I am currently writing a user manual for software and hardware integration products. The framework and style definitions are different among my colleagues. So I want to keep a note of what I think.
For example, it is even better to get the result from others.