Scribd
Upload
70 views7 pages

Hard Versus Soft Systems Methodology: David Cairns CSC9T4

The document discusses the differences between hard and soft systems methodologies. Hard systems approaches view problems as having an objective reality with well-defined technical factors to solve. They use rigid techniques to provide unambiguous solutions. Soft systems approaches see problems as "messy" with stakeholders having different interpretations. They use loose frameworks and focus on improving understanding rather than definitive solutions.

Uploaded by

mostafahhh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
70 views7 pages

Hard Versus Soft Systems Methodology: David Cairns CSC9T4

The document discusses the differences between hard and soft systems methodologies. Hard systems approaches view problems as having an objective reality with well-defined technical factors to solve. They use rigid techniques to provide unambiguous solutions. Soft systems approaches see problems as "messy" with stakeholders having different interpretations. They use loose frameworks and focus on improving understanding rather than definitive solutions.

Uploaded by

mostafahhh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Hard versus Soft Systems Methodology

David Cairns CSC9T4

Systems approaches So we know what the systems approach is now. But, theres different ways of viewing a system: Soft systems approach Hard systems approach Two ends of a scale, a bit grey in the middle

CSC9T4 - M anaging Information

Soft Systems Approach Engineering approach can be inappropriate for soft problems (with fuzzy requirements). Soft systems approaches (Soft Systems Methodology, Soft OR) assume: organisational problems are messy or poorly dened stakeholders interpret problems differently (no objective reality) human factors important creative, intuitive approach to problem-solving outcomes are learning, better understanding, rather than a solution
CSC9T4 - M anaging Information

Hard Systems Approach Hard systems approaches (systems analysis (structured methods), systems engineering, operations research) assume: Objective reality of systems in the world Well-dened problem to be solved Technical factors foremost Scientic approach to problem-solving An ideal solution More traditional way of viewing systems in Computing Science

CSC9T4 - M anaging Information

Whats the difference in hard and soft systems methodologies? HARD systems - rigid techniques and procedures to provide unambiguous solutions to well-dened data and processing problems problems, focused on computer implementations SOFT systems - a loose framework of tools to be used at the discretion of the analyst, focused on improvements to organisational problems

CSC9T4 - M anaging Information

Hard Systems Approach - Example Design a virtual resource management system where resources are held in staff ofces but are made available via a web based interface. Resources will be booked out via the on-line management system which will also send reminders when items are due for return. Identify any obvious requirements via nouns & verbs Web Based Booking System Users Resources
CSC9T4 - M anaging Information

Example
Expand Requirements Web Based
Web Server - Platform? Web Client - Browser / Applet Flow control Event manager Data Base Staff Students Administrators

Booking System

Users

Resources
Books Journals Rooms? CDs?
CSC9T4 - M anaging Information

Analysis Once we have a proper set of requirements, the next step is the analysis of the problem. This involves understanding the scope of the problem Identifying the parts in the requirements that will be part of the eventual solution
For example, is the web server component part of our solution?

Connect them together in an appropriate manner

CSC9T4 - M anaging Information

Design Analysis of the problem indicates what the major components in the system are, it will not tell us how these components work. Design involves Identication of major component boundaries Decomposition of the major components into smaller semi-independent sub-systems Design of the interfaces between these major components & sub-systems

CSC9T4 - M anaging Information

Design Design involves (continued) Identication of new components necessary to bridge the gap between objects in the problem domain and the solution domain. Flow of control within the system Flow of data within the system

CSC9T4 - M anaging Information

10

Implementation & Testing Implementation - The translation of the Design into Source Code For each identied component and interface in the design phase, create the source code that will implement it Integration of code components such that they perform as one system Testing Check that each element / sub-system / component does what it is required to do by the design Check system meets the requirements specication Check system meets the clients expectations Check system meets the users expectations
CSC9T4 - M anaging Information

11

Design - Example
User Resource

Staff Students Administrator

Book Journal CD

Booking System

Controller

Event Manager Database

CSC9T4 - M anaging Information

12

Hard vs. Soft Systems : Review Hard Systems Problem has a definite solution Problem has a number of achievable goals Soft Systems There are many problems to be solved Goals cannot be measured

They answer the how Emphasis is placed on questions what as well as how Has a deterministic complexity Has a unpredictable, nondeterministic, non-definable complexity Likely to have defined Less easily dealt with parameters for failure
CSC9T4 - M anaging Information

13

You might also like