“The assertion that a problem unstated is a problem unsolved seem to have escaped many builders… All too often, design and implementation begins before the real needs and system functions are fully known. The results are skyrocketing costs, missed scheduled, waste and duplication, disgruntled users and endless series of patches and repairs euphemistically called "systems maintenance"”

— Douglas T. Ross

D.T. Ross and K.E. Schoman (1977) "Structured analysis for requirements definition" IEEE Transactions on Software Engineering. Vol 3. (1) p. 6-15; as cited in: G. Agyekum-Mensah et al. (2012) "Adaption of structured analysis design techniques methodology for construction project planning".

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 "The assertion that a problem unstated is a problem unsolved seem to have escaped many builders… All too often, design a…" by Douglas T. Ross?

Douglas T. Ross 27

American computer scientist 1929–2007

Related quotes

“If solutions could be offered within the existing system, there would be no need to design. Thus designers have to transcend the existing system. Their task is to create a different system or devise a new one. That is why designers say they can truly define the problem only in light of the solution. The solution informs them as to what the real problem is.”

Béla H. Bánáthy (1919–2003) Hungarian linguist and systems scientist

Source: Systems Design of Education (1991), p. 20

“In computer design three levels can be distinguished: architecture, implementation and realisation; for the ﬁrst of them, the following working deﬁnition is given: The architecture of a system can be defined as the functional appearance of the system to the user, its phenomenology.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Although the term architecture was introduced only ten years ago in computer technology (Buchholz), the concept of architecture is as old as the use of mechanism by man. When a child is taught to look at a clock, it is taught the architecture of the clock. It is told to observe the position of the short and the long hand and to relate these to the hours and the minutes. Once it can distinguish the architecture from the visual appearance, it can tell time as easily from a wrist watch as from the clock on the church tower.
The inner structure of a system is not considered by the architecture: we do not need to know what makes the clock tick, to know what time it is. This inner structure, considered from a logical point of view, will be called the implementation, and its physical embodiment the realisation.
Source: Computer architecture (1972), p. 154

“The design of a digital system starts with the specification of the architecture of the system and continues with its implementation and its subsequent realisation… the purpose of architecture is to provide a function. Once that function is established, the purpose of implementation is to give a proper cost-performance and the purpose of realisation is to build and maintain the appropriate logical organisation.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Source: Specification of Digital Systems (1978), p. 29

“We have also come to realize that no problem ever exists in complete isolation. Every problem interacts with other problems and is therefore part of a set of interrelated problems, a system of problems I choose to call such a system a mess … Furthermore solutions to most problems produce other problems… a financial problem, a maintenance problem, and conflict among family members for its use.”

Russell L. Ackoff (1919–2009) Scientist

Source: 1970s, Redesigning the future, 1974, p. 21 as cited in: Frederick M. Zimmerman (2011) From Riches to Rags at a Time of Prosperity, p. 12.

“God made Homo sapiens a problem-solving creature. The trouble is that He gave us too many resources: too many languages, too many phases of life, too many levels of complexity, too many ways to solve problems, too many contexts in which to solve them, and too many values to balance.
First came the law, accounting, and history which looks backward in time for their values and decision-making criteria, but their paradigm (casuistry) cannot look forward to predict future consequences. Casuistry is overly rigid and does not account for statistical phenomena. To look forward man used two thousand years to evolve scientific method - which can predict the future when it discovers the laws of nature. In parallel, man evolved engineering, and later, systems engineering, which also anticipates future conditions. It took man to the moon, but it often did, and does, a poor job of understanding social systems, and also often ignores the secondary effects of its artifacts on the environment.
Environmental impact analysis was promoted by governments to patch over the weakness of engineering - with modest success - and it does not ignore history; but by not integrating with system design, it is also an incomplete philosophy. System design and architecture, or simply design, like science and engineering is forward-looking, and provides man with comforts and conveniences - if someone will tell them what problems to solve, and which requirements to meet. It rarely collects wisdom from the backward-looking methodologies, often overlooks ordinary operating problems in designing its artifacts, whether autos or buildings, and often ignores the principles of good teamwork.”

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

Source: Metasystems Methodology, (1989), p.xi cited in Philip McShane (2004) Cantower VII http://www.philipmcshane.ca/cantower7.pdf

“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

“The architecture of a system can be defined as the functional appearance of the system to the user.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Blaauw (1972) cited in: Gerritt A Blaauw (1976) Digital system implementation. p. 6

“A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system.”

John Gall (1925–2014) American physician

Source: General systemantics, an essay on how systems work, and especially how they fail..., 1975, p. 65, cited in: Grady Booch (1991) Object oriented design with applications. p. 11

“A real scientist solves problems, not wails that they are unsolvable.”

Anne McCaffrey book Acorna: The Unicorn Girl

Source: Acorna: The Unicorn Girl

“The synthetic mode of thought, when applied to systems problems, is called the systems approach. In this approach a problem is not solved by taking it apart but by viewing it as a part of a larger problem.”

Russell L. Ackoff (1919–2009) Scientist

Source: 1970s, Redesigning the future, 1974, p. 14.

Help us to complete the source, original and additional information

Douglas T. Ross 27

Related quotes

Related topics