Modeling the Structure and Complexity of Engineering Routine Design Problems

This paper proposes a model to structure routine design problems as well as a model of its design complexity. The idea is that having a proper model of the structure of such problems enables understanding its complexity, and likewise, a proper understanding of its complexity enables the development of systematic approaches to solve them. The end goal is to develop computer systems capable of taking over routine design tasks based on generic and systematic solving approaches. It is proposed to structure routine design in three main states: problem class, problem instance, and problem solution. Design complexity is related to the degree of uncertainty in knowing how to move a design problem from one state to another. Axiomatic Design Theory is used as reference for understanding complexity in routine design

A Historical Perspective on Runtime Assertion Checking in Software Development

This report presents initial results in the area of software testing and analysis produced as part of the Software Engineering Impact Project. The report describes the historical development of runtime assertion checking, including a description of the origins of and significant features associated with assertion checking mechanisms, and initial findings about current industrial use. A future report will provide a more comprehensive assessment of development practice, for which we invite readers of this report to contribute information

Aircraft systems architecting: a functional-logical domain perspective

Presented is a novel framework for early systems architecture design. The framework defines data structures and algorithms that enable the systems architect to operate interactively and simultaneously in both the functional and logical domains. A prototype software tool, called AirCADia Architect, was implemented, which allowed the framework to be evaluated by practicing aircraft systems architects. The evaluation confirmed that, on the whole, the approach enables the architects to effectively express their creative ideas when synthesizing new architectures while still retaining control over the process

A New Combined Framework for the Cellular Manufacturing Systems Design

Cellular Manufacturing (CM) system has been recognized as an efficient and effective way to improve productivity in a factory. In recent years, there have been continuous research efforts to study different facet of CM system. The literature does not contain much published research on CM design which includes all design aspects. In this paper we provide a framework for the complete CM system design. It combines Axiomatic Design (AD) and Experimental Design (ED) to generate several feasible and potentially profitable designs. The AD approach is used as the basis for establishing a systematic CM systems design structure. ED has been a very useful tool to design and analyze complicated industrial design problems. AD helps secure valid input-factors to the ED. An element of the proposed framework is desmontrate through a numerical example for cell formation with alternative process.Cellular manufacturing; Design methodology Axiomatic Design; Experimental Design.

Fifty years of Hoare's Logic

We present a history of Hoare's logic.Comment: 79 pages. To appear in Formal Aspects of Computin

References to past designs

Designing by adaptation is almost invariably a dominantambiguity feature of designing, and references to past designs are ubiquitous in design discourse. Object references serve as indices into designers' stocks of design concepts, in which memories for concrete embodiments and exemplars are tightly bound to solution principles. Thinking and talking by reference to past designs serves as a way to reduce the overwhelming complexity of complex design tasks by enabling designers to use parsimonious mental representations to which details can be added as needed. However object references can be ambiguous, and import more of the past design than is intended or may be desirable

Design for validation: An approach to systems validation

Every complex system built is validated in some manner. Computer validation begins with review of the system design. As systems became too complicated for one person to review, validation began to rely on the application of adhoc methods by many individuals. As the cost of the changes mounted and the expense of failure increased, more organized procedures became essential. Attempts at devising and carrying out those procedures showed that validation is indeed a difficult technical problem. The successful transformation of the validation process into a systematic series of formally sound, integrated steps is necessary if the liability inherent in the future digita-system-based avionic and space systems is to be minimized. A suggested framework and timetable for the transformtion are presented. Basic working definitions of two pivotal ideas (validation and system life-cyle) are provided and show how the two concepts interact. Many examples are given of past and present validation activities by NASA and others. A conceptual framework is presented for the validation process. Finally, important areas are listed for ongoing development of the validation process at NASA Langley Research Center

Specifying Reusable Components

Reusable software components need expressive specifications. This paper outlines a rigorous foundation to model-based contracts, a method to equip classes with strong contracts that support accurate design, implementation, and formal verification of reusable components. Model-based contracts conservatively extend the classic Design by Contract with a notion of model, which underpins the precise definitions of such concepts as abstract equivalence and specification completeness. Experiments applying model-based contracts to libraries of data structures suggest that the method enables accurate specification of practical software

On the engineering of crucial software

The various aspects of the conventional software development cycle are examined. This cycle was the basis of the augmented approach contained in the original grant proposal. This cycle was found inadequate for crucial software development, and the justification for this opinion is presented. Several possible enhancements to the conventional software cycle are discussed. Software fault tolerance, a possible enhancement of major importance, is discussed separately. Formal verification using mathematical proof is considered. Automatic programming is a radical alternative to the conventional cycle and is discussed. Recommendations for a comprehensive approach are presented, and various experiments which could be conducted in AIRLAB are described

A QFD framework for quality, innovation and high-tech product development dynamics

The customer mostly chooses a product on the base of its quality, which therefore arises as the main cause of its commercial success. In a nearly axiomatic drawing, it follows that the effect of innovation is the improvement of quality, which itself becomes the aim of innovation. Even though the previous statement relates quality and innovation, it still does not explain their dynamics. To stress them, the ‘quality' concept must be analyzed in more detail. In fact, in addition to the ‘perceived quality', the quality ensured through `design, manufacturing and marketing' combined domains should be dealt with. This paper enhances this issue taking advantage of principles and models made available by control theory schemes coupled with quality function development (QFD) and best practice software modeling based on unified modeling language (UML