Abstract
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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Clements, P., Northrop, L.: Software Product Lines-Practices and Patterns. Addison Wesley (2001)
Bosch, J.: Staged Adoption of Software Product Families. In: Software Process Improvement and Practice, pp. 125–142 (2005)
Department of Defense. Systems Engineering Fundamentals. Defense Acquisition University Press (2001)
Sage, A.P.: Systems Engineering. Wiley Series in Systems Engineering. John Wiley & Sons (1992)
Kotonya, G., Sommerville, I.: Requirements Engineering. Worldwide Series in Computer Science. John Wiley & Sons (1998)
CMU/SEI. A Systems Engineering Capability Maturity ModelSM, SECMM-95-01, CMU/SEI-95-MM-003 (1995), http://www.sei.cmu.edu/reports/95mm003.pdf
Thornell, H.: Spetsföretag. Uppsala Publishing House (2007)
Weilkiens, T.: System Engineering with SysML/UML – Modelling, Analysis, Design. The MK/OMG Press (2006)
Fröberg, J., Cedergren, S., Larsson, S.: Eliciting Critical Information in a Pre-Study Phase of Developing a Drive System Platform for Automotive Applications, Systems Engineering and Engineering Management for Sustainable Global Development (2011)
Chastek, G.J., Donohoe, P., McGregor, J.D.: Formulation of a Production Strategy for a Software Product Line. Carnegie Mellon University (2009)
Strobl, S., Bernhart, M., Grechenig, T.: An experience report on the incremental adoption and evolution of an SPL in eHealth. In: ICSE Workshop on Product Line Approaches in Software Engineering, Cape Town, South Africa (2010)
Takebe, Y., Fukaya, N., Chikahisa, M., Hanawa, T., Shirai, O.: Experiences with software product line engineering in product development oriented organization. In: 13th International Software Product Line Conference, San Francisco, California (2009)
van der Linden, F., Bosch, J., Kamsties, E., Känsälä, K., Obbink, H.: Software Product Family Evaluation. In: SPLC (2004)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2012 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Fröberg, J., Cedergren, S., Larsson, S. (2012). What Information on Business Parameters Is Required by Embedded Software Developers to Do an Effective Job?. In: Cusumano, M.A., Iyer, B., Venkatraman, N. (eds) Software Business. ICSOB 2012. Lecture Notes in Business Information Processing, vol 114. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-30746-1_24
Download citation
DOI: https://doi.org/10.1007/978-3-642-30746-1_24
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-30745-4
Online ISBN: 978-3-642-30746-1
eBook Packages: Computer ScienceComputer Science (R0)