Early Validation of Engineering Artifacts

  • Karsten Albers
  • Peter Battram
  • Alfred Bognar
  • Veronika Brandstetter
  • Andreas Froese
  • Bastian Tenbergen
  • Andreas Vogelsang
  • Joachim Wegener


Valid engineering artifacts are a key success factor for reliable (software) systems. Validity in this sense means that the engineering artifacts are the right ones to completely and correctly describe system properties as desired by stakeholders, and that they are consistent among one another.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [Boehm 1981] B. Boehm: Software Engineering Economics. Prentice Hall, Englewood Cliffs, 1981.Google Scholar
  2. [Brandstetter et al. 2015a] V. Brandstetter, A. Froese, B. Tenbergen, A. Vogelsang, J. C. Wehrstedt, T. Weyer: Early Validation of Control Software for Automation Plants on the Example of a Seawater Desalination Plant. In: Proceedings of CAISE 2015, pp. 189-196.Google Scholar
  3. [Brandstetter et al. 2015b] V. Brandstetter, A. Froese, B. Tenbergen, A. Vogelsang, J. C. Wehrstedt, T. Weyer: Early Validation of Automation Plant Control Software for using Simulation Based on Assumption Modeling and Validation Use Cases. In: Complex Systems Informatics and Modeling Quarterly Issue 4, pp. 50-65.Google Scholar
  4. [Broy 2010] M. Broy: Multifunctional software systems: Structured modeling and specification of functional requirements. In: Science of Computer Programming. Vol. 75, No. 12, 2010.Google Scholar
  5. [Daun et al. 2014] M. Daun, J. Brings, B. Tenbergen, T. Weyer: On the Model-Based Documentation of Knowledge Sources in the Engineering of Embedded Systems. In: Proceedings of the Fourth Workshop on the Future of the Development of Software-Intensive Embedded System Development (ENVISION2020), 2014, pp. 67-76. Google Scholar
  6. [Daun et al. 2015] M. Daun, B. Tenbergen, J. Brings, T. Weyer: Documenting Assumptions about the Operational Context of Long-Living Collaborative Embedded Systems. In: Proceedings of the 2nd Collaborative Workshop on Evolution and Maintenance of Long-Living Software Systetm (EMLS), 2015, pp. 115-117.Google Scholar
  7. [Fagan 1976] M. E. Fagan: Design and Code Inspections to Reduce Errors in Program Development. IBM Systems Journal, Vol. 15, No. 3, 1976, pp. 258-287.Google Scholar
  8. [Farfeleder et al. 2011] S. Farfeleder, T. Moser, A. Krall, T. Stålhane, H. Zojer, C. Panis: DODT: Increasing requirements formalism using domain ontologies for improved embedded systems development. In: Proceedings of the IEEE 14th International Symposium on Design and Diagnostics of Electronic Circuits & Systems (DDECS), 2011, pp. 271-274.Google Scholar
  9. [Flynn and Warhurst 1994] D. Flynn, R. Warhurst: An Empirical Study of the Validation Process within Requirements Determination. In: Information Systems Journal, Vol. 4, No.3, 2014, pp. 185-212.Google Scholar
  10. [Gacirua et al. 2009] R. Gacirua, L. Ma, B. Nuseibeh, P. Piwek, A. de Roeck, M. Rouncefield, P. Sawyer, A. Willis, H. Yang: Making Tacit Requirements Explicit. In: Proceedings of the 2nd International Workshop on Managing Requirements Engineering Knowledge, 2009.Google Scholar
  11. [Glinz and Fricker 2014] M. Glinz, S. A. Fricker: On shared understanding in software engineering: an essay. In: Computer Science-Research and Development. Springer, Berlin Heidelberg, 2014.Google Scholar
  12. [Grochtmann and Grimm 1993] M. Grochtmann, K. Grimm: Classification Trees for Partition Testing. In: Software Testing, Verification & Reliability, Vol. 3, No. 2, 1993.Google Scholar
  13. [ISO/IEC 25010] ISO/IEC: ISO/lEC 25010:2011-03 – Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models. 2011.Google Scholar
  14. [Lisagor et al. 2010] I. Lisagor, L Sun, T. Kelly: The Illusion of Method: Challenges of Model-Based Safety Assesment. In: Proceedings of the 28th International System Safety Conference (ISSC), 2010.Google Scholar
  15. [Reinkemeier et al. 2011] P. Reinkemeier, I. Stierand, P. Rehkop, S. Henkler: A pattern-based requirement specification language: Mapping automotive specific timing requirements. Software Engineering 2011 – Workshopband, 2011.Google Scholar
  16. [Shull et al. 2000] F. Shull, I. Rus, V. Basili: How Perspective-Based Reading Can Improve Requirements Inspections. In: IEEE Computer, Vol. 33, 2000. Google Scholar
  17. [Sikora et al. 2012] E. Sikora, B. Tenbergen, K. Pohl: Industry Needs and Research Directions in Requirements Engineering for Embedded Systems. In: Requirements Engineering, Vol. 17, No.1, 2012, pp. 57-78.Google Scholar
  18. [Staalhane et al. 2010] T. Staalhane, I. Omoronyiam, F. Reichenbach: Ontology guided requirements and safety analysis. In: Proceedings of the 6th International Conference on Safety of Industrial Automated Systems (SIAS 2010), 2010.Google Scholar
  19. [Tenbergen et al. 2015] B. Tenbergen, T. Weyer, K. Pohl: Supporting the Validation of Adequacy in Requirements-Based Hazard Mitigations. In: Proceedings of the 21st International Working Conference on Requirements Engineering: Foundations for Software Quality (REFSQ), 2015, pp. 17-32.Google Scholar
  20. [Vogelsang et al. 2014] A. Vogelsang, S. Eder, G. Hackenberg, M. Junker, S. Teufl: Supporting concurrent development of requirements and architecture: A model-based approach. In: Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development, 2014.Google Scholar
  21. [Vogelsang et al. 2015] A. Vogelsang, H. Femmer, C. Winkler: Systematic Elicitation of Mode Models for Multifunctional Systems. In: Proceedings of the 23rd IEEE International Requirements Engineering Conference, 2015.Google Scholar
  22. [Wiegers 2003] K. Wiegers: Software Requirements. Microsoft Press, Redmond, 2003.Google Scholar

Copyright information

© Springer International Publishing AG 2016

Authors and Affiliations

  • Karsten Albers
    • 1
  • Peter Battram
    • 2
  • Alfred Bognar
    • 3
  • Veronika Brandstetter
    • 4
  • Andreas Froese
    • 5
  • Bastian Tenbergen
    • 6
  • Andreas Vogelsang
    • 7
  • Joachim Wegener
    • 8
  1. 1.INCHRON GmbHPotsdamGermany
  2. 2.BOOM SOFTWARE GMBHVisbekGermany
  3. 3.Airbus DS Electronic and Border Security GmbHUlmGermany
  4. 4.Siemens AGMunichGermany
  5. 5.paluno – The Ruhr Institute for Software TechnologyUniversity of Duisburg-EssenEssenGermany
  6. 6.Department of Computer ScienceState University of New York at OswegoOswegoUSA
  7. 7.Department of InformaticsTechnische Universität München (TUM)GarchingGermany
  8. 8.Berner & Mattner Systemtechnik GmbHMunichGermany

Personalised recommendations