IMPORTANCE OF DOCUMENTATION TO SYSTEM ANALYSISGroup XSystem Administration and DesignLevel 300 FEHAC/DIT
INTRODUCTIONDocumentation 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.
USESIt facilitates effective communication regarding the system between the technical and the non technical users.
USESIt is very useful in training new users
USESDocumentation also helps the users to solve problems like trouble shooting
USESIt plays a significant role in evaluation process.
USESIt not only helps to exercise better control over the internal and external workings of the firm.
USESDocumentations can help the manager to better quantify the financial ramifications/footprint of the system.
METHODSUse of existing documentary material RecordsStructured interviews of usersCase studiesReconstruction of eventsField diaries of project staffVideo and audio recordingsParticipant observation of users
IMPORTANCEThe 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.
IMPORTANCEDocumentation of processes helps in creating systematic information to articulate the intervention strategies and develop the flow chart of a system
IMPORTANCEBenefit 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.
IMPORTANCEDocumentation is also used by agencies undertaking new and complex forms as part of expansion of systems
CONCLUSIONDocumentation 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.
REFERENCESSoftware System Document Process Maturity Model – Marcello Visconti, Curtis Cook; Computer Science Department, Oregon State UniversityThe Benefit of Business Analysis – www.mordernanalyst.comSystems Design – www.wikipedia.comBusiness Analyst – www.wikipedia.comChange Management Analyst – www.wikipedia.comSystems Analyst – www.wikipedia.comSystem Analysis – www.wikipedia.comStructured System Analysis and Design Method – www.wikipedia.comBusiness Analysis – www.wikipedia.comThe 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.htmlSoftware Documentation – www.literateprogramming.comSoftware and Documentation – Ian Kaplan; http://www.bearcave.com/index.shtml

Importance of documentation to system analysis

  • 1.
    IMPORTANCE OF DOCUMENTATIONTO SYSTEM ANALYSISGroup XSystem Administration and DesignLevel 300 FEHAC/DIT
  • 2.
    INTRODUCTIONDocumentation is oneof 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.
    USESIt facilitates effectivecommunication regarding the system between the technical and the non technical users.
  • 4.
    USESIt is veryuseful in training new users
  • 5.
    USESDocumentation also helpsthe users to solve problems like trouble shooting
  • 6.
    USESIt plays asignificant role in evaluation process.
  • 7.
    USESIt not onlyhelps to exercise better control over the internal and external workings of the firm.
  • 8.
    USESDocumentations can helpthe manager to better quantify the financial ramifications/footprint of the system.
  • 9.
    METHODSUse of existingdocumentary material RecordsStructured interviews of usersCase studiesReconstruction of eventsField diaries of project staffVideo and audio recordingsParticipant observation of users
  • 10.
    IMPORTANCEThe basic importanceof 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.
    IMPORTANCEDocumentation of processeshelps in creating systematic information to articulate the intervention strategies and develop the flow chart of a system
  • 12.
    IMPORTANCEBenefit is notonly 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.
    IMPORTANCEDocumentation is alsoused by agencies undertaking new and complex forms as part of expansion of systems
  • 14.
    CONCLUSIONDocumentation is amuch 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.
    REFERENCESSoftware System DocumentProcess Maturity Model – Marcello Visconti, Curtis Cook; Computer Science Department, Oregon State UniversityThe Benefit of Business Analysis – www.mordernanalyst.comSystems Design – www.wikipedia.comBusiness Analyst – www.wikipedia.comChange Management Analyst – www.wikipedia.comSystems Analyst – www.wikipedia.comSystem Analysis – www.wikipedia.comStructured System Analysis and Design Method – www.wikipedia.comBusiness Analysis – www.wikipedia.comThe 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.htmlSoftware Documentation – www.literateprogramming.comSoftware and Documentation – Ian Kaplan; http://www.bearcave.com/index.shtml