Showing papers on "Product design specification published in 1989"
TL;DR: A new product implementation process which is designed to reduce the risk inherent in new product introductions in consumer markets and suggests a team be created to manage the development, speeding up the tasks in each stage.
Abstract: Proposes a new product implementation process which is designed to reduce the risk inherent in new product introductions in consumer markets. Defines the stages of this process as idea generation, idea screening, conceptual development and testing, business analysis, product development, test market, and product introduction. Concludes that this process differs from previous models in suggesting a team be created to manage the development, speeding up the tasks in each stage.
113 citations
TL;DR: The new architecture for flexibly integrating the whole engineering activities is proposed, where the required engineering activities can be processed concurrently, and a practical system is explained for geometric shape design.
39 citations
01 Apr 1989
TL;DR: This paper shows how formal specification techniques can be beneficially applied in the develop ment of electronic instrumentation and argues that such specifications can be used to gain insight into software/hardware systems and to clarify the resulting design.
Abstract: This paper shows how formal specification techniques can be beneficially applied in the develop ment of electronic instrumentation. As an example of our approach we present a specification of a simple electronic instrument, written in the Z specification language. We argue that such specifications can be used to gain insight into software/hardware systems and to clarify the resulting design. A consequence is that formal specifications can assume a pivotal role in system design as non-executable prototypes and lead to a cost-effect application of formal techniq,ues in industrial settings.
24 citations
TL;DR: This analysis permits improvements to be made in the initial requirements document before its use in a formalized specification paradigm, which strengthens not only the developed specification, but also the entire software development process.
Abstract: The specification generated during the requirements specification phase acts as a cornerstone for the entire software development process. The quality of this document directly influences the overall quality of the resulting software product. The process of requirements specification uses as its input a natural language requirements document, generated by the system's users. This document serves as a guide to the actual specification process. A method is presented for the evaluation and analysis of this document. This analysis permits improvements to be made in the initial requirements document before its use in a formalized specification paradigm. By improving the quality of this document, the input to the specification process is enhanced. This enhancement strengthens not only the developed specification, but also the entire software development process.
20 citations
01 Mar 1989
TL;DR: The research group at ISI aims to improve the program development process by applying program transformation to develop implementations for specifications using the nature of the specification language, which has been designed to minimize the gap between informal conceptualization and formal specification.
Abstract: : The research group at ISI aims to improve the program development process by applying program transformation to develop implementations for specifications. Following this methodology, the development of a piece of software involves its specification in a formal specification language, and subsequent machine-assisted transformation of that specification into an implementation (conventional program). Subsequent maintenance and modification of software developed in this manner is achieved by modifying the specification, and reperforming the transformational development to derive a new implementation. Thus reuse occurs through reusing the original specification, and reusing the original transformational development of that specification. The approach is distinguished by the nature of our specification language, which has been designed to minimize the gap between informal conceptualization and formal specification. A beneficial result of this is that maintenance and modification at the specification level is relatively straightforward. Further, the techniques that are applied in transforming specifications into implementations are themselves applied repeatedly, and serve to capture our programming knowledge in a conveniently reusable manner. Consideration of an example drawn from the domain of process control illustrates these points. (Author)
19 citations
TL;DR: The proposed Product Development Life Cycle model provides for the integration and simultaneous development of the product and the strategy development processes, and provides the industrial marketing manager with a systematic process for reducing the failure rate of new industrial products in the marketplace.
18 citations
TL;DR: Even if manufacturers use the most efficient processes, they can't change lead to gold without good product design, so manufacturers and design engineers need to work together from the start.
Abstract: Even if manufacturers use the most efficient processes, they can't change lead to gold without good product design. Manufacturing managers and design engineers need to work together from the start.
17 citations
03 Jan 1989
TL;DR: A first prototype software process specification language is presented, its application is demonstrated, and software-engineering-related requirements for a supporting information base are derived.
Abstract: General requirements for software process specification languages are discussed. A first prototype software process specification language is presented, its application is demonstrated, and software-engineering-related requirements for a supporting information base are derived. Efforts aimed at implementing the information-base requirements are briefly mentioned. This work is part of the Meta Information Base project at the University of Maryland. >
16 citations
03 Jan 1989
TL;DR: The authors describe research carried out to develop a software process and product specification language that allows all the information necessary to understand, control, and improve any given software engineering process, and develop a meta-information-base schema that automatically generates an information-base structure given a Software Engineering process.
Abstract: The authors describe research carried out to: (i) develop a software process and product specification language that allows all the information necessary to understand, control, and improve any given software engineering process; (ii) develop a meta-information-base schema that automatically generates an information-base structure given a software process and product specification; and (iii) develop a mapping between the software-engineering-oriented and information-base-oriented models. Their generator approach addresses the fact that software engineering changes not only from environment to environment, but also from project to project. >
10 citations
Patent•
13 Oct 1989
TL;DR: In this article, a standard work item file for every product based on machining/assembling content of every product and an additional specification file was proposed to improve the efficiency of managing work.
Abstract: PURPOSE:To improve the efficiency of managing work by forming a product work item file for every product based on a standard work item file indicating machining/assembling content of every product, a work item file for every specification and an additional specification file. CONSTITUTION:At first, IC cards 3 fixed to products A-N moved to processes are set in a card reader/writer 5, then any one of product specification display, work item display or specification item display is selected through a keyboard and the CRT of a terminal 6. If there is an additional specification, additional confirmation data are inputted to produce a product work item file through a host computer 1. Upon finish of work of indicated items, inspection item data are inputted and the IC card 3 is set in the reader/writer 5 thus writing in specification confirmation data, work achievement data, inspection data and the like. By such arrangement, management efficiency is improved and delay of work in process is minimized.
10 citations
01 Apr 1989
01 Aug 1989
TL;DR: A high level, formal specification language, NMSL, is proposed as an aid in solving the problem of integrating increasing numbers of autonomous subnetworks and making it more difficult to determine if the network managers of the subnets will interoperate correctly.
Abstract: Large internet environments are increasing the difficulty of network management. Integrating increasing numbers of autonomous subnetworks (each with an increasing number of hosts) makes it more difficult to determine if the network managers of the subnetworks will interoperate correctly. We propose a high level, formal specification language, NMSL, as an aid in solving this problem. NMSL has two aspects of operation, a descriptive aspect and a prescriptive aspect. In its descriptive aspect, NMSL specifies abstractions of the network components and their instantiations, and verifies the consistency of such a specification. The abstractions include the data objects and processes in a network management system. These abstractions are instantiated on network elements. Network elements are grouped together in the specification of domains of administration. An extension mechanism is provided to allow for the specification of new management characteristics that the basic language cannot express. In its prescriptive aspect, NMSL generates configuration information directly from a consistent specification. This information is used to configure network management processes to make their operation consistent with their specifications. Standard management protocols (such as the emerging ISO or IETF standards) can be used to incorporate the configuration information into running management processes.
TL;DR: Ergonomists will be required to make an even greater contribution in the field of product safety, therefore, by assisting in the determination of the new statutory safety criteria.
TL;DR: The relationship between product specifications and their economic value for the manufacturer and the customer is analyzed in this paper, where an economic model is combined with a cost/benefit analysis for the prospective customer to yield an integrative model that permits coupling of the demand and supply functions under the common denominator of performance level.
Abstract: The relationship between the product specifications and its economic value for the manufacturer and the customer is analyzed. The aspects of the product dealt with are cost performance and its implications for pricing policy. An economic model for the manufacturer is combined with a cost/benefit analysis for the prospective customer to yield an integrative model that permits coupling of the demand and supply functions under the common denominator of performance level. It allows the manufacturer to weigh the performance attributes of the product by means of the customer evaluation and attenuates the tendency to overspecify the product. A numerical example based on data gathered on a citrus-fruit sorting robot is given. In this example the profitability frontier, where both parties make profits, is defined and calculated. >
03 Jan 1989
TL;DR: An example of the use of the protospec concept for requirements specification within expert systems development domain is presented and the result is compared to results for three other specification approaches.
Abstract: The protospec unifies the concepts of requirements specification and prototype into a single software engineering process. An example of the use of the protospec concept for requirements specification within expert systems development domain is presented. The requirements specification resulting from this example is evaluated from both a user and a software engineering point of view. The result is compared to results for three other specification approaches. >
TL;DR: In this article, the implications of CAD with respect to the interdependent issues of new product strategy, the product design spectrum, and product lifecycles are reviewed and discussed, and it is proposed that these issues must shape present and future CAD implementation and application policy within any manufacturing business attempting to be successful in competitive markets.
Abstract: This paper attempts to give an appraisal of how current mechanical computer-aided design (CAD) technology may be best used within the product innovation strategies that have been identified and recorded (Refs. 1–5). In this connection, the paper focuses on and reviews the implications of CAD with respect to the interdependent issues of new product strategy, the product design spectrum, and product lifecycles. On the basis of the review, it is proposed that these issues must shape present and future CAD implementation and application policy within any manufacturing business attempting to be successful in competitive markets.
21 Jun 1989
TL;DR: Design criteria and specifications for an extended computer application of a database system used in the semi-automated preparation of job specifications and bid proposals for retrofitting Energy Management Systems to existing buildings are established.
Abstract: It was necessary to establish design criteria and specifications for an extended computer application of a database system used in the semi-automated preparation of job specifications and bid proposals for retrofitting Energy Management Systems (EMS) to existing buildings. The objectives of extending this application are the inclusion of an embedded expert system, simple expandability of the existing database, and use of simulations to calculate improvements in energy use. This extended computer application allows non-technical personnel to complete routine design and job-costing tasks without requiring consultation with engineering and technical staff.
TL;DR: The line between specification and description when applied to computer architecture design is rather thin and the experience of this author indicates that a particular specification tool known as PAISLey can serve as a suitable hardware description tool.
Abstract: Operational specification is a method of documenting specifications for systems which separates the implementation details from the problem requirements details. Operational specification permits simulation of the specification enabling the specification creator to test the specification to see how well it satisfies prescribed functional requirements. The line between specification and description when applied to computer architecture design is rather thin in my opinion and the experience of this author indicates that a particular specification tool known as PAISLey (described in more detail below) can serve as a suitable hardware description tool.
TL;DR: The system can transform software functional specifications written in a graphical specification language GSPEC to executable programs automatically and the equivalence between a specification and its corresponding program can be guaranteed by the system, and the correctness of the specification can also be validated.
Abstract: This paper describes the design and implementation of an experimental software automation system (NDAUTO) By combining the transformational and procedural approaches in software automation, the system can transform software functional specifications written in a graphical specification language GSPEC to executable programs automatically The equivalence between a specification and its corresponding program can be guaranteed by the system, and the correctness of the specification can also be validated The main new points of the work lie in the design of the specification language, the transformation mechanism and the correctness validation of the specification
Proceedings Article•
01 Jan 1989
TL;DR: The system specification support environment presented in this paper, PROSPEX (Product Specification Expert), supports the RT-SA methodology and provides graphic support for drawing, but also helps the engineer in the analysis and design process itself.
Abstract: The system specification support environment presented in this paper, PROSPEX (Product Specification Expert), supports the RT-SA methodology. It not only provides graphic support for drawing, but also helps the engineer in the analysis and design process itself. PROSPEX analyses the quality and correctness of the RT-SA diagrams using knowledge-based techniques. PROSPEX also includes features for supporting design reuse. The development environment of PROSPEX was KEE expert system development shell running on a Symbolics workstation!.
TL;DR: In this article, the authors suggest that most screening methods have been developed for analyzing incremental improvements in existing businesses and as such, these methods militate against the transfer of new technologies.
Abstract: Innovative ideas will not be transferred between organizations unless they pass the screening tests managers use to choose innovations for transfer. This paper suggests that most screening methods have been developed for analyzing incremental improvements in existing businesses. As such, these methods militate against the transfer of new technologies. The paper describes screening methods in use at invention-management organizations as an alternative. These methods stress the development of business concepts for innovations, i.e., the integration of product specifications with the targeted market's characteristics, the user's capability, and convergent technologies that use and/or are used by the innovation.