Chapter 1-Information Systems

7/27/2019 Chapter 1-Information Systems

1/31

INFORMATION

SYSTEMS WITHINORGANISATIONSSuraj Juddoo

[email protected]


2/31

What well cover today:

1. Ourselvesvery important

2. Nitty gritty details of the module

3. First topic:

1. intro to information systems

2. Systems theory


3/31

Ourselves

Academic/consultant

Specialist in Business information

Systems..attracted to the world of robotics

As you are IT based students, why do you

think this module could be of interest, both

professionally or personally??


4/31

Details of modules

3 hours contact/weeklecture and

seminar(activities + discussions)

Assessment: 30% coursework+70% written

unseen exam

Reading lists: as per module handbook

I expect you to read and learn upon topics

discussed. Failure of which increases yourpotential for failure.

Any queries?


5/31

Introduction

Additional reference:

Rethinking Information Systems in Organisations,

Jean Paul Kowalek

Business Information Management, Dava Chaffyand Steve Wood


6/31

Information Systems as a

discipline

The main aims of todays session:

Set the context(always debatable) of Information

Systems

Understand the principal vectors which led toemergence of IS

Understand some of the failures of IS, and their

impact


7/31

Basic definitions

What is information? How is it different from

data?

Data is commonly believed to be a simple record

of events, activities and observations Information is purposely constructed via human

interpretation of the data


8/31

History

Industrial revolution sharpened differencebetween those engaged in data processingactivities and those engaged in execution of

tasks, based on information(Braverman,1974)Arrival of computer marked the automation of

data processing activities, related mostly withaccounting activities then gradually expanding

to other business functionsApplication of technology in

organisations!!thus, interdisciplinary in nature


9/31

History

Borrowed some ideas from systems theory of

management

Systems theory: thinking of organisations and

their underpinning activities as whole, and not inisolation

Assumption of IS as computer based!!

OBrien(1999):IS is an organised combinationof people,hardware, software,communication

networks and data resources that collects,

transforms and disseminated information in an

organisation.


10/31

10

Input of

data

resources

Processing

data into

information

Output of

information

products

Storage of data

resources

Control of system

performance

Network Resources

Communications media and Networksupport

(OBrien, 2004, page 11)The Components of an IS


11/31

Current situation

Major advances in terms of

technology(processing power, storage

capacity, software complexity). Could be

disruptive or adaptative New applications/concepts(cloud

computing,Big Data,BYOD) which need to be

put into the context of organisational problem

solving

Important organisational change driver!!

Business Process Re-engineering often

improperly used


12/31

Competitive advantage and IS

CA made popular by Michael Porters 5 forcesmodel

With globalisation, the onus to become

competitive is becoming stronger Need for alignment between business strategy

and IT strategy

IT/IS decision makers are now often part of top

management Examples of IT/IS helping CA: SABRE, Dell,

Amazon)


13/31

Failures

Project Management issues(budget and

schedule overrun, lack of personnel)

Inadequacy of IT solution for users

IT solution not showing any clear proof of

benefits greater than costs

IT solution not moving higher than the

operational support according to Mc Farland;thus representing cost centres.


14/31

Failures

OASIG report(1995)

Covered 14000 organisations in UK

20-30% success rates for IT projects

CHAOS report(1995): 31% IT projects cancelled

52.7% cost 189% that expected

Robbins-Gioia LLC(2001):

51% viewed ERP as unsuccessful

46% felt their organisations didnt know how tomaster ERP


15/31

Reasons for failures

Loose statements such as:

Commitment of senior management

Improper end users involvement

Wrong project management

Not properly conceived risk management

Inadequate training of end users

Improper contingency planning There is a current lack of in-depth precise

explanations why all of the above do occur!


16/31

Systems theory(1)

System :- different components working in

synergy towards common goal

State 3 examples of systems??

Systems theory:-

Modular approach

Holistic view

Environments effects


17/31

Systems theory(2)

Inputs:- raw materials of system

Process:- transformation/activity

Outputs:- end product/output/result

Think about those 3 components in systems

you thought of before??


18/31

Systems theory(3)

Boundary:-specifies limit/range/scope of

system

Open systems:-interacts with environment

Closed systems:-no interaction

Feedback: result being used to affect next

input for better system control

Filtering: removing information to order to beconcise


19/31

Types of information

Types of Information:

Strategic

Tactical

Operational

Characteristics: Accurate, complete, Cost

benefit, user centred, relevant, authoritative,

timely, easy to use


20/31

Types of IS

4 levels: Strategic, management, knowledge,

Operational

ESS: target strategic; concise; both internal

and external inputs

DSS: target management; more detailed;

analyse large volumes of data

KWS : systems for specialized services OAS : for office use

TPS : routine tasks


21/31

Information Sources(1)

Internal information:

Collecting data

Communication

manage information effectively

Sources: document study, company literature,

etc.

Give 1 example of some internal data sourcewithin your organisation?


22/31

Information Sources(2)

External information:- may be informal;

involves analysis & survey of environment

Data sources : environment


23/31

SDLC

systematic approach to building software toensure better probability of success

Predictive or adaptative approaches

consists of several phases,whose nature are as

follows:


24/31

Systems analysis

Investigation of system

Extensive involvement of users

Inputs, processes and outputs need to be

determined

Problems, improvements to be elicited

Requirements specifications produced

Generate and evaluate alternatives


25/31

System Design

Come up with a solution based on analysis

stage

Technical specifications of input,outputs,

storage and processes Logical design is the business intelligence,thus

independent of technology

Physical design refers to the technology toimplement the new system : Database, UI,

system interfaces


26/31

System construction

Known as software development phase

System is built, tested and documented

Extensive user involvement


27/31

System implementation

Go live

Train users, transfer old data and changeover

method

Final evaluation


28/31

Maintenance and Review

Must make system running

Perfective, adaptative and corrective

System becomes outdated and cycle restarts


29/31

Waterfall model

SDLC is linear, waterfall model is iterative

Can go back and make changes to precedent

stages

Other models : Object Oriented approach,extreme programming, Scrum


30/31

SDLC ADVANTAGES

Project management by break down of tasks

Good documentation

Used tried and tested(sure) techniques


31/31

SDLC problems

inflexible,: could not adapt to time constraints

Narrow focus: not suitable for more business

intelligent solutions

Old fashioned: much meetings and paperwork

Time and cost overruns : mostly due to poor

management

Chapter 1-Information Systems

Documents