Embedded software design is tightly connected to the functionality and goals of the system it is used to control. For mechatronic systems such as an in-vehicle automotive system, software developers require information on the system goals including business parameters to effectively decide on architecture and functionality. This paper presents results from an case of developing a hybrid electric drive system platform, and presents the information areas that software and system engineers do perceive as important to effectively perform design. We note that business parameters are sought for and elaborate on what information is required. We analyze what these needs are and elaborate on how to address them by using methods from the literature. We conclude that the effort of developing embedded software cannot rely on statically specified business parameters; rather these would be estimated and refined by interaction throughout the development cycle.
3rd International Conference on Software Business, ICSOB 2012; Cambridge, MA;18 June 2012 through 20 June 2012