Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Accounting information and reporting systems: Chapter 8 - A. Aseervatham, D. Ariandarajah

Chapter 8: Testing and documenting systems. In this chapter, you will learn: To 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,. | Testing and documenting systems Learning objectives To 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 terms acceptance testing capacity testing prototyping rapid application development system testing unit testing Acceptance testing Testing by users before a system goes live to prevent expensive corrections or reconstruction Rapid application performance testing (RAPT): allows developers and users to test system modules as they are developed Prototyping: when a working model of a system is built for testing purposes Acceptance testing Unit testing: testing each stage of in-house software packages as they are developed System testing: primarily carried out by programmers in the development environment Operational environment testing: ‘user acceptance testing’ generally done just before the processing begins but after the system is in the real-life environment Documentation Documents created after systems are tested and accepted can be categorised into: Program documentation shows the coding relationships and comments made by programmers System documentation used to detail the system’s design specifications, internal workings and functionality Documentation (cont.) User documentation documentation that users can refer to for information about procedures (e.g. ‘wizards’ and cue cards) Operations documentation operator’s manual; mainly applies to mainframe computer systems User satisfaction with documentation User 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 . | Testing and documenting systems Learning objectives To 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 terms acceptance testing capacity testing prototyping rapid application development system testing unit testing Acceptance testing Testing by users before a system goes live to prevent expensive corrections or reconstruction Rapid application performance testing (RAPT): allows developers and users to test system modules as they are developed Prototyping: when a working model of a system is built for testing purposes Acceptance testing Unit testing: testing each stage of in-house software packages as .