Douglas T. Ross: Quotes about problems

Douglas T. Ross was American computer scientist. Explore interesting quotes on problem.
Douglas T. Ross: 54   quotes 0   likes

“The objective of the Computer-Aided Design Project is to evolve a machine systems which will permit the human designer and the computer to work together on creative design problems.”

Douglas T. Ross

Source: Computer-Aided Design: A Statement of Objectives (1960), p. iii: Abstract.

Problem

“I introduced what I called "outside-in problem solving," which nowadays is called "top-clown." But I prefer outside-in because outside-in allows you to have many different viewpoints instead of a single top that you stupidly try to get to the bottom of, and things of that sort. came out of that.”

Douglas T. Ross

Source: Retrospectives : The Early Years in Computer Graphics at at MIT, Lincoln Lab and Harvard (1989), p. 25.

Problem

“A general theme for what I'm trying to convey and what actually drove me and my very industrious and creative project members over all these years, is… that there is much more to it than pictures. It has to be a picture language. There has to be meaning there, and the meaning is useful. You're trying to solve problems. So it really comes down to man machine problem solving. Better means of communication and expression is what always has driven our work.”

Douglas T. Ross

Source: Retrospectives : The Early Years in Computer Graphics at at MIT, Lincoln Lab and Harvard (1989), p. 26.

Communication , Problem

“The artificial intelligence people, the artificial intelligencia,… kept choosing little games to play, and little things that they could master, right? But my whole philosophy has always been give me a really tough problem that's just beyond the state-of-the-art, and give me a whole bunch of users beating on me to get it done. In other words, the real core of what being an engineer is.”

Douglas T. Ross

Source: An Interview with Douglas T. Ross (1989), p. 24-25.

People , Art , Game , Intelligence

“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".

Problem

“The first paper I ever wrote was "Gestalt Programming" and that was in 1955. The whole idea there was to replace the laborious writing out of detailed programs and all those steps by having analyzed a problem area well enough so that you had what I later came to call a "systematized solution." Then you could compose different problems of this class by just plugging together pieces of program, and they would in turn be controlled by a pushbutton language. The user would make a number of discreet selections. It's just like nowadays it's done with menus, and when you had indicated all the pieces that you wanted to put together--by these mnemonic names and words for things associated with buttons, switches, with one meaning "period," essentially, for that sentence, you see--all these things would be brought together and that would be the man/machine, manual-intervention mode of problem-solving. I took over the term from studying Gestalt psychology, meaning that everything was brought together at once, as a unit, instead of this laborious step-by-step build-up.”

Douglas T. Ross

Source: An Interview with Douglas T. Ross (1989), p. 4.

Idea , Problem , Study

“This report summarizes the activities of the M. I. T. Computer-Aided Design (CAD) Project from 1 December 1959 through 3 May 1967 in the development of a generalized 'system of software systems' for generating specialized problem-solving systems using high-level language techniques and advanced computer graphics. Known as the AED Approach (for Automated Engineering Design) the Project results are applicable not only to mechanical design, as an extension of earlier development of the APT System for numerical control, but to arbitrary scientific, engineering, management, and production systems as well.”

Douglas T. Ross

D.T. Ross & John Erwin Ward (1968). Investigations in computer-aided design for numerically controlled production http://dspace.mit.edu/bitstream/handle/1721.1/755/FR-0351-19563962.pdf?sequence=1. Electronic Systems Laboratory, Electrical Engineering Dept., Massachusetts Institute of Technology. p. iii Abstract.

Problem

“There is a rigorous science, just waiting to be recognized and developed, which encompasses the whole of 'the software problem,' as defined, including the hardware, software, languages, devices, logic, data, knowledge, users, users, and effectiveness, etc. for end-users, providers, enablers, commissioners, and sponsors, alike.”

Douglas T. Ross

D.T. Ross (1989) "Appendix B: Understanding: The Key to Software" in: Computer Science and Telecommunications Board, National Research Council Scaling Up: A Research Agenda for Software Engineering. p. 66 (cited on p. 3).

Knowledge , Problem , Science , Waiting

“From the computer application point of view the primary problem [of Computer-Aided Design] is not how to solve problems, but how to state them.”

Douglas T. Ross

Source: Computer-Aided Design: A Statement of Objectives (1960), p. iii; Abstract.

Problem