Quiz 13: System Implementation

After maintenance,the implementation phase of the systems development life cycle is the most expensive and time-consuming phase of the entire life cycle.

Documentation is one of the six major activities associated with systems implementation.

Test planning is often done during systems design.

The development of a new version of the software and new versions of all design documents are the major deliverables associated with the coding,testing,and installation stage.

The systems administration plan answers such questions as when and where the new system will be installed,what people and resources are required,which data will be converted and cleansed,and how long the installation process will take.

Information systems personnel and end users are the two audiences for the final systems documentation.

System and user documentation,a user training plan,user training modules,and a user support plan are deliverables for documenting the system,training,and supporting users.

A master test plan is developed during design.

Testing managers are responsible for developing test plans,establishing testing standards,integrating testing and development activities in the life cycle,and ensuring that test plans are completed.

During an inspection test,exactly what the code does is investigated.

The purpose of a walkthrough is to detect and correct errors.

Walkthroughs are a very effective method for identifying errors in code.

Desk checking is a testing technique in which the program code is sequentially executed manually by the reviewer.

Unit testing does not require automated code execution.

A systems analyst or programmer typically does syntax checking.

System testing is the process of bringing together all of the modules that a program comprises for testing purposes.

Integration testing brings together all of the programs that a system comprises for testing purposes.

Unit testing is 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.

System testing is intended to demonstrate whether a system meets its requirements.

The focus of integration testing is on the interrelationships among modules.

A test case is a specific scenario of transactions,queries,or navigation paths that represent a typical,critical,or abnormal use of the system.

The people who create the test cases should be the same people who have coded and will test the system.

A symbolic debugger allows a program to be run online,allowing the programmer to observe how different areas of data are affected as the instructions are executed.

Software testing tools can compare the results of one test run with those from prior test cases to identify errors or to highlight the results of new features.

During alpha testing users test a completed information system using simulated data.

Automated testing can improve the quality of software testing and reduce the time for software testing by allowing unattended,or repeated,script playing to simulate high-volume or stress situations.

During beta testing,users test a completed information system using real data in the real user environment.

During recovery testing,the analysts try to break the system.

During stress testing,the analysts try to determine how the system performs on the range of possible environments on which it may be used.

The purpose of system testing is to determine whether the software,documentation,technical support,and training activities work as intended.

Installation is the organizational process of changing over from the current information system to a new one.

The coexistence of the old and new systems is characteristic of the parallel installation approach.

The key advantage of a direct installation is that it limits potential damage and potential cost by limiting the effects to a single site.

A positive aspect of the direct installation approach is that there is a high interest in making installation a success.

A positive aspect of the phased installation approach is that learning can occur and problems can be fixed by concentrating on one site.

A positive aspect of the phased installation approach is that it limits potential harm and costs from system error or failure to certain business activities or functions.

Installation is an organizational change process.

According to Bell and Evans,the resource requirement specification is finalized during systems development phase.

According to Bell and Evans,the release description is finalized during the detailed design and implementation stage of the systems development generic life cycle phase.

System documentation is the detailed information about a system's design specifications,its internal workings,and its functionality.

Internal documentation is system documentation that includes the outcome of structured diagramming techniques such as data flow and entity-relationship diagrams.

A system administrator's guide is an example of external system documentation.

A release description is an example of user documentation.

The purpose of a user's guide is to provide information on how users can use computer systems to perform specific tasks.

An acceptance sign-off allows users to test for proper system installation and then signify their acceptance of the new system with their signatures.

Network architecture refers to all the resources and practices required to help people adequately use computer systems to do their primary work.

Many organizations tend to underinvest in computing skills training.

The extent to which a system is used and the user's satisfaction with the system are two ways to determine if implementation has been successful.

User demographics,performance,and satisfaction are factors that influence the extent to which a system is used.

After maintenance,which of the following is the most expensive and most time consuming phase of the entire life cycle? A)implementation B)physical design C)logical design D)analysis.

Which of the following affect the implementation process? A)the work habits of an organization's members B)the personal goals of an organization's members C)the beliefs of an organization's members D)all of the above

The purpose of coding,testing,and installation is to: A)transform the logical specifications of the system into technology specific details from which all programming and system construction can be done B)convert the physical system specifications into working and reliable software and hardware,document the work that has been done,and provide help for current and future users and caretakers of the system C)systematically repair and improve the information system D)study and propose alternative replacement systems

Who is responsible for ensuring that coding,testing,and installation are properly planned and executed? A)programmers B)management C)systems analysts D)end-users

The process whereby the physical design specifications created by the analysis team is turned into working computer code is referred to as: A)coding B)testing C)implementation D)analysis

Which of the following statements is true regarding testing? A)The coding process should be completed,and then the testing process can begin. B)Once coding has begun,the testing process can begin and proceed in parallel. C)The testing process is performed first,then the coding process begins. D)None of the above.

The process in which the current system is replaced by the new system best describes: A)the systems development life cycle B)installation C)physical design D)set-up

The deliverables for coding,testing,and installation are: A)the creation of a document that will consolidate the information that must be considered when implementing a physically distributed systems design B)structured descriptions and diagrams that outline the logic contained within each DFD process C)the code,program documentation,test scenarios and test data,results of program and system testing,user guides,user training plan,and an installation and conversion plan D)a system service request,a statement of work,and a baseline project plan

A strategy for training users so they can quickly learn the new system is a(n): A)training plan B)installation plan C)user guide D)training curriculum

Training on the use of the system begins during the early stages of the: A)analysis phase B)logical design phase C)implementation phase D)project initiation and planning phase

This plan lays out a strategy for moving from the old system to the new,from the beginning to end of the process: A)baseline project plan B)installation plan C)training plan D)testing plan

A master test plan is developed during: A)implementation B)analysis C)logical design D)physical design

Which of the following are testing managers responsible for? A)developing testing plans B)integrating testing and development activities in the life cycle C)establishing testing standards D)all of the above

The type of testing that does not execute the code is called: A)static testing B)dynamic testing C)referential testing D)manual testing

The results of running the code are not an issue for this particular type of test: A)static testing B)dynamic testing C)referential testing D)none of the above

The type of testing that involves the execution of code is called: A)code testing B)static testing C)dynamic testing D)execution testing

A testing technique in which participants examine program code for predictable language-specific errors defines: A)walkthrough B)inspections C)desk checking D)syntax checking

The type of testing responsible for determining what the code does is: A)walkthrough B)inspection C)system testing D)syntax checking

A testing technique in which the program code is sequentially executed manually by the reviewer is referred to as: A)inspection B)system testing C)desk checking D)syntax checking

Testing each module alone in an attempt to discover any errors that may exist in the module's code is referred to as: A)unit testing B)system testing C)stub testing D)singular testing

The process of bringing together all of the modules that comprise a program for testing purposes is referred to as: A)unity testing B)integration testing C)system testing D)implementation

The bringing together of all the programs that comprise a system for testing describes: A)unity testing B)integration testing C)system testing D)implementation

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 describes: A)module testing B)unit testing C)top-down testing D)stub testing

The purpose of acceptance testing is to: A)determine if new requirements must be added to the newly completed system B)determine if the system meets user requirements C)determine if the system meets its objectives D)do none of the above

The most complete acceptance testing will include: A)alpha testing B)beta testing C)a system audit D)all of the above

The process whereby actual users test a completed information system,the end result of which is the users' acceptance of it,best describes: A)acceptance testing B)alpha testing C)beta testing D)system testing

User testing of a completed information system using simulated data refers to: A)acceptance testing B)alpha testing C)beta testing D)system testing

User testing of a completed information system using real data in the real user environment refers to: A)acceptance testing B)alpha testing C)beta testing D)system testing

Which of the following are designed during alpha testing and try to break the system? A)stress tests B)performance tests C)recovery tests D)security tests

The organizational process of changing over from the current information system to a new one best defines: A)reorganization B)physical design C)installation D)replacement

Changing over from the old information system to a new one by turning off the old system as the new one is turned on best describes: A)phased installation B)single location installation C)parallel installation D)direct installation

Running the old information system and the new one at the same time until management decides the old system can be turned off best describes: A)parallel installation B)single-location installation C)phased installation D)direct cutover installation

During which of the following generic life-cycle phases would a user's guide be produced? A)requirements specification B)project control structuring C)system development D)system delivery

During which of the following generic life-cycle phases would a management plan be produced? A)requirements specification B)project control structuring C)system development D)system delivery

All of the following are types of user documentation except: A)release description B)reference guide C)acceptance sign-off D)management plan

System documentation is intended primarily for: A)maintenance programmers B)end users C)systems analysts D)system operators

Written or other visual information about an application system,how it works,and how to use it best defines: A)system documentation B)user documentation C)internal documentation D)external documentation

System documentation that is part of the program source code or is generated at compile time best defines: A)program statements B)user documentation C)internal documentation D)external documentation

System documentation that includes the outcome of structured diagramming techniques such as data flow and entity-relationship diagrams best defines: A)system documentation B)user documentation C)internal documentation D)external documentation

Which of the following is an exhaustive list of the system's functions and commands,usually in alphabetical order? A)reference guide B)user's guide C)release description D)system administrator's guide

This type of user documentation contains information about a new system release,including a list of complete documentation for the new release,features and enhancements,known problems and how they have been dealt with in the new release,and information about installation: A)reference guide B)user's manual C)release description D)system administrator's guide

This type of user documentation is intended primarily for those who will install and administer a new system and contains information about the network on which the system will run,software interfaces for peripherals such as printers,troubleshooting,and setting up user accounts: A)external documentation B)user's manual C)system documentation D)system administrator's guide

This type of user documentation allows users to test for proper system installation and then signify their acceptance of the new system with their signatures: A)acceptance sign-off B)user contract C)RFP D)system verification

Most user documentation is now delivered: A)on-line,in hypertext format B)through paper manuals C)by calling technical support numbers D)through help desks

Which of the following statements is true about intermittent users? A)Support mechanisms are a good way to provide training for intermittent users of a system. B)Intermittent users are not interested in,nor would they profit from,typical user training methods. C)Intermittent users must be provided "point of need support." D)All of the above.

Potential topics that will determine if training will be useful include the following except for: A)system documentation B)general computer concepts C)information system concepts D)system management

Potential topics that will determine if training will be useful include: A)use of the system B)general computer concepts C)information system concepts D)all of the above

A component of a software package or application in which training and educational information is embedded best defines: A)resident expert B)computer-aided instruction C)electronic tutorial D)electronic performance support system

__________ are a testing technique in which participants examine program code for predictable language-specific errors.

__________ is a testing technique in which the program code is sequentially executed manually by the reviewer.

__________ is 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.

In __________,each module is tested alone in an attempt to discover any errors in its code.

__________ is the process of bringing together all of the modules that a program comprises for testing purposes; the modules are typically integrated in a top-down,incremental fashion.

__________ is the process of bringing together all of the programs that a system comprises for testing purposes; programs are typically integrated in a top-down,incremental fashion.

__________ is the process whereby actual users test a completed information system,the end result of which is the user's acceptance of it.

__________ refers to user testing of a completed information system using simulated data.

__________ refers to user testing of a completed information system using real data in the real user environment.

__________ is the organizational process of changing over from the current information system to a new one.

__________,__________,__________,and __________ are the four approaches to installation.

__________ refers to changing over from the old information system to a new one by turning off the old system when the new one is turned on.

__________ refers to running the old information system and the new one at the same time until management decides the old system can be turned off.

__________ refers to trying out a new information system at one site and using the experience to decide if and how the new system should be deployed throughout the organization.

__________ refers to 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.

__________ and user documentation are the two basic types of documentation.

__________ is the detailed information about a system's design specifications,its internal workings,and its functionality.

__________ is system documentation that is part of the program source code or is generated at compile time.

__________ is system documentation that includes the outcome of structured diagramming techniques such as data flow and entity-relationship diagrams.

__________ is written or other visual information about an application system,how it works,and how to use it.

__________ refers to providing ongoing educational and problem-solving assistance to information system users.

An __________ is a component of a software package or application in which training and educational information is embedded.

A __________ is a single point of contact for all user inquiries and problems about a particular information system or for all users in a particular department.

The basis for __________ is that individuals who work in an organization have their own self-interested goals.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Changing over from the old information system to a new one incrementally,starting with one or a few functional components and then gradually extending the installation to cover the whole new system.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -The process of bringing together all of the modules that comprise a program for testing purposes.The modules are typically integrated in a top-down,incremental fashion.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -User testing of a completed information system using simulated data.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -The organizational process of changing over from the current information system to a new one.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Trying out a new information system at one site and using the experience to decide if and how the new system should be deployed throughout the organization.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -A testing technique in which the program code is sequentially executed manually by the reviewer.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Running the old information system and the new one at the same time until management decides the old system can be turned off.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Changing over from the old information system to a new one by turning off the old system as the new one is turned on.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -A testing technique in which participants examine program code for predictable language-specific errors.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Providing ongoing educational and problem-solving assistance to information systems users.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -The process whereby actual users test a completed information system,the end result of which is the users' acceptance of it.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -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.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -User testing of a completed information system using real data in the real user environment.

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Unit test

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Syntax checking

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Walkthroughs

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Desk checking

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Integration test

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -Inspections

Match each of the following terms with its corresponding definition. a.acceptance testing b.alpha testing c.beta testing d.desk checking e.direct installation f.inspections g.installation h.integration testing i.parallel installation j.phased installation k.single location installation l.stub testing m.support -System test

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -This type of testing verifies protection mechanisms built into the system will protect it from improper penetration.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -User testing of a completed information system using real data in the real user environment.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -The process whereby actual users test a completed information system,the end result of which is the users' acceptance of it.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -This type of testing determines how the system performs on the range of possible environments in which it may be used.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -This type of test tries to break the system.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -The process of bringing together all of the modules that comprise a program for testing purposes.Modules are typically integrated in a top-down,incremental fashion.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -This type of test forces the software (or environment)to fail in order to verify that recovery is properly performed.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -User testing of a completed information system using simulated data.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance 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.

Match each of the following types of testing with its corresponding description. a.integration testing b.system testing c.stub testing d.acceptance testing e.alpha testing f.beta testing g.recovery testing h.security testing i.stress testing j.performance testing -The bringing together of all the programs that a system comprises for testing purposes; programs are typically integrated in a top-down,incremental fashion.

Match each of the following terms with its corresponding description. a.direct installation b.installation c.parallel installation d.phased installation e.single location installation -Running the old information system and the new one at the same time until management decides the old system can be turned off.

Match each of the following terms with its corresponding description. a.direct installation b.installation c.parallel installation d.phased installation e.single location installation -The organizational process of changing over from the current information system to a new one.

Match each of the following terms with its corresponding description. a.direct installation b.installation c.parallel installation d.phased installation e.single location installation -Trying out a new information system at one site and using the experience to decide if and how the new system should be deployed throughout the organization.

Match each of the following terms with its corresponding description. a.direct installation b.installation c.parallel installation d.phased installation e.single location installation -Changing over from the old information system to a new one incrementally,starting with one or a few functional components and then gradually extending the installation to cover the whole new system.

Match each of the following terms with its corresponding description. a.direct installation b.installation c.parallel installation d.phased installation e.single location installation -Changing over from the old information system to a new one by turning off the old system as the new one is turned on.

Briefly identify the four types of installation.

Briefly identify and categorize the seven different types of tests as proposed by Mosley.

Define system documentation,user documentation,internal documentation,and external documentation.

Identify several types of user documentation.

Briefly identify the tasks associated with closing down the project.

What are the six factors,identified by Lucas,that influence the extent to which a system is used?

What is a help desk? What are the top two valued skills help desk personnel should have?

What is an electronic performance support system? What forms might this system take?

What factors influence implementation success?

How can you support intermittent users of a system?