44221: Information Systems Systems Concepts 2 By:Ian Perry Room: C48 Tel: 01723 35 7287

Slides:



Advertisements
Similar presentations
Construct Detailed Analysis Identify the techniques employed in analyzing the information: a.Entity Life History b.Relational Data Analysis c.Context Diagram.
Advertisements

Software Engineering-II Sir Zubair Sajid. 3 Data Flow Diagrams (DFD)  DFDs describe the flow of data or information into and out of a system what does.
How to submit your coursework. The University is changing the way coursework is submitted. Over the next academic year we will be phasing out paper and.
SYSTEMS ANALYSIS AND DESIGN TOOLS
CAEL Prior Learning Assessment Process Mapping – Session 2 Facilitator – Eric Heller
Lecture 9 Descriptors, Events & Event Tables INFO1409 Systems Analysis & Design Module HND Year /9.
How to : Data Flow Diagrams (DFDs)
Finding Threads and Themes.  Exam Outline  The Process  Writing  Tips from Blackboard  A Metaphor?
44221: Information Systems Lecture 5 (Week 6) Review & Ass 1 Requirements By Ian Perry
Software Engineering: Analysis and Design - CSE3308
DT211 Stage 2 Software Engineering
Spreadsheets in Finance and Forecasting Project Session 3b(ii) Data Flow Diagrams.
WEEK 4 Material Intro to Information Requirements & “Storyboarding the UCs” Monday “Paper Prototyping” Workshop by Bonnie Lecture 4b (Mon.)
DT211 Stage 2 Software Engineering
Database Design Concepts Lecture 7 Introduction to E:R Modelling Identifying Entities.
System Analysis and Design
Using Turnitin K. Robins and K. McCourt. Aims of Session To be aware of the benefits of using Turnitin for formative feedback; To be able to set up Turnitin.
Data Flow Diagrams (DFDs)
Model the User Experience Today:  Detail some Use Cases  Develop a storyboard of the use cases  Sketch mock-ups of the use case's information requirements.
Tutorial 6 DFDs vs. Use Case Diagrams (Textbook Chapter 7 & Appendix)
Introduction Operations Management Intermediate Business Management.
IT323 - Software Engineering 2 Tutorial 1. 0 The system 1.0 A Function 1.1 Activity of the function Task Task Task 1.2 Another activity.
44220: Database Design & Implementation Logical Data Modelling Ian Perry Room: C48 Tel Ext.: 7287
44221: Information Systems Introduction to Module By:Ian Perry Room: C41C Tel:
Data Flow Diagrams.
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
Data-Flow Diagrams Week 10 Lecture 1. Data Flow Diagrams (DFDs) One of most important modelling tools used by system analysts In use since late 1970’s.
G041: Lecture 13 Examination Preparation Mr C Johnston ICT Teacher
44222: Information Systems Development Operational & Information Systems Ian Perry Room:C41C Extension:7287
44095: IT for Management Introduction to Module By:Ian Perry Room: C41C Tel:
44222: Information Systems Development Introduction to Module Ian Perry Room: C41C Extension: 7287
44221: Information Systems Lecture 3 (Week 4) Systems Concepts 2 By Ian Perry
Testing and Debugging Version 1.0. All kinds of things can go wrong when you are developing a program. The compiler discovers syntax errors in your code.
DFDs.
ICT IGCSE.  Introducing or changing a system needs careful planning  Why?
SYSTEMS ANALYSIS AND DESIGN TOOLS DATA FLOW DIAGRAMS.
442421: Dissertation Interim Report Ian Perry Room: C49 Extension: 7287
44095: IT for Management Review & Part 2 Requirements By:Ian Perry Room: C41C Tel:
University of Sunderland ISIC 1 Data Flow Diagrams - Part 2 Hierarchical DFDs.
44221: Information Systems Lecture 1 (Week 2) Introduction to Module By Ian Perry
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Context Diagrams IPT Context Diagrams Context diagrams are used to represent entire information systems. The system is shown as a single process.
INFO1002 Systems Modelling Lecture 10 Establishing User Requirements Department of information Systems.
44095: IT for Management Systems Concepts 2 By:Ian Perry Room: C48 Tel:
44221: Information Systems Lecture 3 (Week 4) Systems Control Concepts By Ian Perry
44221: Information Systems Lecture 2 (Week 3) Information Systems Concepts By Ian Perry
44221: Information Systems Review & Assignment 1 By:Ian Perry Room: C41C Tel:
44220: Database Design & Implementation Conceptual Data Modelling Ian Perry Room: C49 Tel Ext.: 7287
44220: Database Design & Implementation Introduction to Module Ian Perry Room: C49 Ext.: 7287
Context Diagram This section includes two parts. Part 1: Description of a Context Diagram Part 2: How To construct a Context Diagram.
Btec National - IT SYSTEMS ANALYSIS AND DESIGN 1 IT Systems Analysis and Design SSADM – Design.
HNC Flow Chart 1 IT Systems Analysis and Design SSADM – Design.
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
44220: Database Design & Implementation Introduction to Module Ian Perry Room: C41C Ext.: 7287
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Using Dataflow Diagrams Systems Analysis and Design, 8e Kendall & Kendall 7.
Day 4 – Process Modeling cont’d Today’s Goals  More on Process Models  Leveling DFDs  Exercise 5 – in class  Group Project / Client Project reminders.
Advanced Higher Computing Science
WHAT IS A Context Diagram?
G063 - Data flow diagrams.
Data Flow Diagrams.
GCE Applied ICT G041: Lesson 13 Examination Preparation
[insert Module title here]
Systems Analysis and Design
Object Oriented Design Model
[insert Module title here]
G063 - Data flow diagrams.
[insert Module title here]
[insert Module title here]
Software design and architecture
How to submit your coursework
Presentation transcript:

44221: Information Systems Systems Concepts 2 By:Ian Perry Room: C48 Tel:

Ian PerrySlide : Information Systems: Systems Concepts 2 The Previous Lecture Introduced the following systems concepts: System, Sub-system, Element Boundary & Identity Environment External Internal Connection & Interaction And went on to show how all of the above could be depicted using relatively simple diagrams.

Ian PerrySlide : Information Systems: Systems Concepts 2 A ‘System in Context’ Diagram The System is composed of a number of Sub- systems (i.e. the Internal Environment). The System has a Boundary (which separates it from other Systems) and a ‘unique’ Identity (which distinguishes it from similar Systems). The System ‘exists’ within other Systems (i.e. the External Environment). Showing that;

Ian PerrySlide : Information Systems: Systems Concepts 2 A ‘High Level Systems Diagram’ Names the Elements which are components of each Sub-System. Shows the connections & interactions; Which, in addition to all of the things that the ‘Systems in Context’ diagram included, also; And between this System & other Systems (i.e. in the External Environment). between the Elements of each Sub-System (i.e. in the Internal Environment).

Ian PerrySlide : Information Systems: Systems Concepts 2 What now? Having previously ‘discovered’; the main building blocks of the system under investigation, i.e.: sub-systems & elements. and a number of important External Environmental factors, e.g.: Customers, Suppliers, etc. We must now explore the system in much more detail; especially the connection and interaction of the components of the system.

Ian PerrySlide : Information Systems: Systems Concepts 2 Why? Our aim is to understand (i.e. name) the Information flows: Connecting the System with its External Environment, i.e.: Interactions between specific elements, of specific sub-systems; and other systems that exist in the external environment. Connecting the sub-systems of the Internal Environment, i.e.: Interactions between specific elements, of specific sub-systems; and other sub-systems within the internal environment.

Ian PerrySlide : Information Systems: Systems Concepts 2 Our ‘Systems View’ so far: Shows what is connected to what; BOTH Internally and Externally. What we now need to discover is what information is flowing along each of these connections. Can’t ‘simply’ add the information flows to this diagram; would become VERY messy. So, we ‘zoom-in’ on one sub-system at a time.

Ian PerrySlide : Information Systems: Systems Concepts 2 A ‘Detailed Information Flow Diagram’ The ‘Elements’ are Processes which were ‘hidden’ on the ‘High- level Systems Diagram’. Processes require ‘Inputs’ (i.e. data) and produce ‘Outputs’ (i.e. information). Customer Services is the System. Do we now know ‘enough’ to suggest where IT might be employed effectively?

Ian PerrySlide : Information Systems: Systems Concepts 2 Customer Interaction? Two Processes Receive Request Input “Product Request” – Customer - External Environment Output “Product Availability?” – Check Stock - Warehouse Interaction Inform Customer Inputs “Products Available” - Check Stock - Warehouse Interaction “Will be Delay!” – Awaiting Manufacture - Manufacture Interaction Output “Yes/Delay” – Customer - External Environment Everything is ‘known’. Should be able to suggest where IT might be employed effectively.

Ian PerrySlide : Information Systems: Systems Concepts 2 Manufacture Interaction? Two Processes Request More Input “Need more of Product x” – Check Stock - Warehouse Interaction Output “Manufacture more Product x – ??? – Manufacturing Sub-system Awaiting Manufacture Inputs “Will take n days” - ??? – Manufacturing Sub-system Output “Delay!” – Inform Customer – Customer Interaction Everything isn’t ‘known’. Need to ‘zoom-in’ on Manufacturing Sub-system, before suggesting where IT might be employed effectively.

Ian PerrySlide : Information Systems: Systems Concepts 2 Warehouse Interaction? One Process Check Stock Inputs “Product Availability?” – Receive Request - Customer Interaction “Yes/No!” - ??? – Warehousing Sub-system Outputs “Are Products Available?” – ??? – Warehousing Sub-system “Need more of Product x” – Request More – Manufacture Interaction “Yes!” – Inform Customer – Customer Interaction Everything isn’t ‘known’. Need to ‘zoom-in’ on Warehousing Sub-system, before suggesting where IT might be employed effectively. AND, perhaps ‘Check Stock’ is actually more than one process?

Ian PerrySlide : Information Systems: Systems Concepts 2 This Week’s Workshop Taking the output of the previous Workshop as a starting point, we will; attempt to draw a ‘Detailed Information Flow Diagram’, for ONE of the sub-systems of the organisation as described by the ‘GIC’ Case Study. And then see if this detailed ‘view’ of the system enables us to answer the question: Where, and how, might Information Technology (IT) be used to improve the efficiency and/or effectiveness of Case Study organisation’s information system?

Ian PerrySlide : Information Systems: Systems Concepts 2 Assignment 1? DO NOT leave it too late to begin working on your Assignment. You should already have attempted to answer Part 1 a) of Assignment 1, i.e.; Draw a ‘High Level Systems Diagram’ of ‘EZPC’. After this week’s workshop you should attempt to do the same for: Part 1 b) of Assignment 1, i.e.: Draw a ‘Detailed Information Flow Diagram’ of ONE of the Sub-systems of ‘EZPC’. Part 2 of Assignment 1, i.e.: Discuss where, and how, Information Technology might be used to improve the efficiency and/or effectiveness of this specific Sub-system.

Ian PerrySlide : Information Systems: Systems Concepts 2 Assignment Hand-in Process You MUST hand in TWO copies of each Assignment for this Module. BOTH copies must be submitted by 3pm of the submission date. An Electronic Copy (via Turnitin) See the ‘Assessment Method’ page of the ‘IS Web-site’; in order to find out how to enrol for & use Turnitin. The ‘Class ID’ and ‘Password’ for the IS Module are: Class ID:42019 Password:1224 Make sure that you submit to the correct place, i.e.: Code Name:E1 – IS Analysis A ‘Paper’ Copy (to the School Office) With properly completed Front-sheets, and a Turnitin receipt, in the correct drawer of the wooden filing cabinet outside of CH5.