1.1.8_to_1.1.10_-User_Focus
1.1.8_to_1.1.10_-User_Focus
1.1.8_to_1.1.10_-User_Focus
1.1.8 TO 1.110
The importance of user
documentation
As programs become more complex and
detailed the users way of thinking may differ
from the developers.
This may lead to serious problems during the
implementation or operational stage of the
Software Life Cycle (SLC).
The user might not know how to use the
product to its full capacity, and even specialized
technicians may not be able to set up the new
system properly for the firm they work for.
This is where there is a need for an effective
and detailed instruction manual highlighting all
components of the program.
The importance of user documentation - Internal
At this stage it is important to determine the difference between internal and external documentation
Internal documentation is the code comprehension features and details provided as part of the source code
itself. Proper internal documentation includes:
Appropriate module headers
Appropriate comments
Useful and meaningful variable names
Useful module, classes, methods and function headers
Appropriate code indentation
Appropriate code structuring
Appropriate use of enumerated types
Appropriate use of constant identifiers
Appropriate use of data types defined by the user
It is very difficult and likely to be
impossible for the source code
to be read by the final user.
The importance of user
documentation - External
External documentation is typically written
as a separate document from the program
itself.
It is provided through various types of user
supporting documents such as a users' guides,
software requirements specification, detailed
description of the design and implementation
features of the program and test document.
Different
methods of User documentation can The user documentation The document should be