44221: Information Systems Lecture 2 (Week 3) Information Systems Concepts By Ian Perry

44221: Information Systems

Lecture 2 (Week 3)

Information Systems Concepts

By Ian Perry

http://itsy.co.uk/ac/0506/Sem1/44221_IS/

Ian Perry Slide 244221: Information Systems: Information Systems Concepts

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: 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.


Levels of Management

StrategicLong-Term

TacticalShort-Term

OperationalDay-to-Day


Business Functions

Director

Etc. Etc. Etc.

Etc.

Product ion

Director

Etc. Etc.

Etc.

M arket ing

Director

Etc. Etc. Etc.

Etc.

Personnel

Director

Etc. Etc.

Etc.

Finance

O rganisat ion


Matrix (i.e. Functions & Levels)

Marketing

Production

Finance Personnel

FUNCTION

Operational

Tactical

Strategic

LEVEL


System A set of interrelated components which act

together in an organised way in order to achieve an objective. A System should have a known/defined/agreed

purpose. As with data/information/knowledge, each

System may be: defined/viewed/interpreted in different ways by

different people. Systems Concepts provide a common language

with which to describe Systems of all types. diagrams are VERY IMPORTANT.


System, Sub-system, Element

E lement E lement

S ub - sys t em E lement

S ys t em

This, however, is NOT a very ‘good’ systems diagram.


A ‘better’ systems diagram?

System

Sub-system

Sub-system

Sub-systemElement

Element

Element

Element

Element

ElementElement


Components Systems are an organised whole,

consisting of a number of component parts, i.e.: The elements of our previous system, sub-

system, elements view. These Components:

Have a Form, which can be: Concrete Abstract

Have Attributes, i.e. characteristic properties, which can be:

Hard Soft


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. Abstract components may ‘appear’ differently to

different individuals. E.g. Pretty/Ugly, Information. Abstract Money = A Bank Statement.


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.: A lot of money. Value for money.


So What? Beware the Abstract/Soft.

Concrete/Hard Components, are quite easy to identify, as they:

tend to ‘appear’ the same to different individuals.

are easy to define/quantify/measure. Abstract/Soft Components, are often very

difficult to identify, as they: may ‘appear’ differently to different individuals. are difficult to define/quantify/measure.


Components, Holism, Emergent Property

AeroplaneFuselageTail

WingEngine

Flight

a Hard/Concrete Example


Components, Holism, Emergent Property

OrderProcessing

CustomerRequirements

ProductKnowledge

CustomerSatisfaction

a Soft/Abstract Example


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; to define which components are a part of this

system. All systems must have an identity;

to distinguish them from other similar systems.


Boundary & Identity (continued)

System A

System B


Connection & Interaction Systems do not exist in isolation:

they are both ‘connected to’ and ‘interact with’ other systems.

Connection between systems may be: Permanent or Ad-hoc.

Interaction between systems is, in most cases, considered to be: A two-way process.


Connection & Interaction (continued)

System A

System B

System C


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:

Budgeting

Unspent(unallocated)Funds

Spent(allocated)Funds

Remaining?Funds


Environment Disturbs all Processes.

Money Disappears Costs Rise

Goods are Damaged

Budgeting

Unspent(unallocated)funds

Spent(allocated)funds

FundsRemaining?


Environment (continued)

Must make a distinction between: External Environment - over which we

have little or no control. E.g. the government puts up the rate of

VAT, causing our costs to rise. Internal Environment - which we may be

able to control to some extent. 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.


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)


Workshop Sessions Do you want to do well in this Module?

36% of last year’s students failed the first assignment, mainly because they didn’t ‘take part’ in the Workshops.

Taking part is not just about turning up: You need to be prepared to contribute.

This week’s Workshop is all about: 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: Read the ‘Local Parts’ Case Study, and attempt to

answer the questions.

44221: Information Systems Lecture 2 (Week 3) Information Systems Concepts By Ian Perry

Documents

information systems

information systemslecture

good systems diagram

abstract components

levelsian perryslide

isian perryslide

hardsoftian perryslide

soft components