BIS 220, INTRODUCTION TO COMPUTER SYSTEMS AND APPLICATIONS

WORKSHOP IVRaji Gogulapati

July 2014

Workshop III Review

Why Most New Information Systems Fail?

Nature of Software Development

IS/ IT Planning & Justification

IS/ IT System Development Methodologies

IS/ IT Funding & Costs

Summary

Your activities for coming week

TOPICS

Why do Systems Implementations Fail Often?

What can be done?

Systems Failures

Question and

Understand

Systems planning/ selection

System implementation

Support

Systems Failures in Stages

Types of Failure

Types of failure

Disaster or Horror

Big or Small

Forthcoming

Expectations Gap Risk

sInactio

n

Failures

What did we learn so far?

Why many new system implementations fail ?

What can be done ?

IS/ IT • Planning • Justification

IS/ IT system development methodologies and options• Team effort• Several

approaches • Start with

investigation and analysis, design, maintenance and review

Emphasis • How to deliver • Right information

to the right person at the right time!

What is Next ?

Workshop III Review

Why Most New Information Systems Fail?

Nature of Software Development

IS/ IT Planning & Justification

IS/ IT System Development Methodologies

IS/ IT Funding & Costs

Summary

Your activities for coming week

Basic system development framework

IS development – intangible, eventually

visible

Process of design to delivery is repeatable

Software engineering –

shifts from waterfall paradigm

Analogies – limited and not

complete

Iterative, agile development

IS/ IT Strategic Planning

External/ Internal Business

environment

.

External/ Internal IS/

IT environment

.

IS/ IT Mgmt. Policies

Framework for IS/ IT Planning

IS/ IT Mgmt. Policies

IS Strategy

IT Strategy

Future Application Portfolio

Framework for IS/ IT Planning continued

Development of Information Systems, Business Manager’s Point of View

Strategic High Potential

Key Operational Support

Business Development Projects

IT Development Projects

Business Infrastructure Projects IT Infrastructure Projects

IS Planning Process

Align organization’s mission and Business assessment

Arrive at Organization’s strategic plan

Consider current technology architecture

IS strategic plan

New Information Technology architecture

IS Operational Plan

IS development plans

Spending Approaches – History and Current

Justification of Investments

Workshop III Review

Why Most New Information Systems Fail?

Nature of Software Development

IS/ IT Planning & Justification

IS/ IT System Development Methodologies

IS/ IT Funding & Costs

Summary

Your activities for coming week

Topics

Stages of SDLC

Systems investigation

Systems analysis

Systems design

Programming and

testing

Implementation

Operations and maintenance

Supporting Tools of SDLC during various stages

Prototyping

Joint Application Design

Upper case tools

Lower case tools

Examples?

What are the benefits of planning for Information Systems? What obstacles teams might have to overcome to have their plans heard in an organization? Discuss

Problem Recognition and Definition

User mentions a problem

Is it a problem or symptom

Establish the need

Define the problem

Technical feasibility (Proof of

concept)

Economic feasibility (costs

vs Benefits)

Legal Feasibility (laws and

regulations)

Operational feasibility (historical

acceptance of IT systems,

Personnel re-training)

Schedule feasibility

(balancing time and resource)

Feasibility Study

Current System

Analysis

Requirements analysis

Conceptual Design

Alternatives

Systems Analysis

Goals of systems analysis stage

Understand As-Is Determine To-Be

Understand current processes Determine requirements for the system being built

System Development Tools

Iterative Development – Theme

Design

Develop

Test

Joint Application Developme

nt User review

Requirements

System Development Tools

Compress cycles, iterative Development – Theme

Rapid Application

Development

Compress SDLC stage

time

Project management terminology

Team work

Project plan

Elements of project management

Identifying requireme

nts

Organizational integration

Team manageme

nt

Risk and opportunity management

Project control

Visibility, status, corrective action, leadership

Elements of Project management

What

• IS/ IT planning• justification of investments

Did we learn

• System development methodologies

• Options

So far?

• How to deliver the right information to the right person at the right time?

What

is

next?Who funds

IT investments What are the costs involved?

What

is

next?Managing

IT Portfolios Evaluation W

hat

is

next?Monitor,

communicate reduce risks

Workshop III Review

Why Most New Information Systems Fail?

Nature of Software Development

IS/ IT Planning & Justification

IS/ IT System Development Methodologies

IS/ IT Funding & Costs

Summary

Your activities for coming week

Topics

Funding and

Costs

Methods

Cost Evaluatio

n

• Comparison

• Chargeback• Allocation • Corporate

Budget

• ?

IT Portfolio Profile

Informational %Strategic %

Transactional %

Infrastructure %

Perspectives for driving performance

Financial perspecti

ve

Internal Perspective

Customer perspecti

ve

Learning Perspective

Goals Measures

Your activities for coming week

Prepare and submit assignments as per syllabus. Remember to include all references and use proper citations. The final exam is during week four – week five. Follow Materials Link.

Read:

Selected Readings specified in Materials tabRefer to your syllabus for details on activities during the workshop

The chapters recommended from the electronic texts in Materials were used.

Some of the figures used in the slides were taken from the chapters in texts.

Source for slides on Information Architecture and Information Management are from Principles of Information Systems Management by John Ward

Source of slides on Information Systems failures is from Phil Simon’s Why New Systems Fail theory and practice collide.