Evolutional development of controlling software for agricultural vehicles and robots

Tsuneo Nakanishi, Claes Lund Jæger-Hansen, Hans-Werner Griepentrog

Research output: Contribution to conferencePaperResearchpeer-review

154 Downloads (Pure)

Abstract

Agricultural vehicles and robots expand their controlling software in size and complexity for their increasing functions. Due to repeated, ad hoc addition and modification, software gets structurally corrupted and becomes low performing, resource consuming and unreliable. This paper presents an evolutional development process combining Software Product Line (SPL) and eXtreme Derivation Development Process (XDDP). While SPL is a promising paradigm for successful reuse of software artefacts, it requires understanding of the whole system, a global and future view of the system, and preparation of well managed core assets. By contrast, while XDDP is a less burden process which focuses only on the portion to be changed in the new system, it never prevents software structure from corrupting due to absence of the global view of the system. The paper describes an adoption process for SPL, with an example of the autonomous tractor, that applies XDDP initially for addition and modification of functions, accumulates core assets and cultivates a global view of the system through iterated development with XDDP, and finally shifts to SPL development.
Original languageEnglish
Publication date2012
Number of pages10
Publication statusPublished - 2012
Event3rd International Conference on Machine Control & Guidance - Stuttgart, Germany
Duration: 27 Mar 201229 Mar 2012

Conference

Conference3rd International Conference on Machine Control & Guidance
CountryGermany
CityStuttgart
Period27/03/201229/03/2012

Keywords

  • Software Evolution
  • Software Development Process
  • Software Product Line
  • Derivative Development

Fingerprint Dive into the research topics of 'Evolutional development of controlling software for agricultural vehicles and robots'. Together they form a unique fingerprint.

Cite this