A Framework for the Construction and Tailoring of Engineering Development Process Models

Author(s):  
Holger Timinger ◽  
Markus Schmidtner ◽  
Finn Reiche
Author(s):  
Robert P. Smith

Abstract This paper describes a model of how reordering tasks in the engineering design and development process affects resource usage in a risky environment. All development projects are risky; their outcome and level of success is unpredictable. Many projects are canceled at some time during the development process, or never produce a working product or produce a product that fails in the marketplace. Doing engineering development is expensive; it requires high-cost labor as well as other potentially expensive resources. To some extent the magnitude of the risk is estimable; it is possible to predict now much resources (time, labor or other costs) any particular development task will consume as well as some estimate of whether or not an insurmountable technical problem is likely to be discovered. Also, development tasks are not independent; there are constraints on their ordering due to needed technical knowledge. The model presented in this paper uses those estimates to suggest an ordering of the tasks in an attempt to minimize the expected resource consumption for those projects that run a risk of cancellation.


Author(s):  
Marco Kuhrmann ◽  
Georg Kalus ◽  
Gerhard Chroust

Software development projects are complex. The more complex a project is, the higher are the requirements related to the software development process. The implementation of a process is a great challenge. This, in part, has to do with human factors (acceptance, etc.) as the benefits of a formal development process might not be obvious immediately and it may take a while until the process becomes the lifeblood of a team. A crucial step towards implementing, enacting and enforcing a process is to provide tool support for the many activities the process asks for. Tool support is necessary to guarantee efficiency in the project, to do the housekeeping and to minimize the “overhead” of the process. This chapter describes challenges and options for supporting process models by tools. Furthermore it describes concrete samples and shows how tool chains can be created with commercial tools as well as with open source tools.


Author(s):  
Alexander Fürst ◽  
David Inkermann ◽  
Thomas Vietor

Pedestrians are among the most vulnerable participants in current city traffic. While in the past original equipment manufacturers (OEMs, in meanings of carmakers) mainly focused on passenger safety, nowadays strict legislation requirements call for the development of more effective pedestrian safety concepts. Considerations for constructive and technological road safety measures generally take place in a company-specific product development process, but mainly in phases, that do not allow for innovative products in terms of new solutions. Thus, the importance of early development phases as well as design process models, such as Pahl and Beitz, will be described here. Also the significance of the development design cases will be handled, as they can mainly influence the innovation degree of the resulting products. In the end an approach will be introduced, of how an analysis of product models regarding their possibilities for adequate evaluation can help, to support a safety-related development process by integrating suitable design methods and tools.


2010 ◽  
Vol 19 (01) ◽  
pp. 307-323 ◽  
Author(s):  
SALVATORE DISTEFANO ◽  
ANTONIO PULIAFITO ◽  
MARCO SCARPA

Performance related problems are becoming more and more strategic in the software development, especially recently with the advent of Web Services and related business-oriented composition techniques (software as a service, Web 2.0, orchestration, choreography, etc.). In particular, an early integration of performance specifications in the SDP has been recognized during the last few years as an effective approach to improve the overall quality of a software. The goal of our work is the definition of a software development process that integrates performance evaluation and prediction. The software performance engineering development process (SPEDP) we specify is focused on performance, which plays a key role driving the software development process, thus implementing a performance/QoS-driven (software) development process. More specifically, in this paper our aim is to formally define the SPEDP design process, posing particular interest on the basis, on the first step of SPEDP, the software/system architecture design, modeling and/or representation. We define both the diagrams to use and show how to model the structure of the software architecture, its behavior and performance requirements. This is the first mandatory step for the automation of the SPEDP into a specific tool, which we have partially implemented as a performance plug-in for ArgoUML, ArgoPerformance.


2006 ◽  
Vol 05 (03) ◽  
pp. 233-242 ◽  
Author(s):  
Qianwang Deng ◽  
Dejie Yu

The product development capability is a core competence in a company, and the product development process is a knowledge-intensive process. The evolution of engineering design shows that knowledge is a key factor of a successful product development. From the 70's in the last century, artificial intelligence has been introduced into this field. It evolves from expert system through knowledge-based system to current knowledge management. Knowledge taxonomy is a core component in knowledge management. A new approach of mapping knowledge in product development through process modelling is proposed. Product development process modelling can help people structure knowledge and the employees linking to each activity in the product development process. According to the analysis of product development process models, there exist three basic kinds of objects: product states, process elements, and resources. The state-process-resource model provides available ontologies of knowledge in the product development domain. In this way, knowledge is hierarchically classified into six knowledge subjects: product, product process, process element, method, tool, and application specific domain. Furthermore, each of the knowledge subjects is divided into three types of knowledge: course, practice, and expertise location.


Sign in / Sign up

Export Citation Format

Share Document