Marketing Chapter 9 key terms

Card Set Information

Marketing Chapter 9 key terms
2013-11-19 22:33:42
MIS Exam2

Marketing chapter 9 key terms (Valacich)
Show Answers:

  1. Adaptive maintenance
    Making changes to an information system to make its functionality meet changing business needs or to migrate it to a different operating environment.
  2. Alpha testing
    Testing performed by the development organization to assess whether the entire system meets the design requirements of the users.
  3. Beta testing
    Testing performed by actual system users with actual data in their work environment.
  4. Break-even analysis
    A type of cost-benefit analysis to identify at what point (if ever) tangible benefits equal tangible costs.
  5. Change request management
    A formal process that unsures that any proposed system changes are documented, reviewed for potential risks, appropriately authorized, prioritized, and carefully managed.
  6. Click-wrap license
    A type of software license primarily used for downloaded software that requires computer users to accept the license terms by clicking a button before installing the software.
  7. Corrective maintenance
    Making changes to an information system to repair flaws in its design, coding, or implementation.
  8. Cost-benefit analysis
    Techniques that contrast the total expected tangible costs versus the tangible benefits for an investment.
  9. Data flows
    Data moving through an organization or within an information system.
  10. Developmental testing
    Testing performed by programmers to ensure that each module of a new program is error free.
  11. Discount rate
    The rate of return used by an organization to compute the present value of future cash flows.
  12. Embedded system
    A microprocessor-based system designed to perform only a specific, predefined task (such as a digital video recorder [tivo] or a network router.
  13. Enterprise license
    A type of software license that is usually negotiated and covers all users within an organization. Also known as a "volume license"
  14. External acquisition
    The process of purchasing an existing information system from an external organization or vendor.
  15. Human-computer interface (HCI)
    The point of contact between an information system and its users.
  16. Information systems planning
    A formal process for identifying and assessing all possible information systems development projects of an organization.
  17. Intangible benefit
    A benefit using a particular system or technology that is difficult to quantify
  18. Intangible cost
    A cost of using a particular system or technology that is difficult to quantify
  19. Joint application design (JAD)
    A special type of a group meeting in which all (or most( users meet with a systems analyst to jointly define and agree on system requirements or designs.
  20. Making the business case
    The process of identifying, quantifying, and presenting the value provided by an information system.
  21. Net-present-value analysis
    A type of cost-benefit analysis of the cash flow streams associated with an investment.
  22. Non-recurring cost
    A one-time cost that is not expected to continue after a system is implemented.
  23. Open source software
    Software for which the source code is freely available for use and/or modification.
  24. Patch management system
    An online system that utilizes Web services to automatically check for software updates, downloading and installing these "patches" as they are made available.
  25. Perfective Maintenance
    Making enhancements to improve processing performance, to improve interface usability, or to add desired but not necessarily required system features.
  26. Preventive maintenance
    Making changes to a system to reduce the chance of future system failure.
  27. Processing logic
    The steps by which data is transformed or moved, as well as a description of the events that trigger these steps.
  28. Productivity paradox
    The observation that productivity increases at a rate that is lower than expected when new technologies are introduced.
  29. Project manager
    The person most responsible for ensuring that a project is a success.
  30. Prototyping
    An iterative systems development process in which requirements are converted into a working system that is continually revised through close work between analysts and users.
  31. proxy variable
    At alternative measurement of outcomes; used when it is difficult to determine and measure direct effects.
  32. Pseudocode
    A way to express processing logic independent of the actual programming language being used.
  33. Recurring cost
    An ongoing cost that occurs throughout the life cycle of system development, implementation, and maintenance.
  34. Request for proposal (RFP)
    A communication tool indicating buyer requirement for a given system and requesting information or soliciting bids from potential vendor.
  35. Requirements collection
    The process of gathering and organizing information from user, managers, customers, business processes, and documents to understand how a proposed information system should function.
  36. Shrink-wrap license
    A type of software licence that is used primarily for consumer products; the contract is activated when the shrink wrap on the packaging has been removed.
  37. Software asset management (SAM)
    A set of activities performed to better manage an organization's software infrastructure by helping to: consolidate and standardize software titles, decide when to retire unused software, or decide when to upgrade or replace software.
  38. System conversion
    The process of decommissioning the currently system and installing a new system into the organization.
  39. System effectiveness
    The extent to which a system enables people and/or the firm to accomplish goals or tasks well.
  40. System effectiveness
    The extent to which a system enables people and/or the firm to accomplish goals or tasks well.
  41. Systems analysis
    The second phase of the systems development life cycle in which the current ways of doing business are studied and alternative replacement systems are proposed.
  42. Systems analysis and design
    The process of designing, building, and maintaining information systems.
  43. Systems analyst
    The primary person responsible for performing systems analysis and design activities.
  44. Systems benchmarking
    A standardized set of performance test designed to facilitate comparison between systems.
  45. Systems design
    The third phase of the systems development life cycle in which details of the chosen approach are developed.
  46. Systems development life cycle (SDLC)
    A model describing the life of an information system from conception to retirement.
  47. Systems implementation
    The fourth phase of the systems development life cycle in which the information system is programmed, tested, installed, and supported.
  48. Systems maintenance
    The process of systematically repairing and/or improving an information system.
  49. Systems planning and selection
    The first phase of the systems development life cycle in which potential projects are identified, selected, and planned.
  50. Tangible benefit
    A benefit of using a particular system or technology that is quantifiable.
  51. Tangible cost
    A cost of using a particular system of technology that is quantifiable.
  52. Total cost of ownership (TCO)
    The cost of owning and operating a system, including the total cost of acquisition, as well as all costs associated with its ongoing use and maintenance.
  53. Weighted multicriteria analysis
    A method for deciding among different information systems investments or alternative designs for a given system in which requirements and constraints are weighted on the basis of their importance.