際際滷

際際滷Share a Scribd company logo

Sad chap10

Download as PPT, PDF
A
Azlan Zain

The document discusses the key activities involved in systems implementation and operation: coding, testing, installation, documentation, training, support, and maintenance. It describes the different types of tests performed at various stages, such as unit testing, integration testing, and acceptance testing. It also outlines the different strategies for installing new systems, such as direct installation, parallel installation, single-location installation, and phased installation. The goal of implementation is to convert system specifications into working software, document the work, and provide help for current and future users.

1 of 27
Download to read offline
Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 10 Systems Implementation and Operation 10.1 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall
System Implementation and Operation 10.2 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall
System Implementation and Operation Seven major activities Coding Testing Installation Documentation Training Support Maintenance Purpose To convert final physical system specifications into working and reliable software To document work that has been done To provide help for current and future users 10.3 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall
The Processes of Coding, Testing, and Installation: Deliverables
Seven Different Types of Tests Inspection: a testing technique in which participants examine program code for predictable language-specific errors Walkthrough: a peer group review of any product created during the systems development process, including code Desk checking: a testing technique in which the program code is sequentially executed manually by the reviewer
Seven Different Types of Tests (Cont.) Unit testing: each module is tested alone in an attempt to discover any errors in its code Integration testing: the process of bringing together all of the modules that a program comprises for testing purposes Modules are typically integrated in a top-down incremental fashion.
Seven Different Types of Tests (Cont.) System testing: the bringing together of all of the programs that a system comprises for testing purposes Programs are typically integrated in a top- down, incremental fashion.
Seven Different Types of Tests (Cont.) Stub testing: a technique used in testing modules, especially where modules are written and tested in a top- down fashion, where a few lines of code are used to substitute for subordinate modules
Acceptance Testing by Users Acceptance testing: the process whereby actual users test a completed information system, the end result of which is the users acceptance of it
Acceptance Testing by Users (Cont.) Alpha testing: user testing of a completed information system using simulated data Beta testing: user testing of a completed information system using real data in the real user environment
Acceptance Testing by Users (Cont.) Types of Alpha Test: Recovery testing forces software (or environment) to fail in order to verify that recovery is properly performed Security testing verifies that protection mechanisms built into the system will protect it from improper penetration Stress testing tries to break the system Performance testing determines how the system performs on the range of possible environments in which it may be used
Installation Installation: the organizational process of changing over from the current information system to a new one Four installation strategies: Direct Installation Parallel Installation Single-location installation 息 2011 PearsonPhased Installation Education, Inc. Publishing as Prentice Hall 12 Chapter 13
Direct Installation Direct installation: changing over from the old system to a new one by turning off the old system when the new system is turned on 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 13 Chapter 13
Parallel Installation Parallel installation: running the old information system and the new one at the same time until management decides the old system can be turned off 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 14 Chapter 13
Single-Location Installation Single-location installation: trying out an information system at one site and using the experience to decide if and how the new system should be deployed throughout the organization Also known as location or pilot installation 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 15 Chapter 13
Single-Location Installation (cont.) 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 16 Chapter 13
Phased Installation Phased Installation: changing from the old information system to the new one incrementally, starting with one or a few functional components and then gradually extending the installation to cover the whole new system 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 17 Chapter 13
Phased Installation (cont.) 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 18 Chapter 13
Documenting the System System documentation: detailed information about a systems design specifications, its internal workings, and its functionality User documentation: written or other visual information about an application system, how it works, and how to use it 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 19 Chapter 13
Training Information Systems Users Potential training topics Use of the system General computer concepts Information system concepts Organizational concepts System management System installation 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 20 Chapter 13
Types of Training Methods Resident expert Traditional instructor-led classroom training E-learning, distance learning Blended learning (instructor plus e- learning) External sources (e.g. vendors) 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 21 Chapter 13
Supporting Information Systems Users Support is extremely important to users. Providing support can be expensive and time-consuming. 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 22 Chapter 13
Automating Support One approach is through automation. Internet-based online support forums On-demand fax Voice response systems Knowledge bases 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 23 Chapter 13
Providing Support Through a Help Desk Help desk: a single point of contact for all user inquiries and problems about a particular information system or for all users in a particular department 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 24 Chapter 13
Providing Support Through a Help Desk (Cont.) Requires Technical skills: extensive knowledge about how to use the system and typical problems that can be encountered People skills: good listening and communication, dealing with complaints and frustrations 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 25 Chapter 13
Organizational Issues in Systems Implementation Biggest measure of success: Will it be used? Major factors influencing implementation success: Management support User involvement Commitment to project Commitment to change Extent of project definition and planning
Why Implementation Sometimes Fails Implementation success factors Extent to which system is used System ease of use and reliability Users satisfaction with system User demographics, such as age and degree of computer experience 10.27 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall

More Related Content

Sad chap10

  • 1. Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 10 Systems Implementation and Operation 10.1 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall
  • 2. System Implementation and Operation 10.2 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall
  • 3. System Implementation and Operation Seven major activities Coding Testing Installation Documentation Training Support Maintenance Purpose To convert final physical system specifications into working and reliable software To document work that has been done To provide help for current and future users 10.3 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall
  • 4. The Processes of Coding, Testing, and Installation: Deliverables
  • 5. Seven Different Types of Tests Inspection: a testing technique in which participants examine program code for predictable language-specific errors Walkthrough: a peer group review of any product created during the systems development process, including code Desk checking: a testing technique in which the program code is sequentially executed manually by the reviewer
  • 6. Seven Different Types of Tests (Cont.) Unit testing: each module is tested alone in an attempt to discover any errors in its code Integration testing: the process of bringing together all of the modules that a program comprises for testing purposes Modules are typically integrated in a top-down incremental fashion.
  • 7. Seven Different Types of Tests (Cont.) System testing: the bringing together of all of the programs that a system comprises for testing purposes Programs are typically integrated in a top- down, incremental fashion.
  • 8. Seven Different Types of Tests (Cont.) Stub testing: a technique used in testing modules, especially where modules are written and tested in a top- down fashion, where a few lines of code are used to substitute for subordinate modules
  • 9. Acceptance Testing by Users Acceptance testing: the process whereby actual users test a completed information system, the end result of which is the users acceptance of it
  • 10. Acceptance Testing by Users (Cont.) Alpha testing: user testing of a completed information system using simulated data Beta testing: user testing of a completed information system using real data in the real user environment
  • 11. Acceptance Testing by Users (Cont.) Types of Alpha Test: Recovery testing forces software (or environment) to fail in order to verify that recovery is properly performed Security testing verifies that protection mechanisms built into the system will protect it from improper penetration Stress testing tries to break the system Performance testing determines how the system performs on the range of possible environments in which it may be used
  • 12. Installation Installation: the organizational process of changing over from the current information system to a new one Four installation strategies: Direct Installation Parallel Installation Single-location installation 息 2011 PearsonPhased Installation Education, Inc. Publishing as Prentice Hall 12 Chapter 13
  • 13. Direct Installation Direct installation: changing over from the old system to a new one by turning off the old system when the new system is turned on 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 13 Chapter 13
  • 14. Parallel Installation Parallel installation: running the old information system and the new one at the same time until management decides the old system can be turned off 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 14 Chapter 13
  • 15. Single-Location Installation Single-location installation: trying out an information system at one site and using the experience to decide if and how the new system should be deployed throughout the organization Also known as location or pilot installation 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 15 Chapter 13
  • 16. Single-Location Installation (cont.) 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 16 Chapter 13
  • 17. Phased Installation Phased Installation: changing from the old information system to the new one incrementally, starting with one or a few functional components and then gradually extending the installation to cover the whole new system 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 17 Chapter 13
  • 18. Phased Installation (cont.) 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 18 Chapter 13
  • 19. Documenting the System System documentation: detailed information about a systems design specifications, its internal workings, and its functionality User documentation: written or other visual information about an application system, how it works, and how to use it 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 19 Chapter 13
  • 20. Training Information Systems Users Potential training topics Use of the system General computer concepts Information system concepts Organizational concepts System management System installation 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 20 Chapter 13
  • 21. Types of Training Methods Resident expert Traditional instructor-led classroom training E-learning, distance learning Blended learning (instructor plus e- learning) External sources (e.g. vendors) 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 21 Chapter 13
  • 22. Supporting Information Systems Users Support is extremely important to users. Providing support can be expensive and time-consuming. 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 22 Chapter 13
  • 23. Automating Support One approach is through automation. Internet-based online support forums On-demand fax Voice response systems Knowledge bases 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 23 Chapter 13
  • 24. Providing Support Through a Help Desk Help desk: a single point of contact for all user inquiries and problems about a particular information system or for all users in a particular department 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 24 Chapter 13
  • 25. Providing Support Through a Help Desk (Cont.) Requires Technical skills: extensive knowledge about how to use the system and typical problems that can be encountered People skills: good listening and communication, dealing with complaints and frustrations 息 2011 Pearson Education, Inc. Publishing as Prentice Hall 25 Chapter 13
  • 26. Organizational Issues in Systems Implementation Biggest measure of success: Will it be used? Major factors influencing implementation success: Management support User involvement Commitment to project Commitment to change Extent of project definition and planning
  • 27. Why Implementation Sometimes Fails Implementation success factors Extent to which system is used System ease of use and reliability Users satisfaction with system User demographics, such as age and degree of computer experience 10.27 Copyright 息 2009 Pearson Education, Inc. Publishing as Prentice Hall