MIS Chapter 12 Making the Business Case for Information Systems and Managing Projects

The prototyping process

1. Identify basic requirements 2. Develop a working prototype 3. Use the prototype 4. User review- are they satisfied? 5. Yes - Operational prototype. No - Revise and enhance the prototype

7 major factors to consider when making the business case for a new info system

1. New products and services 2. Strategic (low cost, differentiation, scope, competitors) 3. Survival 4. Financial rationale 5. Customers and suppliers 6. Long-term IT plan 7. Improved decision making

Information requirements

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

Scoring model

A quick method for deciding among alternative systems based on a system of ratings for selected objectives.

Information systems plan

A road map indicating the direction of systems development: the rationale, the current situation, the management strategy, the implementation plan, and the budget. Developed by Chief Information Officer (CIO) and approved by CEO or Board of Directors

pilot study

A strategy to introduce the new system to a limited area of the organization until it is proven to be fully functional; only then can the conversion to the new system across the entire organization take place

Joint Application Design (JAD)

A technique used to accelerate the generation of information requirements and to develop the initial systems design. Brings end users and info systems specialists together in an interactive session to discuss systems design- can speed up design phase and involve users at an intense level

Systems Development Life Cycle (SDLC)

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. The oldest method for building info systems. Time consuming and expensive to use

implementation

All the organizational activities surrounding the adoption, management, and routinization of an innovation, such as a new information system.

Customization

Allows prewritten software to be modified to meet an organization's unique requirements without destroying the integrity of the software

Portfolio analysis

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. Portfolio analysis inventories all of the firm's information systems projects and assets, including infrastructure, outsourcing contracts, and licenses.

PERT chart

(Program Evaluation and Review Technique) A chart that graphically depicts project tasks and their interrelationships, showing the specific activities that must be completed before others can start.

organizational impact analysis

Study of the way a proposed system will affect organizational structure, attitudes, decision making, and operations.

Request for proposal (RFP)

Used to help select software or software service. 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.

project

a planned series of related activities for achieving a specific business objective

native app

a stand-alone application designed to run on a specific platform and device- mobile platform. Can operate when not connected to the internet. Ex: e-book reading app like Kindle

mobile web app

an Internet-enabled app with specific functionality for mobile devices

parallel strategy

both the old system and its potential replacement are run together for a time until everyone is assured that the new one functions correctly

component-based development

building large software systems by combining pre-existing software components. expedites software creation further

maintenance

changes in hardware, software, documentation, or procedures to a production system to correct errors, meet new requirements, or improve processing efficiency

Prototyping

consists of building an experimental system rapidly and inexpensively for end users to evaluate. Intended as only a preliminary model

documentation

descriptions of how an information system works from either a technical or end-user standpoint

Feasibility study

determines whether each proposed solution is feasible, or achievable, from financial, technical, and organizational standpoints.

acceptance testing

provides the final certification that the system is ready to be used in a production setting

direct cutover strategy

replaces the old system entirely with the new system on an appointed day, carrying the risk that there is no system to fall back on if problems arise

SDLC stages

systems analysis, system design, programming, testing, conversion, production and maintenance

system testing

tests the performance of the info system as a whole in order to determine if discrete modules will function together as planned.

Ergonomics

the interaction of people and machines in the work environment

conversion

the process of changing from the old to the new system. There are four main conversion strategies: the parallel strategy, the direct cutover strategy, the pilot study strategy, and the phased approach strategy.

formal planning and control tools

tools to improve project management by listing the specific activities that make up a project, their duration, and the sequence and timing of tasks. 2 most commonly used methods for documenting project plans - Gantt charts and PERT charts

production

users and technical specialists review the solution to determine how well it has met its original objectives and to decide whether any revisions or modifications are in order

mobile website

version of a regular website that is scaled down in content and navigation for easy access and search on a small mobile screen

Agile development

Focuses on rapid development and delivery of working software with continual user involvement by breaking large project into several small subprojects

Rapid Application Development (RAD)

Process for developing systems in a very short time period by using prototyping, fourth-generation tools, and close teamwork among users and systems specialists

business case

Proposal to management seeking approval for an investment by describing its costs, benefits, and business value.

Intangible benefits

Benefits that are not easily quantified; they include more efficient customer service or enhanced decision making.

Tangible benefits

Benefits that can be quantified and assigned a monetary value; they include lower operational costs and increased cash flows

Scope

Defines what work is or is not included in the project

Systems design

Details how a system will meet the information requirements as determined by the systems analysis. The system design is the blueprint for an information system solution and consists of all the specifications (technical, organizational, & people components) that will deliver the functions identified during systems analysis.

phased approach

Introduces the new system in stages either by functions or by organizational units.

Gantt Chart

Lists project activities and their corresponding start and completion dates. Visually represents the timing and duration of different tasks in a development project and their human resource requirements

test plan

Plan prepared by the development team in conjunction with the users; it includes all the preparations for the series of tests to be performed on the system

project management

The application of knowledge, skills, tools, and techniques to project activities to meet project requirements within specified budgets and time constraints

End-user development

The development of information systems by end users with little or no formal assistance from technical specialists. This reduces the time and steps required to produce a finished application

user-designer communications gap

The difference in backgrounds, interests, and priorities that impede communication and problem solving among end users and information systems specialists.

Testing

The exhaustive and thorough process that determines whether the system produces the desired results under known conditions. Requires detailed testing of individual computer programs, called unit testing as well as system testing, which tests the performance of the information system as a whole. acceptance testing provides the final certification that the system is ready to be used in a production setting. Information systems tests are evaluated by users and reviewed by management.

end-user interface

The part of an information system through which the end-user interacts with the system, such as on-line screens and commands

Capital budgeting

The process of analyzing and selecting various proposals for capital expenditures. One of several techniques used to measure the value of investing in long-term capital investment projects.

unit testing

The process of testing each program separately in the system. Sometimes called program testing