• Àüü
  • ÀüÀÚ/Àü±â
  • Åë½Å
  • ÄÄÇ»ÅÍ
´Ý±â

»çÀÌÆ®¸Ê

Loading..

Please wait....

±¹³» ³í¹®Áö

Ȩ Ȩ > ¿¬±¸¹®Çå > ±¹³» ³í¹®Áö > Çѱ¹Á¤º¸Ã³¸®ÇÐȸ ³í¹®Áö > Á¤º¸Ã³¸®ÇÐȸ ³í¹®Áö ¼ÒÇÁÆ®¿þ¾î ¹× µ¥ÀÌÅÍ °øÇÐ

Á¤º¸Ã³¸®ÇÐȸ ³í¹®Áö ¼ÒÇÁÆ®¿þ¾î ¹× µ¥ÀÌÅÍ °øÇÐ

Current Result Document : 5 / 6 ÀÌÀü°Ç ÀÌÀü°Ç   ´ÙÀ½°Ç ´ÙÀ½°Ç

ÇѱÛÁ¦¸ñ(Korean Title) Â÷·®ÀüÀå¿ë ¼ÒÇÁÆ®¿þ¾îÀÇ API Á¦¾à»çÇ× À§¹è¿©ºÎ ŽÁö¸¦ À§ÇÑ ½ÇÇà°æ·Î Ž»ö¹æ¹ý°ú ¸ðµ¨°ËÁõ ¹æ¹ýÀÇ ºñ±³
¿µ¹®Á¦¸ñ(English Title) Comparison of Path Exploration and Model Checking Techniques for Checking Automotive API Call Safety
ÀúÀÚ(Author) ±èµ¿¿ì   ÃÖÀ±ÀÚ   Dongwoo Kim   Yunja Choi  
¿ø¹®¼ö·Ïó(Citation) VOL 05 NO. 12 PP. 0615 ~ 0622 (2016. 12)
Çѱ۳»¿ë
(Korean Abstract)
Â÷·®ÀüÀå¿ë Á¦¾î ¼ÒÇÁÆ®¿þ¾î´Â Ç¥ÁØ¿¡ ¸í½ÃµÈ ½Ã½ºÅÛ È£Ãâ Á¦¾à»çÇ×À» À§¹èÇÒ °æ¿ì ½É°¢ÇÑ ¾ÈÀü¼º À§ÇùÀ» ÃÊ·¡ÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª Á¦¾à»çÇ× À§¹è´Â ½ÇÇà°æ·Î°¡ º¹ÀâÇØÁú °æ¿ì ¼öµ¿ºÐ¼®À¸·Î »öÃâÇϱ⠾î·Æ°í Å×½ºÆÃÀ» ÅëÇØ Ã£¾Æ³»±âµµ ¾î·Á¿ö ÀÌ¿¡ ƯȭµÈ °ËÁõ ¹æ¹ýÀÌ ÇÊ¿äÇÏ´Ù. º» ¿¬±¸¿¡¼­´Â Â÷·®ÀüÀå¿ë Á¦¾î ¼ÒÇÁÆ®¿þ¾îÀÇ ½Ã½ºÅÛ È£Ãâ Á¦¾à»çÇ× À§¹è ¿©ºÎ¸¦ È¿°úÀûÀ¸·Î °ËÁõÇϱâ À§ÇÑ µÎ °¡Áö ¹æ¹ýÀ» ¼Ò°³ÇÏ°í ±× È¿°ú¸¦ ½ÇÇèÀûÀ¸·Î ºñ±³ÇÏ¿´´Ù. ù ¹ø° ¹æ¹ýÀº ¾ÖÇø®ÄÉÀ̼ÇÀÇ ¸ðµç °¡´ÉÇÑ ½ÇÇà°æ·Î¸¦ Ž»öÇÏ°í °¢ °æ·ÎÀÇ Á¦¾à»çÇ× Áؼö¿©ºÎ¸¦ È®ÀÎÇÏ´Â ¹æ¹ýÀ̸ç, µÎ ¹ø° ¹æ¹ýÀº ¸ðµ¨ °ËÁõ µµ±¸¸¦ ÀÌ¿ëÇÏ¿© ¾ÖÇø®ÄÉÀ̼ÇÀÌ ¿ÀÅ丶Ÿ·Î Ç¥ÇöµÈ Á¦¾à»çÇ×À» À§¹èÇÏ´Â °æ¿ì°¡ ¹ß»ý°¡´ÉÇÑÁö È®ÀÎÇÏ´Â ¹æ¹ýÀÌ´Ù. °¢ ¹æ¹ýÀ» ±¸ÇöÇÏ°í ½ÇÇèÇÑ °á°ú ½ÇÇà°æ·Î¸¦ ÀÌ¿ëÇÑ ¹æ¹ýÀº ¿ÀŽÀ» À¯¹ßÇÏ°í ¸î °¡Áö Á¦¾à»çÇ× À§¹ÝÀ» ³õÄ¡´Â °æ¿ì°¡ Àִµ¥ ¹ÝÇؼ­ ¸ðµ¨ °ËÁõÀ» ÀÌ¿ëÇÑ ¹æ¹ýÀº ¿ÀŽÀÌ ¾ø¾úÀ¸¸ç ºñ±³Àû Å« ¾ÖÇø®ÄÉÀ̼ÇÀ» ´ë»óÀ¸·Î º¸´Ù ºü¸¥ ½Ã°£ ³»¿¡ °ËÁõÀ» ¼öÇàÇÒ ¼ö ÀÖÀ½À» º¸¿´´Ù.
¿µ¹®³»¿ë
(English Abstract)
Automotive control software can be a source of critical safety issues when developers do not comply system constraints. However, a violation is difficult to identify in complicated source code if not supported by an automated verification tool. This paper introduces two possible approaches that check whether an automotive control software complies API call constraints to compare their performance and effectiveness. One method statically analyzes the source code and explores all possible execution paths, and the other utilizes a model checker to monitor constraint violations for a given set of constraint automata. We have implemented both approaches and performed a series of experiments showing that the approach with model-checking finds constraint violations more accurately and scales better.
Å°¿öµå(Keyword) Â÷·®ÀüÀå¼ÒÇÁÆ®¿þ¾î   ¾ÖÇø®ÄÉÀÌ¼Ç ÇÁ·Î±×·¡¹Ö ÀÎÅÍÆäÀ̽º   OSEK/VDX   Á¦¾à»çÇ× ÆÐÅÏ   Á¤ÀûºÐ¼®   ¸ðµ¨°ËÁõ   Automotive Software   API   OSEK/VDX   Constraint Pattern   Static Analysis   Model Checking  
ÆÄÀÏ÷ºÎ PDF ´Ù¿î·Îµå