Advertisement

Facilitating Reuse of Control Software Through Context Modelling Based on the Six-Variable Model

  • Nelufar Ulfat-BunyadiEmail author
  • Rene Meis
  • Maritta Heisel
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 743)

Abstract

When control software is developed, the context of the software is not predefined or given. At first, certain properties of objects in the real world need to be monitored/controlled and developers decide which sensors, actuators, other systems to use to monitor/control them, i.e. they make contextual decisions. Frequently, it is not possible to monitor/control exactly these real world properties. Instead, a different set of properties is monitored/controlled whose values are related to the real world properties. Existing approaches like the famous Four-Variable Model call for documenting the monitored, controlled, input, and output variables for a control software. Yet, they do not ask for documenting the properties that have been of interest at first, before deciding which sensors, actuators, other systems to use, i.e. the real world properties. This results in problems when the control software shall later on be reused in another context. The new context may, for example, comprise additional sensors. In this situation, it is hard for developers to decide which input variables are still necessary and should somehow be monitored and which ones not. To avoid such problems, we suggest a context modelling method which is based on our extension of the Four-Variable Model, the Six-Variable Model, and needs to be applied during requirements engineering.

Keywords

Four-Variable Model Context Context modelling Contextual decision Satisfaction argument Domain knowledge Requirement Specification 

References

  1. 1.
    Alebrahim, A., Heisel, M., Meis, R.: A structured approach for eliciting, modeling, and using quality-related domain knowledge. In: Murgante, B., et al. (eds.) ICCSA 2014. LNCS, vol. 8583, pp. 370–386. Springer, Cham (2014). doi: 10.1007/978-3-319-09156-3_27CrossRefGoogle Scholar
  2. 2.
    Bharadwaj, R., Heitmeyer, C.: Hardware/software co-design and co-validation using the SCR method. IEEE International High Level Design Validation and Test Workshop (1999)Google Scholar
  3. 3.
    Broy, M.: Challenges in automotive software engineering. In: Proceedings of the 28th International Conference on Software Engineering (ICSE 2006), pp. 33–42. ACM (2006)Google Scholar
  4. 4.
    Cote, I., Hatebur, D., Heisel, M., Schmidt, H.: UML4PF – a tool for problem-oriented requirements analysis. In: Proceedings of RE 2011, pp. 349–350. IEEE Computer Society (2011)Google Scholar
  5. 5.
    Gunter, C., Gunter, E., Jackson, M., Zave, P.: A reference model for requirements and specifications. IEEE Softw. 17(3), 37–43 (2000)CrossRefGoogle Scholar
  6. 6.
    Jackson, M.: Problem Frames - Analyzing and Structuring Software Development Problems. ACM Press, New York (2001)Google Scholar
  7. 7.
    van Lamsweerde, A.: Requirements Engineering - From System Goals to UML Models to Software Specifications. Wiley, Hoboken (2009)Google Scholar
  8. 8.
    Miller, S.P., Tribble, A.C.: Extending the four-variable model to bridge the system-software gap. In: Proceedings of DASC 2001 (Digital Avionics Systems Conference) (2001)Google Scholar
  9. 9.
    Parnas, D., Madey, J.: Functional documents for computer systems. Sci. Comput. Program. 25(1), 41–61 (1995)CrossRefGoogle Scholar
  10. 10.
    Patcas, L., Lawford, M., Maibaum, T.: From system requirements to software requirements in the four-variable model. In: Proceedings of AVoCS 2013 (Automated Verification of Critical Systems) (2013)Google Scholar
  11. 11.
    Pohl, K.: Requirements Engineering - Fundamentals, Principles, and Techniques. Springer, Heidelberg (2010)Google Scholar
  12. 12.
    Pretschner, A., Broy, M., Krueger, I., Stauner, T.: Software Engineering for Automotive Systems: a roadmap. In: Proceedings of Future of Software Engineering, pp. 55–71. IEEE Compurter Society (2007)Google Scholar
  13. 13.
    Robert Bosch GmbH: ACC Adaptive Cruise Control. The Bosch Yellow Jackets (2003)Google Scholar
  14. 14.
    Ulfat-Bunyadi, N., Meis, R., Heisel, M.: The six-variable model - context modelling enabling systematic reuse of control software. In: Proceedings of ICSOFT-PT 2016 (11th International Joint Conference on Software Technologies), pp. 15–26. SciTePress (2016)Google Scholar
  15. 15.
    Zave, P., Jackson, M.: Four dark corners of requirements engineering. ACM Trans. Softw. Eng. Methodol. 6(1), 1–30 (1997)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • Nelufar Ulfat-Bunyadi
    • 1
    Email author
  • Rene Meis
    • 1
  • Maritta Heisel
    • 1
  1. 1.University of Duisburg-EssenDuisburgGermany

Personalised recommendations