|

Change Management:
Managing the process of implementing major changes in information technology, business processes, organizational structures, job assignments, and work relationships so as to reduce the risks and costs of change, and optimize its benefits.
Computer-Aided Systems Engineering (CASE):
Using software packages to accomplish and automate many of the activities of information systems development, including software development or programming.
Conversion Methods:
The process in which the hardware, software, people, and data resources of an old information system must be converted to the requirements of a new information system. This usually involves a (1) parallel, (2) phased, (3) pilot, or (4) 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.
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:
Managers and business specialists can develop their own computer-based business applications.
End User Involvement:
End users are involved in the development of new or improved computer applications without the direct involvement of professional systems analysts.
End User Resistance:
A Anew way of doing things" generates some resistance in the people affected. New systems may result in end user resistance. The key to minimizing end user resistance is to provide proper end user education and training, provide for good communications with IS professionals, and get the end users involved in the systems development and implementation.
Evaluation Factors - Hardware:
Criteria used to evaluate hardware services (Figure 10.25)
Evaluation Factors - IS Services:
Criteria used to evaluate IS services (Figure 10.27)
Evaluation Factors - Software:
Criteria used to evaluate software services (Figure 10.26)
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:
A detailed description of user information needs and the input, processing, output, storage, and control capabilities required to meet those needs.
Implementation Process:
Includes acquisition, testing, training, and conversion to a new system.
Intangible Benefits:
The non-quantifiable benefits of a proposed solution.
Intangible Costs:
The non-quantifiable costs of a proposed solution.
Operational Feasibility:
The willingness and ability of management, employees, customers, and suppliers to operate, use, and support a proposed system.
Organizational Analysis:
Evaluating the organizational and environmental systems and subsystems involved in any situation.
Organizational Feasibility:
How well a proposed information system supports the objectives of an organizations strategic plan for information systems.
Postimplementation Review:
Monitoring and evaluating the results of an implemented solution or system.
Prototype:
A working model. In particular, a working model of an information system, which includes tentative versions of user, input and output, databases and files, control methods, and processing routines.
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 Analysis:
(1) Analyzing in detail the components and requirements of a system, (2) Analyzing in detail the information needs of an organization, the characteristics and components of presently utilized information systems, and the functional requirements of proposed information systems.
Systems Approach:
A systematic process of problem solving based on the scientific method, which defines problems and opportunities in a systems context. Data is gathered describing the problem or opportunity, and alternative solutions are identified and evaluated. Then the best solution is selected and implemented, and its success evaluated.
Systems Design:
Deciding how a proposed information system will meet the information needs of end users. Includes logical and physical design activities, and user interface, data and process design activities, which produce system specifications that satisfy the system requirements developed in the systems analysis stage.
Systems Development Life Cycle:
(1) Conceiving, designing, and implementing a system, (2) Developing information systems by a process of investigation, analysis, design, implementation, and maintenance. Also called information systems development, or application development.
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 Investigation:
The screening, selection, and preliminary study of a proposed information system solution to a business problem.
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.
System Testing:
Checking whether hardware and software work properly.
Systems Thinking:
Trying to recognize systems and the new interrelationships and components of systems in any situation.
Tangible Benefits:
The quantifiable benefits of a proposed solution or system.
Tangible Costs:
The quantifiable costs of a proposed solution or system.
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, Data, and Process Design:
The three major activities or products of systems design.
|