On the Model-based Documentation of Knowledge Sources in the Engineering of Embedded Systems

In the development of embedded systems the context is of vital importance, as embedded systems interact with the context through sensing and actuation. Information about the system’s context is contained within different knowledge sources and must be elicited and negotiated during embedded systems development. Examples for such knowledge sources may be: laws, standards, internal process specification, systems in operation as well as stakeholders. Modelbased documentation of these knowledge sources supports the analysis of the context (e.g. to aid in prioritizing of requirements, to resolve conflicts between knowledge sources, to trace the impact of changes in the context towards the system, or to gain certification of safety-critical systems). Most approaches dealing with knowledge sources are limited to elicitation and negotiation, but lack proper documentation techniques. Therefore, this paper sketches an approach that addresses the documentation of the context of knowledge, to make knowledge about the sources of contextual information comprehensibly persistent. The corresponding models of the contexts of knowledge can e.g. be used to structure the processes of requirements elicitation and context analysis.

[1]  Wolfgang Böhm,et al.  Challenges in Engineering for Software-Intensive Embedded Systems , 2012, Model-Based Engineering of Embedded Systems.

[2]  Bashar Nuseibeh,et al.  Viewpoints: A Framework for Integrating Multiple Perspectives in System Development , 1992, Int. J. Softw. Eng. Knowl. Eng..

[3]  Klaus Pohl,et al.  Requirements Engineering - Fundamentals, Principles, and Techniques , 2010 .

[4]  D.R. Chand,et al.  Essential systems analysis , 1986, Proceedings of the IEEE.

[5]  Yves Le Traon,et al.  Evaluating Context Descriptions and Property Definition Patterns for Software Formal Validation , 2009, MoDELS.

[6]  Manfred Broy,et al.  Model-Based Engineering of Embedded Systems , 2012, Springer Berlin Heidelberg.

[7]  K. Ketler,et al.  The outsourcing decision , 1993 .

[8]  Michael Jackson,et al.  The World and the Machine , 1995, 1995 17th International Conference on Software Engineering.

[9]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[10]  Marjo Kauppinen,et al.  Requirements Prioritization Challenges in Practice , 2004, PROFES.

[11]  Jan Van den Bergh,et al.  CUP 2.0: high-level modeling of context-sensitive interactive applications , 2006, MoDELS'06.

[12]  T. Buzan How to Mind Map , 2002 .

[13]  Alberto L. Sangiovanni-Vincentelli,et al.  Taming Dr. Frankenstein: Contract-Based Design for Cyber-Physical Systems , 2012, Eur. J. Control.

[14]  Jennifer E. Rowley,et al.  The wisdom hierarchy: representations of the DIKW hierarchy , 2007, J. Inf. Sci..

[15]  Omar El Sawy,et al.  Redesigning the Customer Support Process for the Electronic Economy: Insights From Storage Dimensions , 1997, MIS Q..

[16]  Gregory Piatetsky-Shapiro,et al.  Advances in Knowledge Discovery and Data Mining , 2004, Lecture Notes in Computer Science.

[17]  Thorsten Weyer Kohärenzprüfung von Verhaltensspezifikationen gegen spezifische Eigenschaften des operationellen Kontexts , 2010 .

[18]  James Robertson,et al.  Mastering the Requirements Process: Getting Requirements Right , 2012 .

[19]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[20]  Thomas A. Henzinger,et al.  Interface automata , 2001, ESEC/FSE-9.

[21]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[22]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[23]  Klaus Pohl,et al.  The Three Dimensions of Requirements Engineering: 20 Years Later , 2013, Seminal Contributions to Information Systems Engineering.