chapter9systemsimplementation-資料下載頁
【導(dǎo)讀】SystemsAnalysis&Design. SixthEdition. Chapter9. 2. PhaseDescription. lifecycle(SDLC). testing,documentation,training,data. conversion,systemchangeover,and. results. 3. Introduction. usersmustbetrained,andexistingdata. mustbeconverted. management. 4. ●Qualityassurance. MellonUniversity. costs. maturitylayers(p.417,Fig.9-3). 5. Standardization(ISO). finishedproduct. 6. 7. Steps. –Startbyreviewing. documentationfrom. priorSDLCphasesand. creatingasetof. programdesigns. –Planning(). codeanizedinto. smallunitsthatare. maintain.–Afterthedesignis. created,codingcan. begin. 8. ●ProjectManagement. projectdeadlines,controlcosts,and. maintainquality. techniques. 9. ●Top-downapproach. ●Partitioning. ●Modulardesign. ●Integration. ●Testing. 10. ●StructureCharts. them. –Examplep.421,Figure9-7. 11. ●StructureCharts. modules. –DataCouple:anempty-circlearrow. Flag（旗標(biāo)）。12. StructuredApplic
【正文】 d new systems are inpatible technically – Also is inappropriate when the two systems perform different functions 36 System Changeover ● Pilot Operation – The group that uses the new system first is called the pilot site – The old system continues to operate for the entire anization – After the system proves successful at the pilot site, it is implemented in the rest of the anization, usually using the direct cutover method – Is a bination of parallel operation and direct cutover methods 37 System Changeover ● Phased Operation – You give a part of the system to all users – The risk of errors or failures is limited to the implemented module only – Is less expensive than full parallel operation – Is not possible, however, if the system cannot be separated easily into logical modules or segments 38 PostImplementation Tasks ● PostImplementation Evaluation – Includes feedback for the following areas: ? Accuracy, pleteness, and timeliness of information system output ? User satisfaction ? System reliability and maintainability ? Adequacy of system controls and security measures ? Hardware efficiency and platform performance 39 PostImplementation Tasks ● PostImplementation Evaluation – Includes feedback for the following areas: ? Effectiveness of database implementation ? Performance of the IT team ? Completeness and quality of documentation ? Quality and effectiveness of training ? Accuracy of costbenefit estimates and development schedules 40 PostImplementation Tasks ● PostImplementation Evaluation – When evaluating a system, you should: ? Interview members of management and key users ? Observe users and puter operations personnel actually working with the new information system ? Read all documentation and training materials ? Examine all source documents, output reports, and screen displays ? Use questionnaires to gather information and opinions form a large number of users ? Analyze maintenance and help desk logs 41 PostImplementation Tasks ● PostImplementation Evaluation – Users can fet details of the developmental effort if too much time elapses – Pressure to finish the project sooner usually results in an earlier evaluation in order to allow the IT department to move on to other tasks 42 PostImplementation Tasks ● Final Report to Management – Your report should include the following: ? Final versions of all system documentation ? Planned modifications and enhancements to the system that have been identified ? Recap of all systems development costs and schedules ? A parison of actual costs and schedules to the original estimates ? Postimplementation evaluation, if it has been performed – Marks the end of systems development work
鄂ICP備17016276號-1