Q&A Hero

Q: Identify four types of installation.

Q: Identify four types of maintenance.

Q: Identify several types of user documentation.

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

Q: Which of the following influences most of the costs associated with maintaining a system? A) Maintenance personnel B) Documentation quality C) Number of latent defects D) Number of customers E) Tools

Q: Which of the following maintenance cost elements is the most significant? A) Tools B) Software structure C) Personnel D) Number of customers E) Hardware

Q: Which of the following typically would be assigned the highest priority? A) Preventive maintenance B) Perfective maintenance C) Corrective maintenance D) Adaptive maintenance E) Evolutionary maintenance

Q: Evolving the system to add new features or improve performance best describes: A) corrective maintenance. B) adaptive maintenance. C) preventive maintenance. D) perfective maintenance. E) evolutionary maintenance.

Q: Changes made to a system to evolve its functionality to changing business needs or technologies are referred to as: A) corrective maintenance. B) adaptive maintenance. C) preventive maintenance. D) perfective maintenance. E) environmental maintenance.

Q: Changes made to a system to repair flaws in its design, coding, or implementation describes: A) corrective maintenance. B) adaptive maintenance. C) preventive maintenance. D) perfective maintenance. E) programmatic maintenance.

Q: Changes made to a system to fix or enhance its functionality best defines: A) maintenance. B) support. C) repair. D) installation. E) coding.

Q: Which of the following types of maintenance accounts for as much as 70% of all maintenance activity? A) Preventive maintenance B) Corrective maintenance C) Adaptive maintenance D) Perfective maintenance E) Internal maintenance

Q: 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. E) electronic encyclopedia.

Q: Which of the following are NOT recommended methods for computer training? A) Tutorials B) Resident expert C) External sources D) Interactive training manuals E) Using prior system manuals

Q: Likely topics from which you must determine if training for system users will be useful include: A) customer service basics. B) system marketing. C) use of the system. D) sales. E) conference services.

Q: Most user documentation is now delivered: A) online, in hypertext format. B) through paper manuals. C) by calling technical support numbers. D) through help desks. E) by e-mail.

Q: This type of user documentation allows users to test for proper system installation and then signify their acceptance of the new system and its documentation with their signatures. A) Acceptance sign-off B) User contract C) Request for Proposal (RFP) D) System verification E) Statement of Work

Q: 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 E) Programmer's guide

Q: 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 E) Programmer's guide

Q: Which of the following consists of 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 E) Programmer's guide

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

Q: 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. E) application documentation.

Q: All of the following are types of user documentation EXCEPT: A) release description. B) reference guide. C) acceptance sign-off. D) entity-relationship diagrams. E) user's guide.

Q: Which of the following is a type of system documentation? A) Data-flow diagrams B) Quick reference guide C) Release description D) System administrator's guide E) Acceptance sign-off

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

Q: 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. E) rotation installation.

Q: Which of the following determines how the system performs on the range of possible environments in which it may be used? A) Performance testing B) Recovery testing C) Stress testing D) Range testing E) Security testing

Q: 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. E) system alteration.

Q: Tests performed during alpha testing that are designed to try to break the system are: A) stress tests. B) performance tests. C) recovery tests. D) security tests. E) stub tests.

Q: 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. E) live testing.

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

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

Q: The most complete acceptance testing will include: A) alpha testing, beta testing, and a walkthrough. B) beta testing, stub testing, and unit testing. C) desk checking, a system audit, and integration testing. D) a system audit, system testing, and integration testing. E) alpha testing, beta testing, and a system audit.

Q: 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) test a completed information system using simulated data. E) test a completed information system using real data.

Q: 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. E) component-level testing.

Q: 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. E) a project walkthrough.

Q: 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. E) stub testing.

Q: 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. E) a walkthrough.

Q: 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. E) stub testing.

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

Q: 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. E) integration testing.

Q: Which of the following is the responsibility of testing managers? A) Developing marketing plans B) Integrating data and metadata C) Establishing testing standards D) Ensuring that trainees don't pass E) Requiring online testing

Q: An overall test plan is developed during: A) systems implementation. B) systems analysis. C) logical design. D) physical design. E) systems planning and selection.

Q: Activities occurring within maintenance include: A) transforming changes into requests. B) obtaining maintenance requests. C) determining a steering committee. D) marketing changes. E) adding data definition language to database.

Q: This plan lays out a strategy for moving from the old system to the new. A) Systems service request B) Installation plan C) Training plan D) Testing plan E) Conversion guide

Q: Training on the use of the system begins during the early stages of: A) the systems analysis phase. B) logical design. C) implementation. D) the systems planning and selection phase. E) physical design.

Q: 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. E) electronic performance support system.

Q: The deliverables from the coding, testing, and installation processes include: 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 database prototype. E) the creation of an analysis plan.

Q: The process whereby the physical design specifications created by the design team are turned into working computer code by the programming team is referred to as: A) coding. B) testing. C) implementation. D) code conversion. E) production.

Q: Reverse engineering and reengineering tools are primarily used to maintain older systems that have incomplete documentation or that were developed prior to automated tools.

Q: A primary objective of using automated tools for systems development and maintenance is to change radically how code and documentation are modified and updated.

Q: Baseline routines are guidelines that list the instructions to construct an executable system from the baseline source code.

Q: Build routines are software modules that have been tested, documented, and approved to be included in the most recently created version of a system.

Q: Managing maintenance requests is a maintenance activity.

Q: The mean time between failures is a measurement of error occurrences that can be tracked over time to indicate the quality of a system.

Q: The number of customers for a given system influences most of the costs associated with maintaining a system.

Q: Preventive maintenance requires the least maintenance effort.

Q: The extent to which a system is used and the user's satisfaction with the system are the two most common and trusted ways to determine if an implementation has been a success.

Q: Post-project reviews are part of the system design phase.

Q: A helpdesk is a single point of contact for all user problems and inquiries about a particular system.

Q: Many organizations are deploying Web-based push systems to provide a way to track support requests.

Q: An electronic performance support system is a component of a software package with training and education information embedded.

Q: All user training must be done as a formal course.

Q: Training and support are not critical for the success of an information system.

Q: User documentation is now most often delivered in hypertext format.

Q: The purpose of a reference guide is to provide information on how users can use computer systems to perform specific tasks.

Q: A release description is an example of user documentation.

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

Q: Today's environment makes it possible to maintain and update external documentation as long as desired.

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

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

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

Q: A risk associated with the parallel installation approach is that there may be a delay until benefits result.

Q: 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.

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

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

Q: A risk associated with the direct installation approach is that not all aspects of the new system can be compared to the old system.

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

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

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