Analysing Systems Failures (1) Main Principles: systems thinking.

Slides:



Advertisements
Similar presentations
© Loughborough University, 2004 Types of Systems There are a number of ways in which we may define types of systems.
Advertisements

UFCE8V-20-3 Information Systems Development 3 (SHAPE HK) Lecture 16 Systems & Systems Thinking.
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Database Systems: Design, Implementation, and Management Tenth Edition
Spring ÇGIE398 - lecture 10 SSM in detail1.
Sharda University School of Business Studies. SYSTEMS THEORY Provides a general analytical framework (perspective) for viewing an organization.
Design Concepts and Principles
Using the Crosscutting Concepts As conceptual tools when meeting an unfamiliar problem or phenomenon.
Software Failure: Reasons Incorrect, missing, impossible requirements * Requirement validation. Incorrect specification * Specification verification. Faulty.
The Managerial Environment
Family Systems Theory. Beginnings In the 1950s Dr. Murry Bowen introduced a transformational theory, Family Systems Theory.
Organizational Behavior Managing Organizational Change and Development Chapter 18 It’s all about: CHANGE.
IMS1805 Systems Analysis Topic 2: Introduction to some key techniques for systems analysis in IS.
System Theory A quick look at systems. General Systems Theory Ludwig von Bertalanffy Peter Checkland General Systems Theory: There are parallels found.
COMM : Applied Organizational Communication Instructor: Dan Lair Day Six: Systems Thinking Approaches to Organizational Communication September.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
Applying Systems Theory to Organizations and Families CSD 5970 Bruce Barnard.
Object Oriented Software Development Systems and Models Seminar: Week 1 Brian Farrimond.
Notion of a Project Notes from OOSE Slides - modified.
CSE Information Systems 1 IMS Information Systems 1 Revision.
Lecture 1: Systems super systems, systems & subsystems SYS366.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
PowerPoint Presentation by Charlie Cook Copyright © 2003 South-Western/Thomson Learning. All rights reserved. Environment: Culture, Ethics, and Social.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Supplement 02 (a)Systems Theory1 Supplement 02 (a) Systems Theory And Franchise Colleges By MANSHA NAWAZ.
03/12/2001 © Bennett, McRobb and Farmer What Are Information Systems? Based on Chapter 1 of Bennett, McRobb and Farmer: Object Oriented Systems.
Course Instructor: Aisha Azeem
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
Chapter 9 Architecture Alignment. 9 – Architecture Alignment 9.1 Introduction 9.2 The GRAAL Alignment Framework  System Aspects  The Aggregation.
SYSTEM ANALYSIS AND DESIGN
Monitoring Evaluation Impact Assessment Objectives Be able to n explain basic monitoring and evaluation theory in relation to accountability n Identify.
CS3500 Software Engineering How does a “program” differ from a “software system”? Program System Tens to hundreds of lines of code Thousands to millions.
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
SOFTWARE DESIGN DOCUMENT (SDD)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
Unit 5: Feedback and control theory An Introduction to Mechanical Engineering: Part Two Feedback and control theory Learning summary By the end of this.
Crosscutting Concepts Next Generation Science Standards.
Management & Development of Complex Projects Course Code MS Project Management Project Life Cycle & PM Process Groups Lecture # 4.
Management 337 / Summer 2005 / Organization Theories / Slide # 1 Organization Theories.
Oktalia Juwita, S.Kom., M.MT. FOUNDATION CONCEPTS OF INFORMATION SYSTEM Dasar-dasar Sistem Informasi – IKU1102.
The chapter discusses 5 major aspects of organizational behavior. Which of the following is NOT one of them: (1) Attitudes (2) Roles (3) Norms (4) Self-Concept.
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.
Accounting Information System. System A system is a set of parts coordinated to accomplish a set of goals. It is also an organized set of interrelated.
Organizational Behaviour What is an organization? Is a group of individuals working together to achieve common goals and structured into a division of.
Chapter 2 A systems view of project management. Learning objectives apply systems theory to explain the interrelations between project elements discuss.
Spring ÇGIE398 - lecture 51 lecture 5 : systems models and diagrams this lecture is about modelling modelling influence diagrams flow charts, precedence.
20CC Ltd Independent Consultants © 20CC Ltd Systems Thinking Overview Sources from The Open University acknowledged.
Principles of Software Engineering: Why Study Software Engineering? COSI 120b, Spring 2005.
Chapter 3 Stephen Littlejohn Theories of Human Communication
Systems Approach. MIS Defined …. “It is a system using formalised procedures to provide management at all levels in all functions with appropriate levels.
MIS.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Lecture 3 : Hard Systems Modelling UFCE8V-20-3 Information Systems Development SHAPE Hong Kong 2010/11.
System A system is a set of elements and relationships which are different from relationships of the set or its elements to other elements or sets.
M253 Team Work in Distributed Environments Week (3) By Dr. Dina Tbaishat.
THE SCIENTIFIC METHOD IN THE HISTORY CLASSROOM AND OTHER THEORETICAL APPROACHES.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter2: Systems Engineering l Designing, implementing, deploying and operating.
Introduction to OOAD and UML
T306 managing complexity: a systems approach TUTORIAL 7 BLOCK 1 – PART 4.
B121 Chapter 6 Effective Ways of Displaying Information.
Introduction to Information Systems 1.2 Systems Theory.
Lecture 9- Design Concepts and Principles
What is a system? A collection of components organized to accomplish a specific function or set of functions. [IEEE STD ]
Block-04 Management & organizations
IE352 System Analysis and Design
Lecture 9- Design Concepts and Principles
Organisations and systems (Chapter 2)
Presentation transcript:

Analysing Systems Failures (1) Main Principles: systems thinking

A systems approach Finkelstein in the CAPSA analysis: “A system is an organised whole comprised of a set of interrelated components. CAPSA is a system whose components are other systems. These systems include software and computing hardware - but are not restricted to it.” i.e. management and human activities are also part of a system.

Using systems ideas to analyse reasons for failure Situations of failure occur in situations where internal complexity and influences from an external environment are strong. Most organisational situations are like this. Raises the question: what is needed for an effective and adaptable organisational system?

Systems Thinking in general Seeing situations in terms of complex interactions between different parts. Change in one part of the situation can have unpredicted (and unpredictable?) knock-on effects elsewhere. May involve comparing a messy, real-world situation with an ideal expressed in systems terms.

System Concepts systems have boundaries distinguishing them from their environments systems have inputs and outputs transformations occur within systems systems have a hierarchy of subsystems systems have monitor and control subsystems systems resist entropy systems exhibit homeostatis - try to revert to a stable state systems have a purpose systems have emergent properties - the whole is more than the sum of the parts

Nature of the Systems Failures approach (Fortune & Peters) Exploits the main systems ideas Involves examining a situation and comparing it to an “ideal type” of system A system is a set of interacting parts of varying degrees of complexity: –simple systems have predictable outputs. –complex systems have outputs that are more difficult to predict.

Outline process of the Failures approach Examine the situation by identifying failures and the many details of how different aspects of the situation interact. Model the situation to illustrate those interactions. Compare the situation as analysed against templates for effective system functioning.

Systems Failure Method

Techniques for expressing the situation in systems terms Systems maps: identify boundaries of systems and the items in the environments of those systems. Transformation diagram: to discuss what systems are there for. Influence diagrams: more dynamic approach, examining where stability and instability exist (negative and positive feedback).

Techniques for comparison Formal systems model - components of an effective and learning organisational system Control paradigm - what is needed for organisational systems to be self-regulating Communication paradigm - issues surrounding effective movement and interpretation of information

Formal Systems Model (Peters and Fortune)

Brief guide to some of the systems jargon “Transformation” - process that the system exists to carry out. “Legitimates” - provides justification or reason for performing the process. “Performance monitoring” - assessing activity and identifying necessary adjustments. “Environment” - external systems which the system affects but does not control.