Vehicle functionality - Why we need a structured development process
Granholm, J. LU
(2005)
In VDI Berichte
p.477-486
- Abstract
In the early days of vehicle engineering, the car was designed top-down. Most design decisions were taken bearing the complete vehicle in mind. As sub-systems have become more complex, and also deeply interlinked, the width of the problem has become impossible for one engineer to understand in all aspects. To be able to cope with this, vehicle manufacturers have created stable partitionings of the vehicle, and organized the development organization around this. However, this has led to a static design process, where some decisions do not have to be taken as they are already given. This in turn means that local sub-optimizations are favoured, whereas completely new solutions on the vehicle level are unlikely to appear. To counter this,... (More)
In the early days of vehicle engineering, the car was designed top-down. Most design decisions were taken bearing the complete vehicle in mind. As sub-systems have become more complex, and also deeply interlinked, the width of the problem has become impossible for one engineer to understand in all aspects. To be able to cope with this, vehicle manufacturers have created stable partitionings of the vehicle, and organized the development organization around this. However, this has led to a static design process, where some decisions do not have to be taken as they are already given. This in turn means that local sub-optimizations are favoured, whereas completely new solutions on the vehicle level are unlikely to appear. To counter this, the author suggests that a reference architecture is created. This would allow all phases of the design process to share the same information set and design rules. Volvo Car Corporation has been using reference architectures for some years. The paper explains the theoretical background to why this step was taken.
(Less)
- author
- Granholm, J.
LU
- publishing date
- 2005-11-23
- type
- Contribution to journal
- publication status
- published
- subject
- in
- VDI Berichte
- issue
- 1907
- pages
- 10 pages
- publisher
- VDI Verlag GMBH
- external identifiers
-
- scopus:27744507923
- ISSN
- 0083-5560
- language
- English
- LU publication?
- no
- id
- 30872487-57d4-47cb-90a8-6971afae985e
- date added to LUP
- 2019-06-21 11:23:23
- date last changed
- 2023-08-30 12:11:29
@article{30872487-57d4-47cb-90a8-6971afae985e,
abstract = {{<p>In the early days of vehicle engineering, the car was designed top-down. Most design decisions were taken bearing the complete vehicle in mind. As sub-systems have become more complex, and also deeply interlinked, the width of the problem has become impossible for one engineer to understand in all aspects. To be able to cope with this, vehicle manufacturers have created stable partitionings of the vehicle, and organized the development organization around this. However, this has led to a static design process, where some decisions do not have to be taken as they are already given. This in turn means that local sub-optimizations are favoured, whereas completely new solutions on the vehicle level are unlikely to appear. To counter this, the author suggests that a reference architecture is created. This would allow all phases of the design process to share the same information set and design rules. Volvo Car Corporation has been using reference architectures for some years. The paper explains the theoretical background to why this step was taken.</p>}},
author = {{Granholm, J.}},
issn = {{0083-5560}},
language = {{eng}},
month = {{11}},
number = {{1907}},
pages = {{477--486}},
publisher = {{VDI Verlag GMBH}},
series = {{VDI Berichte}},
title = {{Vehicle functionality - Why we need a structured development process}},
year = {{2005}},
}