Anyone who uses application software needs accurate information about how the software will help the user accomplish a task. The documentation may be the first tangible item that the user sees and therefore influences the user’s first impressions of the software product. If the information is supplied in a convenient form and is easy to find and understand, the user can quickly become proficient at using the product. Hence, well-designed documentation not only assists the user and helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers.
Documentation is often regarded as something done after the software has been implemented. However, for high-quality software documentation, its development should be regarded as an integral part of the software life cycle process. If done properly, documentation or information management is a big enough job to require process planning in its own right.
BS ISO/IEC 26514 is the International Standard developed to assist users of BS ISO/IEC 15288:2002 Systems engineering. System life cycle processes , or BS ISO/IEC 12207:2008 Systems and software engineering. Software life cycle processes , to design and develop documentation as part of the software life cycle processes. It defines the documentation process from the documentation developer's standpoint.
BS ISO/IEC 26514 supports the interest of software users in consistent, complete, accurate, and usable documentation. It includes both approaches to standardization: a) process standards, which specify the way in which documentation products are to be developed; and b) documentation product standards...