Chapter 2.txt

  1. Application service provider (ASP)
    • Organizations that host and run computer
    • applications for other companies, typically
    • on a per-use or license basis.
  2. Enterprise resource planning (ERP) system
    • A system that integrates individual
    • traditional business functions into a series of
    • modules so that a single transaction occurs
    • seamlessly within a single information system
    • rather than in several separate systems.
  3. Managed service provider (MSP)
    • An organization that remotely provides
    • customized computer applications and
    • network-based services for other
    • companies for a monthly or per-use fee.
  4. Outsourcing
    • The practice of turning
    • over responsibility of some or all of an
    • organization�s information systems
    • applications and operations
  5. Request for proposal (RFP)
    • A document
    • provided to vendors to ask them to propose
    • hardware and system software that will meet
    • the requirements of a new system.
  6. Reuse
    • The use of previously written
    • software resources, especially objects and
    • components, in new applications.
  7. chp5
  8. Business process reengineering (BPR)
    • The search for, and implementation
    • of, radical change in business processes to
    • achieve breakthrough improvements in
    • products and services.
  9. Closed-ended questions
    • Questions in
    • interviews and on questionnaires that ask
    • those responding to choose from among
    • a set of specified responses.
  10. Disruptive technologies
    • Technologies
    • that enable the breaking of long-held
    • business rules that inhibit organizations
    • from making radical business changes.
  11. Formal system
    • The official way a system
    • works as described in organizational
    • documentation.
  12. Informal system
    • The way a system
    • actually works.
  13. JAD session leader
    • The trained
    • individual who plans and leads Joint
    • Application Design sessions.
  14. Key business processes
    • The structured,
    • measured set of activities designed to produce
    • a specific output for a particular
    • customer or market.
  15. Open-ended questions
    • Questions in interviews
    • and on questionnaires that have
    • no prespecified answers.
  16. Scribe
    • The person who makes detailed
    • notes of the happenings at a Joint
    • Application Design session.
  17. Ch6
  18. Action stubs
    • That part of a decision
    • table that lists the actions that result for a
    • given set of conditions.
  19. Balancing
    • The conservation of inputs
    • and outputs to a data-flow diagram process
    • when that process is decomposed
    • to a lower level.
  20. Condition stubs
    • That part of a decision
    • table that lists the conditions relevant to the
    • decision.
  21. Context diagram
    • A data-flow diagram of
    • the scope of an organizational system that
    • shows the system boundaries, external
    • entities that interact with the system, and the
    • major information flows between the entities
    • and the system.
  22. Data-flow diagram (DFD)
    • A graphic
    • that illustrates the movement of data
    • between external entities and the processes
    • and data stores within a system.
  23. Data store
    • Data at rest, which may take
    • the form of many different physical
    • representations.
  24. Decision table
    • A matrix representation
    • of the logic of a decision, which specifies
    • the possible conditions for the decision and
    • the resulting actions.
  25. DFD completeness
    • The extent to which
    • all necessary components of a data-flow
    • diagram have been included and fully
    • described.
  26. DFD consistency
    • The extent to which
    • information contained on one level of a set
    • of nested data-flow diagrams is also
    • included on other levels.
  27. Gap analysis
    • The process of discovering
    • discrepancies between two or more sets of
    • data-flow diagrams or discrepancies within
    • a single DFD.
  28. Indifferent condition
    • In a decision table,
    • a condition whose value does not affect
    • which actions are taken for two or more
    • rules.
  29. Level-0 diagram
    • A data-flow diagram
    • that represents a system�s major processes,
    • data flows, and data stores at a high level of
    • detail.
  30. Level-n diagram
    • A DFD that is the result
    • of n-nested decompositions of a series of
    • subprocesses from a process on a level-0
    • diagram.
  31. Primitive DFD
    • The lowest level of
    • decomposition for a data-flow diagram.
  32. Process
    • The work or actions performed
    • on data so that they are transformed,
    • stored, or distributed.
  33. Process modeling
    • Graphically representing
    • the processes that capture, manipulate,
    • store, and distribute data between a
    • system and its environment and among
    • components within a system.
  34. Source/Sink
    • The origin and/or destination
    • of data; sometimes referred to as
    • external entities.
Card Set
Chapter 2.txt
Glossary 2,5,6 MIS system analysis and design