The document discusses the importance of documentation for system analysis. It states that documentation is used to communicate information about a system and track its progress. It then lists several uses of documentation, including facilitating communication, training new users, troubleshooting, evaluation, and quantifying financial impacts. The document also discusses methods of documentation and notes that the basic importance is to learn from past experiences to improve future evaluations and modifications. It concludes that documentation is an important but often ignored part of the system development life cycle.

1. IMPORTANCE OF DOCUMENTATION TO SYSTEM ANALYSIS Group X System Administration and Design Level 300 FEHAC/DIT

2. INTRODUCTION Documentation is one of the system’s which are used to communicate, instruct and record the information for any reference or operational purpose. With the help of documentation it is very easy to track the flow of the system's progress and the workings of the system can be explained very easily.

3. USES It facilitates effective communication regarding the system between the technical and the non technical users.

4. USES It is very useful in training new users

5. USES Documentation also helps the users to solve problems like trouble shooting

6. USES It plays a significant role in evaluation process.

7. USES It not only helps to exercise better control over the internal and external workings of the firm.

8. USES Documentations can help the manager to better quantify the financial ramifications/footprint of the system.

9. METHODS Use of existing documentary material Records Structured interviews of users Case studies Reconstruction of events Field diaries of project staff Video and audio recordings Participant observation of users

10. IMPORTANCE The basic importance of documentation is to help learn from the design, development, implementation and re-evaluation experience which is used to create a record as well as help in future evaluation or modification.

11. IMPORTANCE Documentation of processes helps in creating systematic information to articulate the intervention strategies and develop the flow chart of a system

12. IMPORTANCE Benefit is not only enjoyed by the system evaluated but also other similar projects and can use the outcome as a model in their formulation and implementation methods.

13. IMPORTANCE Documentation is also used by agencies undertaking new and complex forms as part of expansion of systems

14. CONCLUSION Documentation is a much ignored but absolutely important part of every stage in the System Development Life Cycle of any system. A well written and organized documentation makes the work of future system user in any stage easier.

15. REFERENCES Software System Document Process Maturity Model – Marcello Visconti, Curtis Cook; Computer Science Department, Oregon State University The Benefit of Business Analysis – www.mordernanalyst.com Systems Design – www.wikipedia.com Business Analyst – www.wikipedia.com Change Management Analyst – www.wikipedia.com Systems Analyst – www.wikipedia.com System Analysis – www.wikipedia.com Structured System Analysis and Design Method – www.wikipedia.com Business Analysis – www.wikipedia.com The Cranky User: The Importance ofDocumentation – Peter Seebach; http://www.ibm.com/developerWorks/ Trials & Tribulations of a Business Systems Analyst – http://it.toolbox.com/blogs/business-analyst/ Documentation and Importance of Documentation – http://systemanalysisanddesign.blogspot.com/2008/11/documentation-and-importance-of.html Software Documentation – www.literateprogramming.com Software and Documentation – Ian Kaplan; http://www.bearcave.com/index.shtml