1. 44221: Information Systems Lecture 2 (Week 3) Information Systems Concepts By Ian Perry http://itsy.co.uk/ac/0506/Sem1/44221_IS/

2. Ian PerrySlide 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.

3. Ian PerrySlide 344221: Information Systems: Information Systems Concepts Levels of Management Strategic Long-Term Tactical Short-Term Operational Day-to-Day

4. Ian PerrySlide 444221: Information Systems: Information Systems Concepts Business Functions

5. Ian PerrySlide 544221: Information Systems: Information Systems Concepts Matrix (i.e. Functions & Levels) MarketingProductionFinancePersonnel FUNCTION Operational Tactical Strategic LEVEL

6. Ian PerrySlide 644221: Information Systems: Information Systems Concepts 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.

7. Ian PerrySlide 744221: Information Systems: Information Systems Concepts System, Sub-system, Element This, however, is NOT a very ‘good’ systems diagram.

8. Ian PerrySlide 844221: Information Systems: Information Systems Concepts A ‘better’ systems diagram? System Sub-system Element

9. Ian PerrySlide 944221: Information Systems: Information Systems Concepts 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

10. Ian PerrySlide 1044221: Information Systems: Information Systems Concepts 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.

11. Ian PerrySlide 1144221: Information Systems: Information Systems Concepts 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.

12. Ian PerrySlide 1244221: Information Systems: Information Systems Concepts 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.

13. Ian PerrySlide 1344221: Information Systems: Information Systems Concepts Components, Holism, Emergent Property Aeroplane Fuselage Tail Wing Engine Flight a Hard/Concrete Example

14. Ian PerrySlide 1444221: Information Systems: Information Systems Concepts Components, Holism, Emergent Property Order Processing Customer Requirements Product Knowledge Customer Satisfaction a Soft/Abstract Example

15. Ian PerrySlide 1544221: Information Systems: Information Systems Concepts 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.

16. Ian PerrySlide 1644221: Information Systems: Information Systems Concepts Boundary & Identity (continued) System A System B

17. Ian PerrySlide 1744221: Information Systems: Information Systems Concepts 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.

18. Ian PerrySlide 1844221: Information Systems: Information Systems Concepts Connection & Interaction (continued) System A System B System C

19. Ian PerrySlide 1944221: Information Systems: Information Systems Concepts 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

20. Ian PerrySlide 2044221: Information Systems: Information Systems Concepts Environment Disturbs all Processes. Money DisappearsCosts Rise Goods are Damaged Budgeting Unspent (unallocated) funds Spent (allocated) funds Funds Remaining?

21. Ian PerrySlide 2144221: Information Systems: Information Systems Concepts Environment (continued) Must make a distinction between: External Environment - o ver which we have little or no control. E.g. the government puts up the rate of VAT, causing our costs to rise. Internal Environment - w hich 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.

22. Ian PerrySlide 2244221: Information Systems: Information Systems Concepts 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)

23. Ian PerrySlide 2344221: Information Systems: Information Systems Concepts 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.