Textile Research Journal; June 1981, Vol. 51 Issue: 6 p426-431, 6p
Unevenness (the variation in mass per-unit-length) of a sliver (textile strand) is considered a very important parameter for the quality control of textiles. A single index of unevenness, usually in the form of the statistical parameter CV (coefficient of variation), is hardly adequate for current quality-control requirements. A need exists, therefore, for an instrument capable of producing more detailed information quickly.The instrument described in this paper will print-out accurate data for variance- length curve-one of the important methods of unevenness analysis. A prototype model of the instrument has been built using a unit for converting the linear density into an electrical signal, a 990 prototyping system (TMS 9900 microprocessor), and an A/D converter module as the interface. The performance of the prototype instrument has been tested and the results are reported.
Squires, Stephen, Zelkowitz, Marvin, and Branstad, Martha
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p2-2, 1p
The Second Software Engineering Symposium was sponsored by ACM SIGSOFT, the IEEE Computer Society Technical Committees on Software Engineering and VLSI, and the National Bureau of Standards. Martha Branstad of the National Bureau of Standards and Marvin Zelkowitz of the University of Maryland were General Cochairmen, and Stephen L. Squires of the National Security Agency was the Program Chairman.
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p3-16, 14p
This paper describes a set of freedoms which both simplify the task of specifing systems and make the resulting specification more comprehensible. These freedoms eliminate the need, in specific areas, to consider: the mechanisims for accomplishing certain capabilities, the careful coordination and integration of separate operations, the costs of those operations, and other detailed concerns which characterize implementation.These freedoms are partitioned into the areas of efficiency, method, and data, and providing them has resulted in a novel formal specification language, Gist. The main features of this language are described in terms of the freedoms it affords. An overview of the language is then presented together with an example of its use to specify the behavior of a real system.
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p17-24, 8p
The transformational methodology for software development is adapted to perform rapid conversion of specifications into prototypes. This makes feasible testing of specifications to observe their behaviours and assuring that specifications can indeed be implemented.The approach is centered on gathering techniques to map each type of specification language construct into a reasonably efficient implementation. Instances of these constructs in an actual specification may then serve as the focal points for the conversion process.
Cohen, Donald, Swartout, William, and Balzer, Robert
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p25-32, 8p
Prototypes are built for a variety of reasons. This paper offers an alternative to the use of a prototype as a means of testing a specification (i.e. someone who "knows" what he wants compares his intuitive understanding with the behavior of the prototype on particular test cases). The alternative is symbolic execution of a formal specification, i.e. the specification is the prototype and its behavior is determined by symbolic execution rather than the traditional "concrete" execution. This is an extension of the approach to rapid prototyping based on operational specification [Balzer 82] and an alternative to testing prototypes whether manually constructed or developed mechanically from such an operational specification [Feather 82]. One advantage of this approach is that the prototype need not be built at all. Of course, the formal specification must be written, but this is often necessary anyway, especially if the specifier and implementor are different people. A more important advantage arising from symbolic execution is that a large subset of the possible behaviors can be examined at once.
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p33-34, 2p
Automatic programming as a strategy for developing rapid prototyping systems is an attractive alternative (although perhaps further in the future) to human-oriented methodologies and to executable specifications. In the case of some experimental sciences, however, it is currently possible to develop rapid prototyping systems using the automatic programming strategy. The greatest value of such systems is gained when they are oriented toward use by domain scientists, rather than software engineers. This goal has major implications for the specification language, the user interface, and the programming knowledge required by the system.
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p35-38, 4p
Rapid prototyping is especially effective when implementing interactive information management systems. With the right tools, the development process for these systems involves the generation of successive prototypes where each successor is closer to the user requirement. The final prototype becomes either the production system or a production subsystem which is integrated into the total system. The tools used to generate successive prototypes are called application generators and program generators. There are several software engineering issues addressed by these tools.
ACM SIGSOFT Software Engineering Notes (ACM Digital Library); December 1982, Vol. 7 Issue: 5 p39-44, 6p
This paper describes a software tool, called the Feature Simulator, that "executes" formally written requirements specifications for real-time systems and enables users to "interact" with the simulated product at the completion of the requirements specification phase of the software life-cycle. This tool thus produces an early and rapid prototype with which customers, designers, and managers can verify that the product meets their needs and expectations. Any deficiencies that they find can then be corrected by inexpensive changes to the product's requirements specification, rather than by more costly modifications to the final product.