Metode Pemecahan Masalah 1 Session 1: Metode Pemecahan Masalah 1 Seminar e-Bisnis Program Studi Manajemen Universitas Bina Nusantara.

Slides:



Advertisements
Similar presentations
1 Soft Systems Methodology systems thinking systems thinking systems thinking systems thinking systems thinking systems thinking.
Advertisements

Goals of INFO3315 Learn about the range of techniques to: Understand users Establish requirements Brainstorm alternatives creatively Prototyping alternative.
© Colin Potts B1-1 Organizational approaches to requirements Colin Potts Georgia Tech.
Spring ÇGIE398 - lecture 10 SSM in detail1.
Lecture 4 : Soft Systems Thinking & Practice UFCE8V-20-3 Information Systems Development SHAPE Hong Kong 2010/11.
The Design Process Engineering Graphics Dr. Stephen Crown.
Soft Systems Methodology
Introduction to Soft Systems Methodology
Soft Systems Methodology
CMSCB3001 Business Systems Analysis
Information Technology IMS5024 Information Systems Modelling Human Activity modelling.
Basic Problem Solving Tools Mark Pitman. Contents Topics/issues to be covered include: 1.Brainstorming 2.Cause and Effect diagrams 3.Pareto Charts 2.
SSM - 1 Soft Systems Methodology SSM Elena Losseva MBA 731 November 12, 2007.
Introduction to Soft Systems Methodology. The Vision SSM Models Use Cases Activity Models Dynamic Models Object Models Programs Databases Business Computing.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
淡江資管碩專一 許瀞文 陳雅玲 指導教授:戴敏育 博士 報告日期:
8 Thinking Critically, Making Decisions, Solving Problems.
Analytical methods for IS professionals ISYS3015 Qualitative research methods Data collection.
Four Dark Corners of Requirements Engineering
Designing a Product Product design is usually a problem that requires a creative Design and/or manufacturing solution.
Chapter 2 So What Is the Problem?.
socio-organizational issues and stakeholder requirements
UFCE8V-20-3 Information Systems Development 3 (SHAPE HK)
Foundation in Business Analysis
THE PRINCIPLE OF ALIGNMENT EDA 122. ALIGNMENT OUTCOMES PROCESS.
COM332 – SA3 WISDM & SSM. Web development approaches –Focused on the user interface and in particular the look and feel of a web site –Failed to address.
IE398 - lecture 10 SSM in detail
Systems Thinking, Rich Mapping and Conceptual Models.
Requirements Analysis
7-2 Decision Making: How Individuals and Groups Arrive at Decisions Copyright © 2008 by the McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
The Theoretical Basis That Allows The Design process To Work
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Chapter 11 Analysis Concepts and Principles
© Tesseract Management Systems / Managing by Design / DEFINING PROCESSES FOR THE ORGANISATION These slides are intended to support a group through.
CPSC 372 John D. McGregor Module 2 Session 1 More on requirements and the Investment Decision.
An overview of multi-criteria analysis techniques The main role of the techniques is to deal with the difficulties that human decision-makers have been.
Week 4 (2) 2008IS33 ISD - SSM 1 COMP3470 IS33 People-Centred Information Systems Development Week 4 : Lecture 2 ISD Approaches: Soft Systems Methodology.
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Requirements Management with Use Cases Module 3: Analyze the Problem Requirements Management with Use Cases Module 3: Analyze the Problem.
Chapter Thirteen – Organizational Effectiveness.  Be able to define organizational effectiveness  Understand the issues underpinning measuring organizational.
PLANNING YOUR APPROACH: THE MANAGEMENT COMPONENT OF CPS.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Engineering Design Utilizing the Engineering Design Process.
/0904 © Business & Legal Reports, Inc. BLR’s Training Presentations Creative Problem-Solving.
Information Modelling Holistic Technique. Rich Picture Root Definition Conceptual Model Cognitive Map SSM Multiview SODA Soft Methodology.
Chapter 2 The Design and Problem-Solving Process.
An Interactive Model of Research Design. 1. ID Problem Rich Picture 2. Express Problem 3. CATWOE & Root Def. Five Stakeholder Perspectives 4. Build Conceptual.
M253 Team Work in Distributed Environments Week (3) By Dr. Dina Tbaishat.
The Engineering Design Process
true potential An Introduction to the Middle Manager Programme’s CMI Qualifications.
Advanced Higher Computing Science The Project. Introduction Worth 60% of the total marks for the course Must include: An appropriate interface using input.
Soft Systems Modelling 1 David Millard | davidmillard.org.
The design cycle model and the design process.
Analisis Bisnis.
Chapter 10 Holistic Techniques.
Public Services Information Management
What is a system? A collection of components organized to accomplish a specific function or set of functions. [IEEE STD ]
Object oriented system development life cycle
THE BUSINESS ANALYSIS PROCESS MODEL
PROFESSOR ROBIN MATTHEWS KINGSTON UNIVERSITY BUSINESS SCHOOL LONDON
SOFT SYSTEMS AND THE META MODEL SEPTEMBER 2018 perspectives abridged
soft systems and the enneagram methodology
Engineering design is the process of devising a system, component, or process to meet desired needs. It is a decision-making process in which the basic.
PROFESSOR ROBIN MATTHEWS KINGSTON UNIVERSITY BUSINESS SCHOOL LONDON
Stakeholder Management
Killer Project Management Best Practices
Designing a teaching session
Presentation transcript:

Metode Pemecahan Masalah 1 Session 1: Metode Pemecahan Masalah 1 Seminar e-Bisnis Program Studi Manajemen Universitas Bina Nusantara

Problem Solving Method The problem-solving method that will be used in the following discussion consists of four basic steps: FIND OUT Look at the problem. Have you seen a similar problem before? If so, how is this problem similar? How is it different? What facts do you have? What do you know that is not stated in the problem?

Problem Solving Method (2) CHOOSE A STRATEGY How have you solved similar problems in the past? What strategies do you know? Try a strategy that seems as if it will work. If it doesn't, it may lead you to one that will.

Problem Solving Method (3) SOLVE IT Use the strategy you selected and work the problem. LOOK BACK Reread the question. Did you answer the question asked? Is your answer in the correct units? Does your answer seem reasonable?

Soft Systems Methodology Checkland's "soft systems methodology" is a response to difficulty in applying the approach of hard systems (engineering) thinking to business problems. Hard systems engineering tends to emphasise: –measurable system objectives –top down decomposition of systems into sub-sytems.

Soft Systems Methodology (2) Advanced systems engineering may show systems with unexpected and counter-intuitive behaviour and complex feedback loops between components but, systems engineering when applied to "human systems" leads to problems. –Organisation goals may be in dispute. It is wrong to assume that all organisational members accept the views and goals of top management. –Formal methods usually begin with a problem statement but - fixing the problem too early tends to hide problems. –The method itself can restrict what will be elicited - conclusions will reflect methods and starting positions.

Soft Systems Methodology (3) In principle, an SSM project is done by the people of the organisation, with a consultant-facilitator. It covers: –Problem situation –Analysis –Root definition of Relevant Systems –Conceptualisation –Comparison –Definition –Selection –Design –Implementation

CATWOE Analysis Part of the problem expression is identifying the parties involved. Checkland uses mnemonic CATWOE to describe the human activity and =situation. What is CATWOE? –Clients (those who more or less directly benefit - customers - or suffer) from the machinations of the... –Actors - the players, who perform the scenes, read and interpret the script and improvise. Who are the local and institutional actors.... who undertake the..... –Transformations.... what transformations, movements, conversions of X take place? What is the nature of the transformations? What is the content and process of transformation from ingredients to a sandwich, from mixed, varied data to information, from an idea to a performance concept or marketable product etc?

CATWOE Analysis (2) Weltanschauung or world-view.... what is going on in the wider world that is influencing and shaping the system and need for the system to adapt? Owners - the activity is ultimately "controlled" or paid for by by the owners and it occurs within an Environment - the political, legal, economic, social, demographic, technological, ethical, competitive, natural environment –NB: some categories (actor, client, owner, environment) may overlap. CATWOE analysis helps in working out a "root definition" and expressing the domain of the problem. Avoid early conclusions about who and what is "important".

Transformation Example Checkland offers the case of an aircraft landing system. The transformation involves getting the incoming aircraft from a height and a distance safely on the runway. The actors woul be the pilots (human and auto), the clients would be the passengers and crew, the owners the owners of the airline, and the environment: the air traffic controllers, air lanes, traffic conditions and geographic features. The weltanschauung may involve competition between international airports, the airport-housing environment, high concern for safety and high technology operations.

Rich Picture Diagrams Checkland tends to describe his systems with diagrams or "rich pictures" - a diagram "without rules". Rich pictures have some distinguishing features. They show –the people involved –their stated purposes –their desires and fears (usually in think bubbles). –more environmental detail than most diagrams (human activities, like processes, cross organisational boundaries). –how interests agree or conflict. Rich pictures are cartoons - they can be funny, sad, political... and all at once.

The Process View Using CATWOE in an analysis exercise and drawing a rich picture focuses attention on a process view. SSM targets existing systems and Checkland encourages investigation and definition of existing organisation features and how these interact with the process. Consider too the "climate" of the organisation (efficient, sloppy, democratic, sulky, joyous...?). After the problem examination and definition stage SSM participants "should" be able to see the organisation differently, more fully and to different levels and sub- problems of problems. They will have "facts" and viewpoints at varying levels of detail - many "problem" statements, some major and some trivial. (Which are which?)

Root Definition The analysts now need to define what it is all about. What is the arena of concern - lets synthesis the "root definition" - a well- defined statement about the area of activity and its components. This is for internal use creative use not public dissemination. It may represent a minimum that can be agreed in terms of a description of the real activity domain. People should be able to see what they are agreeing to and what has been left out. Examples? To be completed. A root definition defines both what is agreed and what is still unresolved and other associated things. A root definition for which there is a consensus - at a point in time..... is an important outcome of the SSM process.

Conceptual Modelling Having arrived at a root definition and a CATWOE rich picture - the analysts can now turn attention to their imagined, "ideal" system. Creativity and solution generation time is here.... exploring –the wild and fanciful –defining the musts and the desirables –evaluating and choosing –criteria for choosing - decisions - if a "best" model is found - criteria maybe implicit.... but be clear about criteria!