44221: Information Systems
Lecture 2 (Week 3)
Information Systems Concepts
By Ian Perry
http://itsy.co.uk/ac/0506/Sem1/44221_IS/
The Structure of Organisations

Can ‘view’ an Organisation in many ways, but some
of the most common (i.e. those that you will see in
many books) are:




Levels of Management
Business Functions
Matrix (i.e. Functions & Levels)
No one of these gives a ‘perfect’ view for all
organisations, it depends upon:



Ian Perry
Why you are attempting to analyse the organisation.
The style/type/size/complexity of organisation you are
attempting to analyse.
The amount of detail your analysis requires.
44221: Information Systems: Information Systems Concepts
Slide 2
Levels of Management
Strategic
Long-Term
Tactical
Short-Term
Operational
Day-to-Day
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 3
Business Functions
Organisation
Production
Director
Etc.
Ian Perry
Etc.
Etc.
Marketing
Director
Etc.
Personnel
Etc.
Etc.
Etc.
Director
Etc.
Etc.
Etc.
Finance
Director
Etc.
44221: Information Systems: Information Systems Concepts
Etc.
Etc.
Etc.
Slide 4
Matrix (i.e. Functions & Levels)
FUNCTION
LEVEL
Marketing
Production
Finance
Personnel
Strategic
Tactical
Operational
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 5
System

A set of interrelated components which act
together in an organised way in order to achieve
an objective.


As with data/information/knowledge, each
System may be:


A System should have a known/defined/agreed
purpose.
defined/viewed/interpreted in different ways by
different people.
Systems Concepts provide a common language
with which to describe Systems of all types.

Ian Perry
diagrams are VERY IMPORTANT.
44221: Information Systems: Information Systems Concepts
Slide 6
System, Sub-system, Element
System
Sub-system
Element
Ian Perry
Element
Element
This, however, is NOT
a very ‘good’ systems
diagram.
44221: Information Systems: Information Systems Concepts
Slide 7
A ‘better’ systems diagram?
System
Sub-system
Element
Sub-system
Element
Element
Element
Element
Sub-system
Element
Ian Perry
Element
44221: Information Systems: Information Systems Concepts
Slide 8
Components

Systems are an organised whole, consisting
of a number of component parts, i.e.:


The elements of our previous system, subsystem, elements view.
These Components:

Have a Form, which can be:



Have Attributes, i.e. characteristic properties,
which can be:


Ian Perry
Concrete
Abstract
Hard
Soft
44221: Information Systems: Information Systems Concepts
Slide 9
Concrete v Abstract Form

Concrete components have a physical existence,
and can be detected by at least one of our senses.




Concrete components tend to ‘appear’ the same to
different individuals.
E.g. a Warehouse, a Desk, the Temperature.
Concrete Money = Coins & Notes.
Abstract components have no physical existence,
so you can’t see, touch, hear, or smell them.



Ian Perry
Abstract components may ‘appear’ differently to
different individuals.
E.g. Pretty/Ugly, Information.
Abstract Money = A Bank Statement.
44221: Information Systems: Information Systems Concepts
Slide 10
Hard v Soft Attributes

Hard components, do not depend upon
someone’s personal sense of value.

Easy to define/quantify/measure, e.g.:



The absolute size of a £20 Note.
The number of £1 Coins in my pocket.
Soft components, have no agreed objective
test to prove one person right or wrong.

Hard (impossible?) to define/quantify/measure,
e.g.:


Ian Perry
A lot of money.
Value for money.
44221: Information Systems: Information Systems Concepts
Slide 11
So What?

Beware the Abstract/Soft.

Concrete/Hard Components, are quite easy to
identify, as they:



Abstract/Soft Components, are often very
difficult to identify, as they:


Ian Perry
tend to ‘appear’ the same to different individuals.
are easy to define/quantify/measure.
may ‘appear’ differently to different individuals.
are difficult to define/quantify/measure.
44221: Information Systems: Information Systems Concepts
Slide 12
Components, Holism, Emergent Property
Fuselage
Tail
Wing
Engine
Ian Perry
Aeroplane
Flight
a Hard/Concrete Example
44221: Information Systems: Information Systems Concepts
Slide 13
Components, Holism, Emergent Property
Customer
Requirements
Product
Knowledge
Order
Processing
Customer
Satisfaction
a Soft/Abstract Example
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 14
Boundary & Identity

There must be a way of defining what
components are to be included within the
system under analysis.


And hence what components are to be
excluded.
As such:

All systems must have a boundary;


All systems must have an identity;

Ian Perry
to define which components are a part of this
system.
to distinguish them from other similar systems.
44221: Information Systems: Information Systems Concepts
Slide 15
Boundary & Identity (continued)
System A
System B
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 16
Connection & Interaction

Systems do not exist in isolation:


Connection between systems may be:


they are both ‘connected to’ and ‘interact with’
other systems.
Permanent or Ad-hoc.
Interaction between systems is, in most
cases, considered to be:

Ian Perry
A two-way process.
44221: Information Systems: Information Systems Concepts
Slide 17
Connection & Interaction (continued)
System A
System B
System C
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 18
Process

All systems ‘do something’ (i.e. Process), and
interact with other systems via one or
more:



Inputs
Outputs
E.g. the Process of Budgeting:
Unspent
(unallocated)
Funds
Spent
(allocated)
Funds
Ian Perry
Funds
Remaining?
Budgeting
44221: Information Systems: Information Systems Concepts
Slide 19
Environment

Disturbs all Processes.
Goods are Damaged
Money Disappears
Unspent
(unallocated)
funds
Costs Rise
Budgeting
Funds
Remaining?
Spent
(allocated)
funds
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 20
Environment (continued)

Must make a distinction between:

External Environment - over which we have
little or no control.


Internal Environment - which we may be able
to control to some extent.

Ian Perry
E.g. the government puts up the rate of VAT,
causing our costs to rise.
E.g. Money is disappearing, so we implement a
new security system to attempt to catch the
member of staff who is stealing from us.
44221: Information Systems: Information Systems Concepts
Slide 21
Summary of Systems Concepts








System, Sub-system, Element
Concrete or Abstract Form
Hard or Soft Attributes
Components, Holism, Emergent Property
Boundary & Identity
Connection & Interaction
Process (Input(s) & Output(s))
Environment (External & Internal)
Ian Perry
44221: Information Systems: Information Systems Concepts
Slide 22
Workshop Sessions

Do you want to do well in this Module?


Taking part is not just about turning up:


You need to be prepared to contribute.
This week’s Workshop is all about:


36% of last year’s students failed the first assignment,
mainly because they didn’t ‘take part’ in the Workshops.
Applying the information systems concepts from this
week’s Lecture in order to begin the analysis of a
business as described by a Case Study.
So, in advance of the Workshop session:

Ian Perry
Read the ‘Local Parts’ Case Study, and attempt to
answer the questions.
44221: Information Systems: Information Systems Concepts
Slide 23