Term
|
Definition
| The major outcome and deliverable from the project initiation and planning phase. It contains an estimate of the project’s scope, benefits, costs, risks, and resource requirements. (p. 99) |
|
|
Term
|
Definition
| A type of cost-benefit analysis to identify at what point (if ever) benefits equal costs. (p.107) |
|
|
Term
|
Definition
| A written report that outlines the justification for an information system. The report highlights economic benefits and costs and the technical and organizational feasibility of the proposed system. (p.99) |
|
|
Term
|
Definition
| A process of identifying the financial benefits and costs associated with a development project. (p.102) |
|
|
Term
|
Definition
| A strategy in systems analysis and design in which the project is reviewed after each phase, and continuation of the project is rejustified in each of these reviews. (p. 98) |
|
|
Term
|
Definition
| A benefit derived from the creation of an information system that cannot be easily measured in dollars or with certainty. (p.103) |
|
|
Term
|
Definition
| A cost associated with an information system that cannot be easily measured in terms of dollars or with certainty. (p.103) |
|
|
Term
| Legal and Contractual Feasibility |
|
Definition
| The process of assessing potential legal and contractual ramifications due to the construction of a system. (p.108) |
|
|
Term
|
Definition
| A cost associated with project start-up and development, or system start-up. (p.103) |
|
|
Term
|
Definition
| The process of assessing the degree to which a proposed system solves business problems or takes advantage of business opportunities. (p.108) |
|
|
Term
|
Definition
| The process of evaluating how key stakeholders within the organization view the proposed system. (p.109) |
|
|
Term
|
Definition
| A document prepared for the customer that describes what the project will deliver and outlines generally at a high level all work required to complete the project. (p.111) |
|
|
Term
|
Definition
| A cost resulting from the ongoing evolution and use of a system. (p.104) |
|
|
Term
|
Definition
| The process of assessing the degree to which the potential time frame and completion dates for all major activities within a project meet organizational deadlines and constraints for affecting change. (p.108) |
|
|
Term
|
Definition
| A benefit derived from the creation of an information system that can be measured in dollars and with certainty. (p.102) |
|
|
Term
|
Definition
| A cost associated with an information system that can be easily measured in dollars and with certainty. (p.103) |
|
|
Term
|
Definition
| The process of assessing the development organization’s ability to construct a proposed system. (p.108) |
|
|
Term
|
Definition
| A peer group review of any product created during the systems development process; also called a structured walkthrough. (p.115) |
|
|
Term
| Business Process Reengineering (BRP) |
|
Definition
| The search for, and implementation of, radical change in business processes to achieve breakthrough improvements in products and services. (p.153) |
|
|
Term
|
Definition
| Questions in interviews and on questionnaires that ask those responding to choose from among a set of specified responses. (p.141) |
|
|
Term
|
Definition
| Technologies that enable the breaking of long- held business rules that inhibit organizations from making radical business changes. (p.154) |
|
|
Term
|
Definition
| Questions in interviews and on questionnaires that have no pre-specified answers. (p.140) |
|
|
Term
|
Definition
| That part of a decision table that lists the actions that result for a given set of conditions. (p.186) |
|
|
Term
|
Definition
| The conservation of inputs and outputs to a data-flow diagram process when that process is decomposed to a lower level. (p.178) |
|
|
Term
|
Definition
| That part of a decision table that lists the conditions relevant to the decision. (p. 186) |
|
|
Term
|
Definition
| 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. (p. 172) |
|
|
Term
|
Definition
| A graphic that illustrates the movement of data between external entities and the processes and data stores within a system. (p. 168) |
|
|
Term
|
Definition
| Data at rest, which may take the form of many different physical representations. (p. 170) |
|
|
Term
|
Definition
| A matrix representation of the logic of a decision, which specifies the possible conditions for the decision and the resulting actions. (p.186) |
|
|
Term
|
Definition
| The extent to which all necessary components of a data- flow diagram have been included and fully described. (p. 180) |
|
|
Term
|
Definition
| The extent to which information contained on one level of a set of nested data-flow diagrams is also included on other levels. (p. 181) |
|
|
Term
|
Definition
| The process of discovering discrepancies between two or more sets of data-flow diagrams or discrepancies within a single DFD. (p. 183) |
|
|
Term
|
Definition
| In a decision table, a condition whose value does not affect which actions are taken for two or more rules. (p. 187) |
|
|
Term
|
Definition
| A data- flow diagram that represents a system’s major processes, data flows, and data stores at a high level of detail. (p. 173) |
|
|
Term
|
Definition
| A DFD that is the result of n nested decompositions of a series of sub processes from a process on a level-0 diagram. (p. 176) |
|
|
Term
|
Definition
| The lowest level of decomposition for a data-flow diagram. (p. 182) |
|
|
Term
|
Definition
| The work or actions performed on data so that they are transformed, stored, or distributed. (p. 170) |
|
|
Term
|
Definition
| Graphically representing the processes that capture, manipulate, store, and distribute data between a system and its environment and among components within a system. (p. 168) |
|
|
Term
|
Definition
| That part of a decision table that specifies which actions are to be followed for a given set of conditions. (p. 186) |
|
|
Term
|
Definition
| The origin and/or destination of data; sometimes referred to as external entities. (p. 170) |
|
|
Term
|
Definition
| The process whereby actual users test a completed information system, the end result of which is the users’ acceptance of it. (p. 347) |
|
|
Term
|
Definition
| User testing of a completed information system using simulated data. (p. 347) |
|
|
Term
|
Definition
| User testing of a completed information system using real data in the real user environment. (p. 347) |
|
|
Term
|
Definition
| Changing over from the old information system to a new one by turning off the old system when the new one is turned on. (p. 348) |
|
|
Term
|
Definition
| The organizational process of changing over from the current information system to a new one. (p. 348) |
|
|
Term
|
Definition
| The process of bringing together all of the modules that a program comprises for testing purposes. Modules are typically integrated in a top-down, incremental fashion. (p. 344) |
|
|
Term
|
Definition
| Changes made to a system to fix or enhance its functionality. (p. 361) |
|
|
Term
|
Definition
| Running the old information system and the new one at the same time until management decides the old system can be turned off. (p. 348) |
|
|
Term
|
Definition
| 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. (p. 348) |
|
|
Term
| Single Location Installation |
|
Definition
| 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. (p. 348) |
|
|
Term
|
Definition
| 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. (p. 345) |
|
|
Term
|
Definition
| The bringing together of all the programs that a system comprises for testing purposes. Programs are typically integrated in a top-down, incremental fashion. (p. 345) |
|
|
Term
|
Definition
| Each module is tested alone in an attempt to discover any errors in its code. (p. 344) |
|
|
Term
|
Definition
| Written, or other visual information, about how an application system works, and how to use it. (p. 351) |
|
|
