Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Identification and Bridging of Semantic Gaps: The Case of Multi-Domain Engineering Andreas M. Hein Institute of Astronauti...
Content <ul><li>1. Context: Frequent problems in Multi-Domain Engineering </li></ul><ul><li>2. Introduction to the Semanti...
1. Context: Frequent problems in Multi-Domain Engineering <ul><li>What is an engineering domain? </li></ul><ul><li>- Mainl...
2. Introduction to the Semantic Gap <ul><li>“ A “semantic gap” is the  difference in meaning  between  constructs  formed ...
2. Introduction to the Semantic Gap 10.05.2010 Workshop Philosophy & Engineering
How to close the gap? <ul><li>Goal:  Increase the synonymy of the constructs! </li></ul>25.05.10 Workshop Philosophy & Eng...
3. Semantic Gaps in Multi-Domain Engineering 10.05.2010 Workshop Philosophy & Engineering
Between stakeholder and engineer 25.05.10 Workshop Philosophy & Engineering 2010
Close the gap between stakeholder and engineer 25.05.10 Workshop Philosophy & Engineering 2010
What is SysML ? <ul><li>[3] </li></ul>25.05.10 Workshop Philosophy & Engineering 2010 1 Structure 2 Behaviour 3 Requiremen...
Within an engineering domain 25.05.10 Workshop Philosophy & Engineering 2010
Close the gap within an domain 25.05.10 Workshop Philosophy & Engineering 2010
Feature Based CAD/CAM <ul><li>feature = geometry + semantics  [2] </li></ul><ul><li>Example:  blind borehole </li></ul><ul...
Between Engineering Domains 25.05.10 Workshop Philosophy & Engineering 2010
Bridging of the Inter-Domain Gap <ul><li>What does usually happen? </li></ul><ul><li>- Searching for analogies (similar st...
Close the gaps between engineering domains 25.05.10 Workshop Philosophy & Engineering 2010
Example using SysML <ul><li>[4] </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
Example using SysML 25.05.10 Workshop Philosophy & Engineering 2010
5. Limits to inter-domain understanding <ul><li>Expert – Novice difference: </li></ul><ul><li>Is this diagram gramatically...
6. Conclusion <ul><li>Many problems in engineering can be associated with the notion „Semantic Gap “ </li></ul><ul><li>Thr...
<ul><li>Thank you for your attention! </li></ul><ul><li>Andreas Hein </li></ul><ul><li>Institute of Astronautics </li></ul...
References <ul><li>[1] Spinczyk, O. (2008) Betriebssysteme, Rechnernetze und verteilte Systeme 1  </li></ul><ul><li>(BSRvS...
Upcoming SlideShare
Loading in …5
×

Identification and Bridging of Semantic Gaps: The Case of Multidomain Engineering

2,368 views

Published on

Andreas Hein's fPET-2010 presentation

Published in: Technology, Business, Education
  • Be the first to comment

Identification and Bridging of Semantic Gaps: The Case of Multidomain Engineering

  1. 1. Identification and Bridging of Semantic Gaps: The Case of Multi-Domain Engineering Andreas M. Hein Institute of Astronautics, Technical University of Munich Workshop Philosophy & Engineering 2010, Golden, Colorado
  2. 2. Content <ul><li>1. Context: Frequent problems in Multi-Domain Engineering </li></ul><ul><li>2. Introduction to the Semantic Gap (SG) </li></ul><ul><li>3. Semantic Gaps in Multi-Domain Engineering </li></ul><ul><li>4. Limits to inter-domain understanding </li></ul><ul><li>5. Conclusion </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  3. 3. 1. Context: Frequent problems in Multi-Domain Engineering <ul><li>What is an engineering domain? </li></ul><ul><li>- Mainly dependent on engineering curriculum (already interdisciplinary) </li></ul><ul><li>- Constantly shifting and fuzzy borders (mechatronics, bionics) </li></ul><ul><li>Frequent problems in Multi-Domain Engineering: </li></ul><ul><li>- Engineer does not understand customer needs </li></ul><ul><li>- Design engineer and production engineer miss opportunities </li></ul><ul><li>- Engineers from different domains have difficulties to understand each other </li></ul><ul><li>What is common to these problems? </li></ul><ul><li>(commonly refered to „communication“ problem) </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  4. 4. 2. Introduction to the Semantic Gap <ul><li>“ A “semantic gap” is the difference in meaning between constructs formed within different representation systems .” </li></ul><ul><li>Example: </li></ul><ul><li>[1] </li></ul>25.05.10 Workshop Philosophy & Engineering 2010 Human understanding Machine understanding
  5. 5. 2. Introduction to the Semantic Gap 10.05.2010 Workshop Philosophy & Engineering
  6. 6. How to close the gap? <ul><li>Goal: Increase the synonymy of the constructs! </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  7. 7. 3. Semantic Gaps in Multi-Domain Engineering 10.05.2010 Workshop Philosophy & Engineering
  8. 8. Between stakeholder and engineer 25.05.10 Workshop Philosophy & Engineering 2010
  9. 9. Close the gap between stakeholder and engineer 25.05.10 Workshop Philosophy & Engineering 2010
  10. 10. What is SysML ? <ul><li>[3] </li></ul>25.05.10 Workshop Philosophy & Engineering 2010 1 Structure 2 Behaviour 3 Requirements 4 Parameter
  11. 11. Within an engineering domain 25.05.10 Workshop Philosophy & Engineering 2010
  12. 12. Close the gap within an domain 25.05.10 Workshop Philosophy & Engineering 2010
  13. 13. Feature Based CAD/CAM <ul><li>feature = geometry + semantics [2] </li></ul><ul><li>Example: blind borehole </li></ul><ul><li>Geometric form: Cylinder with cone at the end </li></ul><ul><li>(diameter, length, angle) </li></ul><ul><li>Semantics: hole that is made of a drill, does not go entirely through the </li></ul><ul><li>material </li></ul>10.05.2010 Workshop Philosophy & Engineering
  14. 14. Between Engineering Domains 25.05.10 Workshop Philosophy & Engineering 2010
  15. 15. Bridging of the Inter-Domain Gap <ul><li>What does usually happen? </li></ul><ul><li>- Searching for analogies (similar structures) in natural language </li></ul><ul><li>- Display ideas in drawings, using common objects (boxes, relations) </li></ul><ul><li>- Increase the synonymy of each others mental representations </li></ul><ul><li>(„cognitive synchronization“) </li></ul><ul><li>- Domain specific documentation </li></ul><ul><li>New development: Integrated documentation in SysML framework </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  16. 16. Close the gaps between engineering domains 25.05.10 Workshop Philosophy & Engineering 2010
  17. 17. Example using SysML <ul><li>[4] </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  18. 18. Example using SysML 25.05.10 Workshop Philosophy & Engineering 2010
  19. 19. 5. Limits to inter-domain understanding <ul><li>Expert – Novice difference: </li></ul><ul><li>Is this diagram gramatically correct? (SysML knowledge required) </li></ul><ul><li>Is the (propositional) content making sense? (domain-knowledge required) </li></ul><ul><li>Economy </li></ul><ul><li>How much effort does it take to convey the knowledge? </li></ul><ul><li>How important is the knowledge? </li></ul><ul><li>Are people willing to learn new „vocabulary“? </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  20. 20. 6. Conclusion <ul><li>Many problems in engineering can be associated with the notion „Semantic Gap “ </li></ul><ul><li>Three characteristic Semantic Gaps in Multi-Domain Engineering </li></ul><ul><li>How to bridge these gaps </li></ul><ul><li>How the understanding between domains works and can be improved </li></ul><ul><li>The limits of inter-domain understanding </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  21. 21. <ul><li>Thank you for your attention! </li></ul><ul><li>Andreas Hein </li></ul><ul><li>Institute of Astronautics </li></ul><ul><li>Technical University of Munich </li></ul><ul><li>[email_address] </li></ul>25.05.10 Workshop Philosophy & Engineering 2010
  22. 22. References <ul><li>[1] Spinczyk, O. (2008) Betriebssysteme, Rechnernetze und verteilte Systeme 1 </li></ul><ul><li>(BSRvS1) Zusammenfassung und Ausblick. Retrieved January 15, 2010, from </li></ul><ul><li>http://ess.cs.uni-dortmund.de/Teaching/SS2008/BSRvS1/Downloads/14-Zusammenfassung-Ausblick-1x2.pdf </li></ul><ul><li>[2] Shah, J.J., Mäntylä, M. (1995). Parametric and Feature Based CAD/CAM. </li></ul><ul><li>New York: John Wiley & Sons, Inc. </li></ul><ul><li>[3] Object Management Group, Systems Modeling Language Specification v.1.1, </li></ul><ul><li>http://www.omgsysml.org </li></ul><ul><li>[4] All SysML diagrams are drawn with the MagicDraw SysML plugin software </li></ul>

×