“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

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

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 "Advances in hardware and network technologies have paved the way for the development of increasingly pervasive software…" by Bernhard Rumpe?
Bernhard Rumpe photo
Bernhard Rumpe 8
German computer scientist 1967

Related quotes

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

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.

“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

“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

“Creating a modeling language that is also an executable language has long been a goal of the software community. Many years ago, in 1968 to be exact, while working with software components to successfully develop a telecommunications system, we created a modeling language that was the forerunner to UML. To model components we used sequence diagrams, collaboration diagrams, and state transition diagrams (a combination of state charts and activity diagrams). Our modeling language then seamlessly translated the component models into code. Each code component was in its turn compiled into an executable component that was deployed in our computer system. The computer system was a component management system—thus we had "components all the way down."”

Stephen J. Mellor (1952) British computer scientist

Source: Executable Uml: A Foundation for Model-Driven Architecture, 2002, p. xxiii: Foreword.

“The hardware of a computer is useless without the right software. Similarly, in an organization the hardware (strategy and structure) is inert without the software (beliefs and behaviors).”

Larry Bossidy (1935) American businessman

Source: Execution: The Discipline of Getting Things Done

“The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

“Formulating and structuring a system provide methods for relating (1) what the system consists of in the mind of the persons or group desiring it; (2)what it means in terms of the persons or group designing and building it; and (3) in terms of the persons or groups operating, using and servicing it. They provide a set of "reasonable" parts and methods of relating them so that the many persons working on the system can understand the whole in sufficient detail for their purposes, and their particular parts in explicit detail so that they may contribute their best efforts to the extent required. A further purpose of system formulation is to recognize the magnitude of the job, including the possible pitfalls.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), Systems Engineering Methods (1967), p. 70; Rest of first paragraph of Ch.3

Zygmunt Vetulani photo

“The fact that a computer player wins a game of chess or bridge with a human does not necessarily mean that the device is intelligent. The victory results from the fact that in the final analysis the device has been applied appropriate algorithms developed by man, e. g. using the properties of artificial neural networks. It is not the device that wins with a man, e. g. a chess player, but a man – the designer of the device. It is simply the rivalry of one intellect with another through the medium of computer science.”

Zygmunt Vetulani (1950) Polish mathematician

Tumiłowicz, Bronisław (February 2018): Zrób sobie mózg https://www.tygodnikprzeglad.pl/zrob-sobie-mozg/. Przegląd (6/2018): pp. 58–59.

Ward Cunningham photo

“When I was at Tek, I was frustrated that computer hardware was being improved faster than computer software. I wanted to invent some software that was completely different, that would grow and change as it was used. That’s how wiki came about.”

Ward Cunningham (1949) American computer programmer who developed the first wiki

"Startup mines for riches in collaboration software" in The Portland Tribune (7 March 2008) http://www.portlandtribune.com/rethinking/story.php?story_id=120430910578805900

Grady Booch photo

“The object-oriented paradigm is useful when building software systems where there is a hierarchy defined as a ranking or ordering of abstractions.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 54

Related topics