chapter9systemsimplementation

chapter9systemsimplementation内容摘要：

rect and erroneous data – Stub testing: simulation of each oute by displaying a message so that it is easier to link with another program later – Regardless of who creates the test plan, the project manager or a designated analyst also reviews the final test results 19 Testing the System ● Integration Testing – Integration testing, or link testing – Testing the programs independently does not guarantee that the data passed between them is correct – A testing sequence should not move to the integration stage unless it has performed properly in all unit tests 20 Testing the System ● System Testing – Aka Acceptance tests – Major objectives: • Perform a final test of all programs • Verify that the system will handle all input data properly, both valid and invalid • Ensure that the IT staff has the documentation and instructions needed to operate the system properly and that backup and restart capabilities of the system are adequate 21 Testing the System ● System Testing – Major objectives: • Demonstrate that users can interact with the system successfully • Verify that all system ponents are integrated properly and that actual processing situations will be handled correctly • Confirm that the information system can handle predicted volumes of data in a timely and efficient manner 22 Documentation ● Documentation ● Program Documentation ● System Documentation: data dictionary, DFD,… ● Operations Documentation: scheduling info for printed output, etc. ● User Documentation – Online documentation, eg. FAQ’s 23 Management Approval ● After system testing is plete, you present the results to management ● If system testing produced no technical, economical, or operational problems, management determines a schedule for system installation and evaluation 24 System Installation and Evaluation ● Remaining steps in systems implementation: – Prepare a separate operational and test environment – Provide training for users, managers, and IT staff – Perform data conversion and system changeover – Carry out postimplementation evaluation of the system – Present a final report to management 25 Operational and Test Environments ● The environment for the actual system operation is called the operational environment or production environment ● The environment that analysts and programmers use to develop and maintain programs is called the test environment ● A separate test environment is necessary to maintain system security and integrity and protect the operational environment 26 Operational and Test Environments 27 Training ● Training Plan – The first step is to identify who should receive training and what training is needed – The three。