Details
| Originalsprache | Englisch |
|---|---|
| Seiten (von - bis) | 378-386 |
| Seitenumfang | 9 |
| Fachzeitschrift | Proceedings - International Conference on Software Engineering |
| Jahrgang | 26 |
| Publikationsstatus | Veröffentlicht - 2004 |
| Veranstaltung | 26th International Conference on Software Engineering, ICSE 2004 - Edinburgh, Großbritannien / Vereinigtes Königreich Dauer: 23 Mai 2004 → 28 Mai 2004 |
Abstract
A software engineering department in a Daimler-Chrysler business unit was highly professional at developing embedded software for busses and coaches. However, customer specific add-ons were a regular source of hassle. Simple as they are, those individual requirements have to be implemented in hours or days rather than weeks or months. Poor quality or late upload into the bus hardware would cause serious cost and overhead. Established software engineering methods were considered inadequate and needed to be cut short. Agile methods offer guidance when quality, flexibility and high speed need to be reconciled. However, we did not adopt any full agile method, but added single agile practices to our "process improvement toolbox". We suggested a number of classical process improvement activities (such as more systematic documentation and measurement) and combined them with agile elements (e.g. Test First Process). This combination seemed to foster acceptance of agile ideas and may help us to break the ice for a cautious extension of agile process improvement.
ASJC Scopus Sachgebiete
- Informatik (insg.)
- Software
Zitieren
- Standard
- Harvard
- Apa
- Vancouver
- BibTex
- RIS
in: Proceedings - International Conference on Software Engineering, Jahrgang 26, 2004, S. 378-386.
Publikation: Beitrag in Fachzeitschrift › Konferenzaufsatz in Fachzeitschrift › Forschung › Peer-Review
}
TY - JOUR
T1 - Breaking the ice for agile development of embedded software
T2 - 26th International Conference on Software Engineering, ICSE 2004
AU - Manhart, Peter
AU - Schneider, Kurt
N1 - Funding Information: The authors wish to acknowledge that this research was promoted by a stay of H. Steudel at the Clarkson University, Potsdam, New York, as well as by a stay of D. J. Kaup in Berlin. This research has been supported in part by the Max Planck Society of Germany, the National Science Foundation of the USA, the US Air Force Office of Scientific Research and the Office of (US) Naval Research.
PY - 2004
Y1 - 2004
N2 - A software engineering department in a Daimler-Chrysler business unit was highly professional at developing embedded software for busses and coaches. However, customer specific add-ons were a regular source of hassle. Simple as they are, those individual requirements have to be implemented in hours or days rather than weeks or months. Poor quality or late upload into the bus hardware would cause serious cost and overhead. Established software engineering methods were considered inadequate and needed to be cut short. Agile methods offer guidance when quality, flexibility and high speed need to be reconciled. However, we did not adopt any full agile method, but added single agile practices to our "process improvement toolbox". We suggested a number of classical process improvement activities (such as more systematic documentation and measurement) and combined them with agile elements (e.g. Test First Process). This combination seemed to foster acceptance of agile ideas and may help us to break the ice for a cautious extension of agile process improvement.
AB - A software engineering department in a Daimler-Chrysler business unit was highly professional at developing embedded software for busses and coaches. However, customer specific add-ons were a regular source of hassle. Simple as they are, those individual requirements have to be implemented in hours or days rather than weeks or months. Poor quality or late upload into the bus hardware would cause serious cost and overhead. Established software engineering methods were considered inadequate and needed to be cut short. Agile methods offer guidance when quality, flexibility and high speed need to be reconciled. However, we did not adopt any full agile method, but added single agile practices to our "process improvement toolbox". We suggested a number of classical process improvement activities (such as more systematic documentation and measurement) and combined them with agile elements (e.g. Test First Process). This combination seemed to foster acceptance of agile ideas and may help us to break the ice for a cautious extension of agile process improvement.
UR - http://www.scopus.com/inward/record.url?scp=4544343290&partnerID=8YFLogxK
M3 - Conference article
AN - SCOPUS:4544343290
VL - 26
SP - 378
EP - 386
JO - Proceedings - International Conference on Software Engineering
JF - Proceedings - International Conference on Software Engineering
SN - 0270-5257
Y2 - 23 May 2004 through 28 May 2004
ER -