Term
| Systems Development Life Cycle (SDLC) |
|
Definition
| Five procedures and steps that a company goes through when it decides to design and implement a new system. The five steps are systems analysis, conceptual design, physical design, implementation and conversation, and operation and maintenance. |
|
|
Term
|
Definition
(1) A rigorous and systematic approach to decision making, characterized by a comprehensive definition of available alternatives and an exhaustive analysis of the merits of each alternative as a basis for choosing the best alternative.
(2) Examination of user information requirements in an organization to establish objectives and specifications for the design of an information system. |
|
|
Term
|
Definition
| The systems development life cycle phase where a general framework is created to implement user requirements and solve problems identified in the analysis phase. |
|
|
Term
|
Definition
| The phase of the systems development life cycle in which the designer specifies the hardware, software, and procedures for delivering the conceptual systems design. |
|
|
Term
| Implementation & Conversion |
|
Definition
| The capstone phase in the systems development life cycle where the elements and activities of the system come together. |
|
|
Term
|
Definition
| The last phase of the system development life cycle where follow-up studies are conducted to detect and correct design deficiencies. Minor modifications will be made as problems arise in the new system. |
|
|
Term
| Information Systems Steering Committee |
|
Definition
| Plans and oversees the information systems function. The committee often consists of high-level management people, such as the controller and systems and user-department management. The steering committee sets policies that govern the AIS and ensures top-management participation, guidance, and control. |
|
|
Term
|
Definition
| The people who help users determine their information needs and then design an information system to meet those needs. |
|
|
Term
|
Definition
| Persons who develop, code, and test computer programs. |
|
|
Term
|
Definition
| A document that shows how a project will be completed, including the modules or tasks to be performed and who will perform them, the dates they should be completed, and project costs. |
|
|
Term
|
Definition
| A long-range planning document that specifies the overall information system plan of an organization. It shows what the system will consist of, how it will be developed, who will develop it, how needed resources will be acquired, and where the AIS is headed. |
|
|
Term
| Program Evaluation and Review Technique (PERT) |
|
Definition
| A commonly used technique for planning, coordinating, controlling, and scheduling complex projects such as systems implementation. |
|
|
Term
|
Definition
| The path requiring the greatest amount of time to complete a project. If any of the activities on the critical path are delayed, the whole project is delayed. If possible, resources are shifted to critical path activities to reduce project completion time. |
|
|
Term
|
Definition
| A bar graph used for project planning and control. Project activities are shown on the left, and units of time are shown across the top. The time period over which each activity is expected to be performed is represented with a horizontal bar on the graph. |
|
|
Term
|
Definition
| An investigation to determine if the development of a new application or system is practical. This is one of the first steps in the systems evaluation and selection process. |
|
|
Term
|
Definition
| The dimension of feasibility concerned with whether the benefits of a proposed system will exceed the costs. |
|
|
Term
|
Definition
| The dimension of feasibility concerned with whether a proposed system can be developed given the available technology. |
|
|
Term
|
Definition
| The dimension of feasibility that determines if there will be any conflicts between the system under consideration and the organization's ability to discharge its legal obligation. |
|
|
Term
|
Definition
| The dimension of feasibility that determines if the system being developed can be implemented in the time allotted. |
|
|
Term
|
Definition
| The dimension of feasibility concerned with whether a proposed system will be used by the people in an organization. It also is concerned with how useful the system will be within the operating environment of the organization. |
|
|
Term
|
Definition
| An estimate of funds to be appropriated for the acquisition of major capital assets and for investment in long-term projects. The estimated benefits are compared with the costs to determine if the system is cost beneficial. |
|
|
Term
|
Definition
| The number of years required of the net savings to equal the initial cost of an investment. |
|
|
Term
|
Definition
| A value determined by discouraging all estimated future cash flows back to the present, using a discount rate that reflects the time value of money to the organization. |
|
|
Term
| Internal Rate of Return (IRR) |
|
Definition
| The effective interest rate that equates the present value of total costs to present value of total savings. |
|
|
Term
| Behavioral Aspects of Change |
|
Definition
| Systems development causes changes in organizations that may result in people changing their behavior. Organizations must be sensitive to and consider the feelings and reactions of persons affected by such changes. |
|
|
Term
|
Definition
| A way of resisting change that is intended to destroy, cripple, or lessen the effectiveness of a system. Aggression may take the form of increase error rates, disruptions, or deliberate sabotage. |
|
|
Term
|
Definition
| A way of resisting change by blaming anything and everything on the new system. the system becomes the scapegoat for all real and imagined problems and errors. |
|
|
Term
|
Definition
| A way of resisting change by not using the new system. |
|
|
Term
| Request for Systems Development |
|
Definition
| A written request for anew or improved system. The request describes the current system's problems, why the change is needed and the proposed system's goals and objectives as well as its anticipated benefits. |
|
|
Term
|
Definition
| Preliminary investigation to determine if a proposed new system is both needed and possible. |
|
|
Term
| Proposal to Conduct Systems Analysis |
|
Definition
| A document calling for the analysis of either an existing or proposed system. This document is prepared by a user or department and requests the information systems function to analyze the feasibility of developing a system to perform a specific function. |
|
|
Term
|
Definition
| The systematic gathering of facts relating to the existing information system. A systems analyst generally carries out this task. |
|
|
Term
|
Definition
| A complete description of all aspects of each systems application, including narrative material, charts, and program listings. |
|
|
Term
|
Definition
| The description of how a system functions by describing the flow of documents, the computer processes performed and the people performing them, the equipment used, and other physical elements of the system. |
|
|
Term
|
Definition
| Descriptions of a system that focus on the essential activities and flow of information in the system irrespective of how the flow is actually accomplished. |
|
|
Term
|
Definition
| The culmination of the systems survey. It contains documentation such as memos, interview and observation notes; questionnaire data; file and record layouts and descriptions; input and output descriptions; and copies of documents, flowcharts; and data flow diagrams. |
|
|
Term
|
Definition
| Way of handling systems change by reorganizing that every system must have an objective, a set of components, and a set of interrelationships among the components. Proceeds step by step, with a through exploration of all implications and alternatives at each step. |
|
|
Term
|
Definition
| Comprehensive report prepared at the end of the systems analysis and design phase that summarizes and documents the findings of analysis activities. |
|
|
