Life on COMPUTERS and TECHNOLOGY ^^

System documentation and documentation are two types of documents. System documentation is needed to better understand and maintenance of application software. The user documentation is designed to help the user to operate the system. A document requires high quality design documents, writing and editing, and testing and, therefore, requires more time for documentation. Poor quality of documentation can be produced more quickly. Today, the online documentation is increasingly important, compared to traditional paper manuals. Users are more familiar with the paper and are easier to use. Even if the documents online requires people to become familiar with the controls additional software for finding information is easier in the documents online. They also allow the user to interact with the document.
Unable to perform Translation:invalid textThere are essentially three types of user documentation: reference documents, procedures manuals and tutorials. The references are used when the user needs to learn how a particular function. Manuals of procedure describes how to perform the tasks carried out. Tutorials to teach people to use, how to capture important elements of the system.
Unable to perform Translation:invalid textIntroduction
Unable to perform Translation:invalid textThere are two types of documents.
Unable to perform Translation:invalid textSystem documentation must be intended to help programmers and systems analysts for the application software and enable them to build or maintain once the system is installed. System documentation is a byproduct of system analysis and design process is established and the project goes forward.
Unable to perform Translation:invalid textEach phase and phase to produce documents that are important to understand how the system is constructed or are essential for the construction, and these documents are in draft book (s) is stored.
Unable to perform Translation:invalid textUser documentation (eg user manuals, training manuals and online help systems) was developed to help users in the system. While the majority of users expect to have hosted the project team training and to read the manual before using the system, which unfortunately is not always the case. It is now common practice - especially in the case of commercial software for personal computers - for users, the software, without training or start reading the manual.
Unable to perform Translation:invalid textThe documentation for the user is often up to project completion, which remains a dangerous strategy. The development of good documentation is longer than many expect, because it requires writing a lot more than a few pages.
Unable to perform Translation:invalid textCompiling the necessary project documentation (paper or online), wrote the text, the modification and test. For the good quality of documentation, this process takes approximately 3 hours per page of paper (single spaced) to the paperwork, or 2 hours of screen for on-line documentation.
Unable to perform Translation:invalid textThus, a "simple" part of the documentation on how to take a 20-page manual and a series of 20 screens, with 100 hours. Of course, the documentation of inferior quality can be produced more quickly.
Unable to perform Translation:invalid textThe time required to develop and test the user documentation must be produced in the project plan. Most companies plan to begin the documentation of the development, once the design specifications of the interface and the program is complete. The original draft of the documentation is usually completed immediately after the unit tests have been completed in the program.
Unable to perform Translation:invalid textThis will reduce - but not eliminate - the need for the documents reviewed and revised before the test begins.
Unable to perform Translation:invalid textAlthough the printed manuals are still important, is the on-line documentation is increasingly important. Documentation of paper is easier to use because it is familiar to users, especially for beginners who have less familiarity with computers, on-line documentation, the user needs to learn more orders. The paperwork is easier to scroll in order to gain a general understanding of their organization and problems, and may be away from the computer itself uses.
Unable to perform Translation:invalid textUnable to perform Translation:invalid result dataUnable to perform Translation:invalid textThird, the documentation on-line allows the user to interact with the material. For example, you can connect or "Tooltips" (ie, using pop-up text) to explain unfamiliar terms and a programmer can write "Show Me" routine on the screen to show exactly what buttons to choose and how to enter text . Finally, the documentation on-line much cheaper to deploy and maintain documentation on paper.
Unable to perform Translation:invalid textTypes of documentation
Unable to perform Translation:invalid textThere are basically three different types of user documentation: reference documents, procedures manuals and tutorials. Reference materials (also as a support system) should be used when the user learns to respond to a particular function (eg printing of a monthly report that need to take an order by the customer). Typically, people read the reference information after you have tried and perform any function. Write the reference material requires special attention, because users are often impatient or frustrated when they begin to read.
Unable to perform Translation:invalid textProcedures manuals describe how companies perform the tasks (eg printing a monthly report, with) an order for the customer. Each point in the process of hand that guides the user through a task that requires several functions or steps in the system. Therefore, each entry is generally much longer than an entry in a reference document.
Unable to perform Translation:invalid textTutorials to teach people to use as a), are important components of the system (as an introduction to the basic functions of the system. Each entry in the tutorial is generally longer than the companies in the manuals of procedures and structures are viewed as a rule use in order so that the messages contained in the documents of reference and procedure manuals should be viewed individually.
Unable to perform Translation:invalid textWhatever the type of user documentation, the entire development process is similar to the process of developing interface. The developer of the first projects of the overall structure of the documentation, then develops the components within this group.
Unable to perform Translation:invalid textDocumentation and document management on the corporate intranet are key to a company, and has spent the resources, it is worth. For more information on these topics, and training activities related to the analysis and data modeling training Bangalore