|Fulltext||0.11 MB||PDF (requires Acrobat Reader)||Previous | Next|
|Authors:||Sebastian Schlund: Faculty of Civil Engineering, Mechanical Engineering, Safety Engineering University of Wuppertal, Wuppertal, Germany|
|Nico Müller: Faculty of Civil Engineering, Mechanical Engineering, Safety Engineering University of Wuppertal, Wuppertal, Germany|
|Publication title:||Developing Quality: Managing Requirements over the Entire Product Life Cycle|
|Conference:||11th QMOD Conference. Quality Management and Organizational Development Attaining Sustainability From Organizational Excellence to SustainAble Excellence; 20–22 August; 2008 in Helsingborg; Sweden|
|Publication type:||Abstract and Fulltext|
|Abstract:||Purpose: The consequent alignment of organizations efforts on requirements towards customer satisfaction sets out the fundament for corporate success. To achieve this objective; the entire life cycle of a product (PLC – Product Life Cycle) has to be considered as relevant for product development. Within the PLC; requirements appear in different instances. Looking comprehensively at the product development process; it seems straightforward to document the information collected during the life cycles of different products and to make it accessible for future development projects.|
Approach: This paper presents an approach to reasonably consider; document and link requirements with requirement-relevant instances in order to achieve an improvement to product development. This approach ensures the use of an up-to-date requirement set at each stage of the entire PLC by instantaneously taking upcoming information into account.
Originality/Value: Although the consequent structuring of requirement-relevant instances allows the selective allocation by relevance; all information is documented so that this provides advantages to subsequent projects. With the “reuse” of requirements; this information comes into focus again and the consequent and structured documentation offers the possibility to improve the initial requirement set and therefore to start with a better information base.
Findings: Employing a continuous consideration of requirements; today’s problems in product development may be resolved and the development process may be adjusted to future needs.
|Keywords:||Requirements management; Product development process; Product life cycle|
|No. of pages:||12|
|Series:||Linköping Electronic Conference Proceedings|
|Publisher:||Linköping University Electronic Press; Linköpings universitet|
|REFERENCE TO THIS PAGE |