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

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Comprehensive Balanced Mathematics Model Elementary Okaloosa County School District Dr. Lynda Penry.
The Influence of Culture on Caregiving
Functions CSLU Fall 2007 Cameron McInally Fordham University.
Using the Crosscutting Concepts As conceptual tools when meeting an unfamiliar problem or phenomenon.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Bite sized training sessions: Objectives & Principles.
CS 128/ES Lecture 2b1 Attribute Data and Map Types.
“Working Surface Pairs & Channel and Support Structures”
PD1: Getting started.
CS 128/ES Lecture 2b1 Attribute Data and Map Types.
44221: Information Systems Lecture 5 (Week 6) Review & Ass 1 Requirements By Ian Perry
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
The Architecture Design Process
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Concurrent & Distributed Systems Lecture 6: Simulation (WWCH) What? –The use of an abstract model of a real engineering system, which can be implemented.
Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?
WEEK 4 Material Intro to Information Requirements & “Storyboarding the UCs” Monday “Paper Prototyping” Workshop by Bonnie Lecture 4b (Mon.)
Database Design Concepts Lecture 7 Introduction to E:R Modelling Identifying Entities.
Exam 3 Material Inequalities and Absolute Value
Network Modeling - Not Just For Computer Networks  Computer Networks  The need for network modeling is being driven by a technical trend – distributed.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
44220: Database Design & Implementation Logical Data Modelling Ian Perry Room: C48 Tel Ext.: 7287
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
44221: Information Systems Introduction to Module By:Ian Perry Room: C41C Tel:
44095: IT for Management Introduction to Spreadsheets (Basic/Complex Formulae & Worksheets) By:Ian Perry Room: C48 Tel:
Data Flow Diagrams (DFD). ScenarioCriteriaTasks Data flow diagram(DFD) is a diagram of the movement of data between external entities.
CSE 303 – Software Design and Architecture
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
Lecture 3 THE KEY SKILLS TESTED IN A DISSERTATION.
Version: 2.0 © University of Tasmania All rights reserved. CRICOS Provider Code: 00586B Accounting & Financial Decision Making BFA103BFA103.
CM602: Effective Systems Development Exam Preparation Slide 1 Exam Preparation Preparing for the CM602 Examination D.Miller J. Horton.
44221: Information Systems Worksheets & Named Ranges By:Ian Perry Room: C41C Tel:
44220: Database Design & Implementation Review & Assignment 2 Ian Perry Room: C49 Tel Ext.: 7287
44095: IT for Management Introduction to Module By:Ian Perry Room: C41C Tel:
Design Process 중앙대학교 전자전기공학부. Design for Electrical and Computer Engineers 2. Design Process  Engineering : Problem solving through specialized scientific.
BTEC L2 Business Enterprise/ICT Unit 2 – Business Organisations P2: Describe the purpose for a business in setting aims and objectives To understand why.
442421: Dissertation Interim Report Ian Perry Room: C49 Extension: 7287
44222: Information Systems Development Documenting a Solution Ian Perry Room:C41C Extension:7287
1 IRU – database design part one Geoff Leese September 2009.
44221: Information Systems Systems Concepts 2 By:Ian Perry Room: C48 Tel:
44095: IT for Management Review & Part 2 Requirements By:Ian Perry Room: C41C Tel:
44220: Database Design & Implementation Modelling the ‘Real’ World Ian Perry Room: C41C Ext.: 7287
44221: Information Systems Lecture 1 (Week 2) Introduction to Module By Ian Perry
Lesson Objectives All of you should be able to: Identify the parts of any given system. Most of you will be able to: Describe all elements of any given.
44220: Database Design & Implementation Review & Assignment 2 Ian Perry Room: C41C Tel Ext.: 7287
Researching and Writing Dissertations Roy Horn Researching and Writing Dissertations.
AP Lang and Comp April 8, 2014 Ms. Bugasch Goals 1. Compare/Contrast Essay - Edits and Revisions 2. AP Terms 3. Introduction to the rhetorical mode: definition.
44221: Information Systems Lecture 7 (Week 9) Organising Data & Presenting Information By Ian Perry
44095: IT for Management Systems Concepts 2 By:Ian Perry Room: C48 Tel:
44221: Information Systems Lecture 2 (Week 3) Information Systems Concepts By Ian Perry
Computer Science, Algorithms, Abstractions, & Information CSC 2001.
44221: Information Systems Review & Assignment 1 By:Ian Perry Room: C41C Tel:
CSE 303 – Software Design and Architecture
20CC Ltd Independent Consultants © 20CC Ltd Systems Thinking Overview Sources from The Open University acknowledged.
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
Systems Approach. MIS Defined …. “It is a system using formalised procedures to provide management at all levels in all functions with appropriate levels.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Activity & Class Modeling Labs Discussion p3 T120B pavasario sem.
44222: Information Systems Development Documenting a Solution Ian Perry Room:C49 Extension:7287
44220: Database Design & Implementation Introduction to Module Ian Perry Room: C41C Ext.: 7287
The design cycle model and the design process.
44220: Database Design & Implementation Review & Assignment 2 Ian Perry Room: C41C Tel Ext.: 7287
CompSci 280 S Introduction to Software Development
Data Flow Diagrams.
Unit 2 - Global Information
Presentation transcript:

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

Ian PerrySlide : Information Systems: Systems Concepts 2 Our Systems ‘view’ so far … System Sub-system Element Sub-system Element Sub-system Element Customers Supplier s Competitors The Government A System is composed of Elements grouped into Sub-systems. A System has a Boundary (which separates it from other Systems) and a ‘unique’ Identity (which distinguishes it from similar Systems). A System ‘exists’ within other Systems; which are referred to as the Environment of that System.

Ian PerrySlide : Information Systems: Systems Concepts 2 Components Systems are an organised whole, consisting of a number of component parts, i.e.; the Elements & Sub-systems. Components: Have a Form, which might be: Concrete Abstract Have Attributes, which might be: Hard Soft

Ian PerrySlide : Information Systems: Systems Concepts 2 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 Human Being. Concrete Money = the Coins & Notes in my Pocket. 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. a Pretty/Ugly Person. Abstract Money = my Total Worth.

Ian PerrySlide : Information Systems: Systems Concepts 2 Hard v Soft Attributes Hard components; do not depend upon someone’s personal sense of value. Easy to define/quantify/measure. E.g. The dimensions of a Room. Hard Money = 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 nice Room. Soft Money = Value for money.

Ian PerrySlide : Information Systems: Systems Concepts 2 So What? Beware the Abstract/Soft. Concrete/Hard Components, are quite easy to identify, as they: tend to ‘appear’ the same to different individuals. and are easy to define/quantify/measure. Abstract/Soft Components, are often difficult to identify, as they: may ‘appear’ differently to different individuals. and are, therefore, difficult to define/quantify/measure. Do NOT, however, ignore the Abstract/Soft; as all Systems contain Abstract/Soft Components.

Ian PerrySlide : Information Systems: Systems Concepts 2 Holism Systems thinking is all about considering the whole System; and its relationship with other whole Systems. The general principle of holism, as concisely stated by Aristotle, is that; “The whole is more than the sum of its parts”. A more modern definition is that; the properties of a given system cannot be determined or explained by the sum of its component parts alone. (

Ian PerrySlide : Information Systems: Systems Concepts 2 Emergent Property Emergent Properties; occur/arise; because of the interaction between the components of a System and its environment. result in; what the System as a whole, or a component of the System (i.e. Sub-system and/or Element), is supposed to (i.e. has been designed to) achieve. may not always be as intended; e.g. users may adapt products to support tasks that designers never intended.

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

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

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

Ian PerrySlide : Information Systems: Systems Concepts 2 Connection & Interaction (continued) System A Sub-system Element Sub-system Element System C Sub-system Element Sub-system Element System B Sub-system Element Sub-system Element Sub-system Element System A is ‘usually’ supplied with raw materials by System B. However, if System B is unable to supply ‘enough’ raw materials, they can be sourced from System C.

Ian PerrySlide : Information Systems: Systems Concepts 2 Connection & Interaction (continued) Naming the Sub-systems can make the Connections & Interactions easier to understand. Competitors Government System Customer Services Warehousing Manufacturing Element Customers Suppliers Element

Ian PerrySlide : Information Systems: Systems Concepts 2 Connection & Interaction (continued) Customer Services Customers Sub-System Warehousing Manufacturing Sub-System Element Concentrate on ONE of the original Sub-systems at a time; and ‘view’ it as a System, in order to explore the Connections & Interactions in more detail. NB. The Sub-systems of this ‘view’ were the Elements of the previous ‘view’ of the whole System.

Ian PerrySlide : Information Systems: Systems Concepts 2 Systems Concepts from this Lecture Components Concrete/Abstract Form Hard/Soft Attributes Holism & Emergent Property Connection & Interaction

Ian PerrySlide : Information Systems: Systems Concepts 2 This Week’s Workshop Apply the information systems concepts from this week’s Lecture, in order to; analyse, in greater detail, the business as described by the ‘Local Parts’ Case Study. In advance of the Workshop session: Read the updated Case Study; attempt to answer the questions; and be prepared to contribute. Assignment 1? I hope you have all had a go at Assignment 1 by now. If not, then don’t leave it too late to begin; IS Analysis is NOT a trivial task.