Chapter 5

Cards (33)

  • Parallel operation cutover
    : Running two systems in parallel essentially doubles resource consumption.
  • Payback method
    : Product life cycles and rapid advances in technology, the effective lives of information systems tend to be short.
  • Phased cutover
    : Operating the new system in modules phasing in the new system in modules reduce the risk of a devastating system failure.
  • Polymorphism
    : Ability of a variable, function or object to take on multiple forms. It allows multiple and different objects to respond to the same message.
  • Procedural language
    : Well-structured steps and procedures within its programming context to compose a program.
  • Project planning
    : Allocation of resources to individual applications within the framework of the strategic plan.
  • Project proposal
    : Document provides management with a basis for deciding whether to proceed with the project.
  • Project schedule
    : Document that formally presents management’s commitment to the project.
  • Quality assurance group
    : Programmers, analysts, users, and internal auditors to simulate the operation of the system to uncover errors, omissions, and ambiguities in the design.
  • Run manual
    : Computer operators use documentation transaction (input) files, master files, and output files used in the system.
  • Schedule feasibility
    : The firm’s ability to implement the project within an acceptable time.
  • Special-purpose system
    : Software vendors create accounting procedures to selected target segments of the economy.
  • Stakeholders
    : Entities either inside or outside an organization that have direct or indirect interest in the
  • Steering committee
    : An organizational committee consisting of senior-level management responsible for systems planning.
  • Strategic systems planning
    : Budgeting resources for other strategic activities of systems resources at the macro level.
  • Structure diagram
    : Design is usually documented by data flow and structure diagrams to depict the top-down decomposition of a hypothetical business process.
  • System survey
    : Determination of what elements, if any, of the current system should be preserved as part of the new system.
  • Systems analysis report
    : Analysis and recommendations for the new system.
  • Systems analysis
    : Two-step process that involves a survey of the current system and then an analysis of the user’s needs.
  • Systems development life cycle
    : Formal process consisting of two major phases: new systems development and maintenance.
  • Systems evaluation and selection
    : An optimization process that seeks to identify the best system.
  • Systems maintenance
    : Modifying the system to produce a new report or changing the length of a data field.
  • Systems planning
    : Linking of individual system projects or applications to the strategic objectives of the firm.
  • Systems professional
    : Systems analysts, systems engineers, database designers, and programmers gather facts about problems with the current system, analyze these facts, and formulate a solution to solve the problems.
  • Systems selection report
    : The deliverable product of the systems selection process.
  • Tangible benefits
    : Organization to reduce inventories and at the same time improve customer service by reducing stock outs.
  • Technical feasibility
    : The physical basis for most of the system’s design features, this aspect bears heavily on the overall feasibility of the competing system.
  • Third-generation languages (3GLs)

    : Program logic is executed by the programmer to specify the precise order in procedural language.
  • Turnkey system
    : Completely finished and tested systems that are ready for implementation.
  • Tutorial
    : Train the novice or the occasional user.
  • User handbook
    Documentation will guide the user interactively in the use of the syste
  • Vendor-supported system
    : Custom systems that organizations purchase from commercial vendors.
  • Walkthrough
    : Analysis of system design to ensure the design is free from conceptual errors that could become programmed into the final system.