| Conversion | The process in which the hardware, software, people, network, and data resources of an old information system must be converted to the requirements of a new information system. This usually involves a parallel, phased, pilot, or plunge conversion process from the old to the new system.
|
 |
|
|
| Cost/Benefit Analysis | Identifying the advantages or benefits and the disadvantages or costs of a proposed solution.
|
|
|
|
| Data Conversion | Converting data into new data formats required by a new business application and its software and databases. Also includes correcting incorrect data, filtering out unwanted data, and consolidating data into new databases and other data subsets.
|
|
|
|
| Documentation | A collection of documents or information that describes a computer program, information system, or required data processing operations.
|
|
|
|
| Economic Feasibility | Whether expected cost savings, increased revenue, increased profits, and reductions in required investment exceed the costs of developing and operating a proposed system.
|
|
|
|
| End-User Development | The process by which the end user of a software application is also the primary developer of the software.
|
|
|
|
| Feasibility Study | A preliminary study that investigates the information needs of end users and the objectives, constraints, basic resource requirements, cost/benefits, and feasibility of proposed projects.
|
|
|
|
| Functional Requirements | The information system capabilities required to meet the information needs of end users. Also called system requirements.
|
|
|
|
| Implementation Process | The process and activities associated with installing a software application and preparing it for actual use.
|
|
|
|
| Operational Feasibility | The willingness and ability of management, employees, customers, and suppliers to operate, use, and support a proposed system.
|
|
|
|
| Postimplementation Review | Monitoring and evaluating the results of an implemented solution or system.
|
|
|
|
| Project Management | Managing the accomplishment of an information system development project according to a specific project plan, so a project is completed on time, is within its budget, and meets its design objectives.
|
|
|
|
| Prototyping | The rapid development and testing of working models, or prototypes, of new information system applications in an interactive, iterative process involving both systems analysts and end users.
|
|
|
|
| Systems Approach | A systematic process of problem solving that defines problems and opportunities in a systems context. Data are gathered describing the problem or opportunity, and alternative solutions are identified and evaluated. Then the best solution is selected and implemented, and its success is evaluated.
|
|
|
|
| Systems Implementation | The stage of systems development in which hardware and software are acquired, developed, and installed; the system is tested and documented; people are trained to operate and use the system; and an organization converts to the use of a newly developed system.
|
|
|
|
| Systems Maintenance | The monitoring, evaluating, and modifying of a system to make desirable or necessary improvements.
|
|
|
|
| System Specifications | The product of the systems design stage. It consists of specifications for the hardware, software, facilities, personnel, databases, and the user interface of a proposed information system.
|
|
|
|
| Systems Thinking | Recognizing systems, subsystems, components of systems, and system interrelationships in a situation. Also known as a systems context or a systemic view of a situation.
|
|
|
|
| Technical Feasibility | Whether reliable hardware and software capable of meeting the needs of a proposed system can be acquired or developed by an organization in the required time.
|
|
|
|
| User Interface Design | Designing the interactions between end users and computer systems, including input/ output methods and the conversion of data between human-readable and machine-readable forms.
|