“Hard systems viewpoints are basically those held by designers and engineers who are trying to create systems to meet an understood need in an effective and economic manner. Those in the soft camp caricature the approach as head-down, concerned with optimization, obsessed with quantitative metrics and highly pragmatic. So much so, in fact, that the term system thinking has been purloined by the soft camp as though they alone thought! The soft camp use the term engineer’s philosophy, not too endearingly, to describe the hard approach, in which the requirement is stated by a customer and the engineer satisfies the requirement without question.”

—  Derek Hitchins

Source: Putting systems to work (1992), p. 6; as cited in: Stuart Anderson (2006) "Heterogeneous Modelling of Evolution for Socio-technical Systems"

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Hard systems viewpoints are basically those held by designers and engineers who are trying to create systems to meet an…" by Derek Hitchins?
Derek Hitchins photo
Derek Hitchins 14
British systems engineer 1935

Related quotes

“An example from soft systems thinking is Checkland's appreciation of soft systems methodology. He wants to introduce hard systems approaches to deal with hard problems only after and through a soft systems analysis.”

Robert L. Flood (1959) British organizational scientist

Robert L. Flood (1993) Dealing with Complexity: An Introduction to the Theory and … - Pagina 127.

“Soft systems viewpoints are those held by behavioural, management, social anthropology, social psychology and other science students concerned with observing the living world, and in particular the human world. Human activity systems (HASs) are messy, in that they do not exhibit a clear need or purpose - if they can be said to exhibit purpose at all. Indeed, so complex is the real world of people that the idea of driving towards optimal solutions may be a non-starter - perhaps we should see if we can simply understand and concern ourselves with improving the situation.”

Derek Hitchins (1935) British systems engineer

Source: Putting systems to work (1992), p. 7; as cited in: Stuart Anderson (2006)

“Models are used essentially for evaluation and prediction purposes as well as for the analysis and study of the different parts of the system so that the systems engineer or designer may arrive at sound engineering decisions regarding the system design.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 113; As cited in: Alberto Ortiz (1992, p. 12-13)

“System engineering is the art and science of creating effective systems, using whole system, whole life principles.”

Derek Hitchins (1935) British systems engineer

Derek Hitchins (1995) cited in: Herbert Negele (2000) Systems engineering--a key to competitive advantage for all industries. p,166

“In a world in which training and functions of individuals and groups are growing more and more specialized the number of ways to accomplish any particular result increasing. Different design, different facilities, different equipment, different methods, and different organizational means are available to meet the needs of man. It is highly desirable that we have trained persons look at these varied possibilities to compare their effectiveness, and to point the way to sound engineering decisions. Systems Engineering Methods is directed towards the development of a broad systems engineering approach to help such people improve their decision-making capability. Although the emphasis is on engineering, the systems approach can also has validity for many other areas in which emphasis may be social, economic, or political.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), Systems Engineering Methods (1967), p. vii

“Software engineering concerns methods and techniques to develop large software systems. The engineering metaphor is used to emphasize a systematic approach to develop systems that satisfy organizational requirements and constraints.”

Hans van Vliet (1949) Dutch computer scientist

Source: Software Engineering: Principles and Practice, 2007, p. 2

A. Wayne Wymore photo

“[In the year 1957] I have just returned from an exciting meeting of the American Society for Engineering Education where I heard a paper on the new discipline of systems engineering. It is no longer sufficient for engineers merely to design boxes such as computers with the expectation that they would become components of larger, more complex systems. That is wasteful because frequently the box component is a bad fit in the system and has to be redesigned or worse, can lead to system failure. We must learn how to design large-scale, complex systems from the top down so that the specification for each component is derivable from the requirements for the overall system. We must also take a much larger view of systems. We must design the man-machine interfaces and even the system-society interfaces. Systems engineers must be trained for the design of large-scale, complex, man-machine-social systems.”

A. Wayne Wymore (1927–2011) American mathematician

Systems Movement: Autobiographical Retrospectives (2004)

“Within the past ten years there have appeared with increasing frequency books, articles, conferences, and monograms dealing with system engineering, system analysis, system design, the systems approach, the design of systems, system theory, and problems of systems engineering. The number of publications and the stature of their authors does not allow the dismissal of the subject as a passing fad. The breadth of engineering activity involved in even a cursory examination of recent publications is of interest… It is therefore obvious that whatever Systems Engineering may or may not be, it is non-sectarian and encompasses activities that are of concern in all phases of engineering. On the other hand undergraduate college offerings akin to Systems Engineering are rather limited and even graduate programs are not extensive.”

Allen B. Rosenstein (1920–2018) American systems engineers

Source: Systems engineering and Modern Engineering Design (1965), p. 1.

“Systems engineering is most effectively conceived of as a process that starts with the detection of a problem and continues through problem definition, planning and designing of a system, manufacturing or other implementing section, its use, and finally on to its obsolescence. Further, Systems engineering is not a matter of tools alone; It is a careful coordination of process, tools and people.”

Arthur D. Hall (1925–2006) American electrical engineer

A.D. Hall (1965) "Systems Engineering from an Engineering Viewpoint" In: Systems Science and Cybernetics. Vol.1 Issue.1

“A new concept and a new method were needed. The concept from the engineering standpoint is the evolution of the engineering scientist, i. e., the scientific generalist who maintains a broad outlook. The method is that of the team approach. On large-scale-system problems, teams of scientists and engineers, generalists as well as specialists, exert their joint efforts to find a solution and physically realize it.
We are led to the concept of the system-design team, a small group of engineers or scientists, to lead a large project and organize the system effort. Such men have been variously called engineering scientists, system engineers, system analysts, or large-scale-system designers. The technique has been variously called the systems approach or the team development method. It is toward this man and his teammates that these discussions are directed. With the realization that not enough can be learned in all the required fields to make him a specialist, enough is introduced to make him aware of the language and problems of the specialist. This generalist is a new quantity in the engineering world, and his education must be begun.”

Robert E. Machol (1917–1998) American systems engineer

Source: System Engineering (1957), p. 8

Related topics