Part 1
A. There are several techniques used in the documentation process. As a system analyst I would propose to the members of this group a straightforward standardized approach. A reasonable suggestion for this project would be to use the Procedure Manual technique for documenting this system. The Procedure Manuals will provide instructions on how to operate and understand how the system works. These manuals are also used as a guide that can be updated at different intervals for future users. Procedure Manuals are also made available to users via the Web. This new approach has made it convenient for users to seek support in a much faster way by offering a FAQ page, and online chat (Kendall & Kendall, 2011). In addition it is also a great tool for future analyst.
B. The Procedure Manual should help with the many concerns that members of the group have because it will allow a person from each department to construct a standard procedure manual for their department. Each department will be allowed to create a step by step process to make the procedure manual understandable. In order to avoid errors another member of the department will be allowed to review the steps to make corrections, after which the department will have to approve the documentation. Once each department has created a standard procedure manual the group should then meet to compare and make sure there are no gaps and no missing information. One procedure manual should then be created and dated when it was written and approved. In addition, this technique will help streamline all the different inconsistencies that the group members have by allowing them to create their own departmental procedure manual (Deloach, 2013).
C. Documenting is a very important part of total quality assurance. Good documenting benefits the entire organization. It provides a roadmap for designers, users, and analyst. Also, it serves as a reference for the system. “Software, systems, formal and