Whatever happened to software engineering?

The term "software engineering" originally appeared as a (some would say, the) solution to the software crisis; the term that has been used to include all the problems, real or perceived, in the use of computers in society. In the last fifty years, computers have been applied to an increasing number and type of activities, in large part, due to the exponential increase in speed, capacity, and exponential decrease in cost. Nevertheless, there are continuing references to the software crisis, an indication that software engineering had not "solved" it. The term computer-aided software engineering (CASE) appeared about ten years ago to signal a major advance. Today, CASE is used much less frequently, particularly by the vendors that market CASE tools or by the individuals that develop software. This paper examines the proposition that software development is engineering, whether it is becoming less, rather than more, relevant to the practical application of computing power, identifies and analyzes some of the forces at work, and discuss some implications for the profession

Software-Spezifikation durch halbformale, anschauliche Modelle

Der Beitrag erörtert die Frage, welche Ansätze zur Spezifikation grundsätzlich in Frage kommen, und begründet, warum in der industriellen Praxis das Prinzip der halbformalen Spezifikation auf der Basis anschaulicher Modelle vorteilhaft ist. Die Beispiele und die am Schluss wiedergegebenen Erfahrungen stammen aus unserer Arbeit mit dem Spezifikationssystem SPADES, das auf dem Prinzip der halbformalen Beschreibung beruht

ESPRESO-W, ein Werkzeug für die Spezifikation von Prozeßrechner-Software

ESPRESO (System zur Darstellung der Sezifikation von Prozeßrechner-Software) ist ein rechnerunterstütztes Spezifikationssystem, das spezielle Anforderungen der Spezifikation von Prozeßrechner-Software berücksichtigt. Die Komponenten von ESPRESO sind eine formale Sprache ESPRESO-S und ein Programmsystem ESPRESO-W. Im vorliegenden Beitrag werden die wesentlichen Aspekte von ESPRESO-S kurz zusammengefaßt. Danach werden Konzeption und Aufbau von ESPRESO-W und Probleme seiner Implementierung ausführlich dargestellt

Developing manufacturing control software: A survey and critique

The complexity and diversity of manufacturing software and the need to adapt this software to the frequent changes in the production requirements necessitate the use of a systematic approach to developing this software. The software life-cycle model (Royce, 1970) that consists of specifying the requirements of a software system, designing, implementing, testing, and evolving this software can be followed when developing large portions of manufacturing software. However, the presence of hardware devices in these systems and the high costs of acquiring and operating hardware devices further complicate the manufacturing software development process and require that the functionality of this software be extended to incorporate simulation and prototyping.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/45542/1/10696_2005_Article_BF01328739.pd

Information processing systems analysis and design. Progress report, January 1, 1975--September 30, 1975

Non