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

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 "This report summarizes the activities of the M. I. T. Computer-Aided Design (CAD) Project from 1 December 1959 through …" by Douglas T. Ross?
Douglas T. Ross photo
Douglas T. Ross 27
American computer scientist 1929–2007

Related quotes

“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 (1929–2007) American computer scientist

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

Ed Yourdon photo

“Designed as a companion volume to the acclaimed Object-Oriented Analysis, this book focuses on the middle part of the software lifecycle: the activity of design. It shows readers how to apply object-oriented design, and how to tailor and expand the method to suit specific organization and project needs. Readers will explore the major issues in OOD; the role of OOD in the systems lifecycle; how to use graphical notation; strategies for creating design; and hints for evaluating the efficiency of a design created with OOD. For software engineers and other users undertaking real-world systems development projects and designing overall software architecture for systems will find this reference approach to improving systems design indispensable.”

Ed Yourdon (1944–2016) American software engineer and pioneer in the software engineering methodology

Abstract.
Object-oriented design (1991)

“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

Fred Brooks photo

“A little retrospection shows that although many fine, useful software systems have been designed by committees and built as part of multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers.”

Fred Brooks No Silver Bullet

Page 202.
No Silver Bullet (1986)

“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 (1929–2007) American computer scientist

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

“Advances in hardware and network technologies have paved the way for the development of increasingly pervasive software-based systems of systems that collaborate to provide essential services to society. Software in these systems is often required to (1) operate in distributed and embedded computing environments consisting of diverse devices (personal computers, specialized sensors and actuators), (2) communicate using a variety of interaction paradigms (e. g., SOAP messaging, media streaming), (3) dynamically adapt to changes in operating environments, and (4) behave in a dependable manner. Despite significant advances in programming languages and supporting integrated development environments (IDEs), developing these complex software systems using current code-centric technologies requires herculean effort.”

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37: Introduction

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

August-Wilhelm Scheer photo

“Business information systems can be either designed as custom applications or purchased as off-the-shelf standard solutions. The development of custom applications is generally expensive and is often plagued by uncertainties, such as the selection of appropriate development tools, the duration of the development cycle, or the difficulties involved in assessing costs. Thus, empirical surveys have shown that between half to two-thirds of information systems projects fail. The current tendency to shift from individual development to standardized, prepackaged software solutions is therefore not surprising.”

August-Wilhelm Scheer (1941) German business theorist

August-Wilhelm Scheer, and Frank Habermann. " Enterprise resource planning: making ERP a success http://ecis.seattleu.edu/courses/ecis464spring04/Articles/Making%20ERP%20a%20Success.pdf." Communications of the ACM 43.4 (2000): 57-61.

“The growing complexity of software is the motivation behind work on industrializing software development. In particular, current research in the area of model driven engineering (MDE) is primarily concerned with reducing the gap between problem and software implementation domains through the use of technologies that support systematic transformation of problem-level abstractions to software implementations. The complexity of bridging the gap is tackled through the use of models that describe complex systems at multiple levels of abstraction and from a variety of perspectives, and through automated support for transforming and analyzing models. In the MDE vision of software development, models are the primary artifacts of development and developers rely on computer-based technologies to transform models to running systems.”

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37

“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