Term
|
Definition
| Provides the final certification that the system is ready to be used in a production setting |
|
|
Term
| Component-based development |
|
Definition
| Building large software systems by combining pre-existing software components. |
|
|
Term
| Computer-aided software (CASE) Engineering |
|
Definition
| provides software tools to automate the methodologies described to reduce the amount of repetitive work in systems development. |
|
|
Term
|
Definition
| the process of changing from the old system to the new system |
|
|
Term
|
Definition
| the modification of a software package to meet an organizations unique requirements without destroying the package software's integrity. |
|
|
Term
|
Definition
| primary tool for structured analysis that graphically illustrates a system's component process and the flow of data between them. |
|
|
Term
|
Definition
| A risky conversion approach where the new system completely replaces the old one on an appointed day. |
|
|
Term
|
Definition
| descriptions of how an information system works from either a technical or end-user standpoint. |
|
|
Term
|
Definition
| the development of information systems by end users with little or no formal assistance from technical specialists |
|
|
Term
|
Definition
| the interaction of people and machines in the work environment, including the design of jobs, health issues, and the end-user interface of information systems. |
|
|
Term
|
Definition
| As part of the systems analysis process, he way to determine whether the solution is achievable, given the organization's resources and constraints. |
|
|
Term
| Formal planning and tools |
|
Definition
| improve project management by listing the specific activities that make up a project, their duration, and the sequence and timing of tasks. |
|
|
Term
|
Definition
| visually represents the timing, duration, and human resource requirements of project tasks, with each task represented as a horizontal bar whose length is proportional to the time required to complete it. |
|
|
Term
|
Definition
| Simon's final stage of decision-making, when the individual puts the decision into effect and reports on the progress of the solution. |
|
|
Term
|
Definition
| A detailed statement of the information needs that a new system must satisfy; identifies who needs what information, and when, where, and how the information is needed |
|
|
Term
|
Definition
| a road map indicating the direction of systems development the rationale, the current situation, the management strategy, the implementation plan and the budget. |
|
|
Term
|
Definition
| benefits that are not easily quantified; they include more efficient customer service or enhanced decision making |
|
|
Term
| Joint application design (JAD) |
|
Definition
| process to accelerate the generation of information requirements by having end users and information systems specialists work together in intensive interactive design sessions. |
|
|
Term
|
Definition
| changes in hardware, software, documentation, or procedures to a productions system to correct errors, meet new requirements,or improve processing efficiency. |
|
|
Term
| Object-oriented development |
|
Definition
| approach to systems development that uses the object as the basic unit of systems analysis and design. The system is modeled as a collection of objects and the relationship between them. |
|
|
Term
| Organizational impact analysis |
|
Definition
| study of the way a proposed system will affect organizational structure, attitudes, decision making, and operations. |
|
|
Term
|
Definition
| a safe and conservative conversion approach where both the old system and its potential replacement are run together for a time until everyone is assured that the new one functions correctly. |
|
|
Term
|
Definition
| graphically depicts project tasks and their interrelationships, showing the specific activities that must be completed before others can start. |
|
|
Term
|
Definition
| introduces the new system in stages either by functions or by organizational units. |
|
|
Term
|
Definition
| an analysis of the portfolio of potential applications within a firm to determine the risks and benefits, and to select among alternatives for information systems. |
|
|
Term
|
Definition
| describe the logic of the processes occurring within the lowest levels of a data flow diagram. |
|
|
Term
|
Definition
| the stage after the new system is installed and the conversion is complete; during this time the system is reviewed by users and technical specialists to determine how well it has met its original goals. |
|
|
Term
|
Definition
| a planned series of related activities for achieving a specific business objective. |
|
|
Term
|
Definition
| Application of knowledge, skills, tools and techniques to achieve specific targets within specified budget and time constraints. |
|
|
Term
|
Definition
| the process of building an experimental system quickly and inexpensively for demonstration and evaluation so that users can better determine information requirements. |
|
|
Term
| Rapid application development (RAD) |
|
Definition
| process for developing systems in a very short time period by using prototyping, fourth generation tools, and close teamwork among users and systems specialists. |
|
|
Term
| Request for proposal (RFP) |
|
Definition
| a detailed list of questions submitted to vendors of software or other services to determine how well the vendor's product can meet the organization's specific requirements. |
|
|
Term
|
Definition
| defines what work is or is not included in a project |
|
|
Term
|
Definition
| a quick method fro deciding among alternative systems based on a system of ratings for selected objectives. |
|
|
Term
|
Definition
| system documentation showing each level of design, the relationship among the levels, and the overall place in the design structure; can document one program, one system or part of one program. |
|
|
Term
|
Definition
| refers to the fact that techniques are carefully drawn up, step by step, withe each step building on a previous one. |
|
|
Term
|
Definition
| tests the functioning of the information system as a whole in order to determine if discrete modules will function together as planned. |
|
|
Term
|
Definition
| the analysis of a problem that the organization will try to solve with an information system. |
|
|
Term
|
Definition
| details how a system will meet the information requirements as determined by the systems analysis. |
|
|
Term
| Systems development lifecycle (SDLC) |
|
Definition
| a traditional methodology for developing an information system that partitions the systems development process into formal stages that must be completed sequentially with a very formal division of labor between end users and information systems specialists. |
|
|
Term
|
Definition
| benefits that can be quantified and assigned a monetary value; they include lower operational costs and increased cash flows. |
|
|
Term
|
Definition
| prepared by the development team in conjunction with the users it includes all of the preparation for the series of tests to e performed on the system. |
|
|
Term
|
Definition
| the exhaustive and thorough process that determines whether the system produces the desired results under known conditions. |
|
|
Term
|
Definition
| the process of testing each program separately in the system. Sometimes called program testing. |
|
|
Term
| User-designer communications gap |
|
Definition
| the differences in backgrounds, interests, and priorities that impede communication and problem solving among end users and information systems specialists. |
|
|
