Kế toán, kiểm toán - Testing and documenting systems

Testing and documenting systemsLearning objectivesTo understand the need for testing a computer system in an operational environment.To discover the different types of testing.To learn about documenting a system before implementation and training.To learn about the different media used for documentation.To understand why it is necessary to consult users to ensure acceptability of documentation.To learn about reviewing and updating documentation to ensure currency and accuracy.key termsacceptance testingcapacity testingprototypingrapid application developmentsystem testingunit testingAcceptance testingTesting by users before a system goes live to prevent expensive corrections or reconstructionRapid application performance testing (RAPT):allows developers and users to test system modules as they are developedPrototyping:when a working model of a system is built for testing purposesAcceptance testingUnit testing:testing each stage of in-house software packages as they are developedSystem testing:primarily carried out by programmers in the development environmentOperational environment testing:‘user acceptance testing’ generally done just before the processing begins but after the system is in the real-life environmentDocumentationDocuments created after systems are tested and accepted can be categorised into:Program documentationshows the coding relationships and comments made by programmersSystem documentationused to detail the system’s design specifications, internal workings and functionalityDocumentation (cont.)User documentationdocumentation that users can refer to for information about procedures (e.g. ‘wizards’ and cue cards)Operations documentationoperator’s manual; mainly applies to mainframe computer systemsUser satisfaction with documentationUser documentation should cater for all types of users and consideration should be given to: the level of language (should be simple and non-technical)the learning capacity of usersthe fact that the level of experience for users will differthe fact that work styles and habits of users will differ (e.g. some will prefer to use a mouse, others will prefer keystroke commands)Maintenance of documentationDocumentation should be easily accessible to usersNeeds to be kept updated and currentA register for paper documentation should be maintained to identify the location of copies and ensure changes are made to all copies