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

2. Ian PerrySlide 244221: Information Systems: Introduction to Module Why study Information Systems? An understanding of Information Systems is vital to business management and information technology students: As all business organisations rely upon the ability of their Information Systems to provide/support the knowledge required for all levels of decision-making, i.e.: Strategic Tactical Operational

3. Ian PerrySlide 344221: Information Systems: Introduction to Module Learning Outcomes? By the end of the module you will be able to: Understand why a distinction must be made between data, information & knowledge. Identify the role of Information Systems in a given business context. Relate theoretical models of Information Systems to business cases, by describing a given situation using systems terminology. Produce working examples of computer-based Information Systems tools to address specific business needs.

4. Ian PerrySlide 444221: Information Systems: Introduction to Module Assessment Method Two, equally weighted, assignments; based upon a common Case Study. Assignment 1 - Information Systems Analysis Deadline = 26 October 2005; Weighting = 50% Describe a business situation, as presented by the case study scenario, using appropriate systems language. Identify specific processes within the case study organisation that might benefit from the development of computer-based Information Systems tools. Assignment 2 - Information Systems Tools Deadline = 07 December 2005; Weighting = 50% Produce a working example of an IS Tool that will support part of the Information System, as described by Assignment 1. Produce a short report explaining how this IS Tool might be used in support of decision making.

5. Ian PerrySlide 544221: Information Systems: Introduction to Module EZPC – Case Study EZPC assemble PC Systems for sale to customers such as PC World, Dixons, Currys, etc. Each PC is ‘made-to-order’ (as a result of a request from a specific customer), based on a limited set of ‘Standard’ PC Configurations. Computer components (i.e. Processors, Hard Disks, Memory, etc.), from which the PC systems are assembled, are purchased from a number of suppliers. EZPC also sells these computer components directly to their Customers. The components, either waiting to be assembled into PC Systems, and/or passed on directly to EZPC’s customers; are stored at three different warehouse locations, i.e.: Newcastle, Leeds & Reading.

6. Ian PerrySlide 644221: Information Systems: Introduction to Module EZPC – Case Study (continued) At each of these locations: A sales team deals with their local customers. A second group of staff work out what components are required to fulfill each customer order. A third group of staff assemble the PCs. A fourth group of staff control the warehouse operations; ordering & receiving components from suppliers, passing components on to the assembly process, receiving completed PCs back from the assembly process, packing PCs and components prior to delivery. Delivery of PCs and components is contracted out to a national distribution company.

7. Ian PerrySlide 744221: Information Systems: Introduction to Module EZPC – Case Study (continued) The Leeds warehouse acts as the Head Office for EZPC. all dealings with EZPC’s suppliers are controlled from the Leeds Head Office. At each warehouse location: Customer ‘requests’ for components are passed directly to the Warehouse, as a ‘component list’. Customer ‘requests’ for PCs are passed to the Planning Department who translate each Customer ‘request’ into an ‘work order’ for the Assembly Department. the Assembly Department must then check with the Warehouse for the availability of enough PC components in order to complete each ‘work order’ before commencing assembly.

8. Ian PerrySlide 844221: Information Systems: Introduction to Module EZPC – Case Study (continued) if a ‘work order’ can not be completed, due to a lack of components, then the Warehouse must raise a ‘purchase order’ (via the Head Office) with one of EZPC’s Suppliers. When enough components are received from EZPC’s Suppliers, then the Warehouse notifies the Assembly Department and the assembly process can commence. Once the Assembly Department has completed a ‘work order’, then the assembled PCs are passed on to the Warehouse. The Warehouse then produces ‘delivery lists’ for each Customer’s order, and uses these as ‘picking lists’ in order to find the PCs and/or components in the warehouse, and pack them ready for delivery.

9. Ian PerrySlide 944221: Information Systems: Introduction to Module EZPC – Case Study (continued) Problems? Each ‘work order’ is currently produced by hand, which is both very time consuming and often leads to mistakes, both of which upset the customers. Each of the Warehouses is quite small, and can only hold a small stock of computer components and assembled PCs, so ‘work orders’ often become ‘purchase orders’ (once again a manual calculation). Raising a ‘purchase order’ with one of EZPC Suppliers, can result in a delay of up to 10 days for the delivery of the computer components. Often, even when Warehouse is almost full of computer components, a ‘work order’ cannot be completed, as these are the wrong components with which to satisfy a specific customer ‘request’.

10. Ian PerrySlide 1044221: Information Systems: Introduction to Module Lectures (CG3) Workshops (IT3/4) 2. Introduction to Module 3. Systems Concepts 4. Systems Control Concepts 5. Decision Making Concepts 6. Review & Ass 1 Reqs 7. Assignment 1 Deadline 8. Intro to Spreadsheets 9. Org. Data / Present Info. 10. Spreadsheet Automation 11. Review & Ass 2 Reqs 12. -- No Lecture -- 13. Assignment 2 Deadline 2. Web-site & Assessment 3. Business Analysis 4. Control Systems 5. Decision Making 6. Assignment 1 Support 7. Assignment 1 Deadline 8. Useful SS Functions 9. Worksheets & Charts 10. Macros & Printing 11. Assignment 2 Support 12. Assignment 2 Support 13. Assignment 2 Deadline

11. Ian PerrySlide 1144221: Information Systems: Introduction to Module Data, Information & Knowledge A clear understanding of difference between Data, Information & Knowledge is crucial if you are to be able to understand/develop an Information System. What is Data? A series of observations, measurements, or facts (transactions/events). Collins Concise English Dictionary E.g. 12 Ian Sunny

12. Ian PerrySlide 1244221: Information Systems: Introduction to Module Data  Information What is Information? ‘data that have been transformed into a meaningful and useful form for people’. ‘data placed in a context and given value by specific end-users’. Process DataInformation (perhaps!)

13. Ian PerrySlide 1344221: Information Systems: Introduction to Module Information Attributes Information (or do I mean data?) can be thought of as having three dimensions: Time Timeliness, Currency, Frequency, etc. Content Accuracy, Relevance, Completeness, etc. Form Clarity, Detail, Order, Presentation, etc. Information is often affected by more than one of the above.

14. Ian PerrySlide 1444221: Information Systems: Introduction to Module What is this? - 120505 Why did you say that? People tend to look for a familiar structure & place data in a familiar context, e.g.: 120505 => DD/MM/YY => 12/05/05 => 12 May 2005 We use structure & context to transform the data we receive into information. However: Different people see different structures and/or might apply different contexts to the data they receive: What if you were me?

15. Ian PerrySlide 1544221: Information Systems: Introduction to Module So? Information = Data + Structure + Context The same data can give different information if a different structure and/or context is applied. Try these: SSMTW_what letter is next? SDLMM_what letter is next?

16. Ian PerrySlide 1644221: Information Systems: Introduction to Module Knowledge What is Knowledge? That which is gained by the possession of information. Enabling people to: have a ‘better’ understanding of a situation And/Or: make ‘better’ decisions.

17. Ian PerrySlide 1744221: Information Systems: Introduction to Module An Information Systems Approach Information Systems  Computer Systems Need to take a holistic view of: Organisation, People, and Technology. People Technology Organisation

18. Ian PerrySlide 1844221: Information Systems: Introduction to Module Summary Data  Information: Data are simply facts relating to ‘things’ like events, transactions, etc. Information: is a people thing, because only they can determine the structure & context with which data might become information. Knowledge: is gained by the possession of information that enables people to have a ‘better’ understanding of a situation and/or make ‘better’ decisions.

19. Ian PerrySlide 1944221: Information Systems: Introduction to Module Always Remember This! “Data is only potential information; information is potential knowledge; and knowledge is potential competitive advantage if it is used in a creative, flexible, and above all, accurate way.” Adrian M (1990) Let’s Get Serious. Focus News. Winter.

20. Ian PerrySlide 2044221: Information Systems: Introduction to Module IS Reading List It is difficult to recommend just one book for this module, so I won’t. Instead, here is a list of those Information Systems books that may prove useful to aid your understanding of this module (NB. all of these can found in the KDL, Scarborough Library). Benyon-Davies P, 2002, Information Systems: An Introduction to Informatics in Organisations, Palgrave. ISBN: 0333963903, KDL: 658.4038011 BEN Bocij, Chaffey, et al, 2003, Business Information Systems: Technology, Development and Management for the E-business, Pearson Education. ISBN: 027365540x, KDL: 658.40380285 BOC Cleary T, 1998, Business Information Technology. Financial Times/Pitman Publishing. ISBN: 0273634100, KDL: 658.4038 CLE

21. Ian PerrySlide 2144221: Information Systems: Introduction to Module IS Reading List (continued) Cobham & Curtis, 2005 [5th Ed.], Business information Systems: Analysis, Design, and Practice, Financial Times/Prentice Hall. ISBN: 0273687921, KDL: 658.4038011 CUR Gordon & Gordon, 2004, Information Systems: A Management Approach, Wiley. ISBN: 0471455490, KDL: 658.4038011 GOR Harry M, 2001, Business Information: A Systems Approach, Pearson Education Limited. ISBN: 0273646702, KDL: 658.4038011 HAR Martin E W, 2005, Managing Information Technology, 5th ed., Prentice Hall. ISBN: 0131293710, KDL: 658.4038 MAR Whiteley D, 2004, Introduction to Information Systems: Organisations, Applications, Technology, and Design, Palgrave Macmillan. ISBN: 0333997662, KDL: 658.4038011 WHI

22. Ian PerrySlide 2244221: Information Systems: Introduction to Module You can not afford to miss anything! DO NOT leave Assignments to the last minute: Quite a few of last year’s students failed Assignment 1 for the IS Module. DO NOT miss any Lecture or Workshop sessions. There are Lectures & Workshops for the IS Module almost EVERY WEEK. The first IS Workshop sessions will take place THIS WEEK, i.e.: 11:15 to 1:05, on Tuesday, in IT3. 11:15 to 1:05, on Wednesday, in IT4. Make sure that you know which Workshop you should attend; BEFORE you leave this Lecture.

23. Ian PerrySlide 2344221: Information Systems: Introduction to Module Web-site Development The WSD Lectures (which take place every other week) will begin THIS WEEK; i.e.: 9:15 to 10:05, on Friday, in CG1 The WSD Workshops (which also take place every other week) will begin NEXT WEEK: 11:15 to 1:05, on Friday, in IT4