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

»çÀÌÆ®¸Ê

Loading..

Please wait....

±¹³» ³í¹®Áö

Ȩ Ȩ > ¿¬±¸¹®Çå > ±¹³» ³í¹®Áö > Çѱ¹Á¤º¸°úÇÐȸ ³í¹®Áö > Á¤º¸°úÇÐȸ³í¹®Áö (Journal of KIISE)

Á¤º¸°úÇÐȸ³í¹®Áö (Journal of KIISE)

Current Result Document :

ÇѱÛÁ¦¸ñ(Korean Title) °´Ã¼ÁöÇ⠺м®ÀÇ À¯½ºÄÉÀ̽º¿Í UML ¸ðµ¨À» ÀÌ¿ëÇÑ µ¿Àû ¿µÇ⠺м® ¹æ¹ý
¿µ¹®Á¦¸ñ(English Title) Dynamic Impact Analysis Method using Use-case and UML Models on Object-oriented Analysis
ÀúÀÚ(Author) ÀÌÂù   À±Ã»   Chan Lee   Cheong Youn  
¿ø¹®¼ö·Ïó(Citation) VOL 43 NO. 10 PP. 1104 ~ 1114 (2016. 10)
Çѱ۳»¿ë
(Korean Abstract)
¼ÒÇÁÆ®¿þ¾îÀÇ º¯°æÀº °³¹ß ±â°£ ¶Ç´Â °³¹ß ÀÌÈÄ¿¡µµ Áö¼ÓÀûÀ¸·Î ¿ä±¸µÈ´Ù. º¯°æ ¿äû ½Ã ¿µÇâ
ÀÇ ¹üÀ§¸¦ Á÷°üÀûÀ¸·Î Á¤È®È÷ ÆľÇÇÏ´Â °ÍÀº ¾î·Á¿î ÀÏÀ̸ç, ü°èÀûÀÎ ¹æ¹ýÀ» ÅëÇØ º¯°æ ¿µÇâÀÇ ¹üÀ§¸¦ º¸´Ù Á¤È®ÇÏ°Ô ÆľÇÇÏ´Â °úÁ¤ÀÌ ÇÊ¿äÇÏ´Ù. º¯°æ ¿µÇ⠺м®Àº º¯°æ¿¡ ÀÇÇØ ¾ß±âµÇ´Â ÆÄ±Þ È¿°ú¸¦ ÀνÄÇÏ¿© ´©¶ôµÇ´Â ºÎºÐÀÌ ¾øµµ·Ï ÇÏ´Â °ÍÀ» ±× ¸ñÀûÀ¸·Î ÇÑ´Ù. º» ³í¹®Àº °´Ã¼ÁöÇâ °³¹ß ȯ°æ¿¡¼­ À¯½ºÄÉÀ̽º ½Ã³ª¸®¿À¿Í UML ¸ðµ¨¸µ »êÃâ¹°µé °£ÀÇ ¿¬°ü °ü°è¸¦ ÀÌ¿ëÇÏ¿© º¯°æ ¿äûÀ¸·Î ÀÎÇÑ ¿µÇâÀÇ ¹üÀ§¸¦ ½±°Ô ÆľÇÇÒ ¼ö ÀÖ´Â ¹æ¹ýÀ» Á¦½ÃÇÑ´Ù. ÀÌ ¹æ¹ýÀº À¯½ºÄÉÀ̽º ½Ã³ª¸®¿ÀÀÇ º¯°æÀ¸·Î ÀÎÇØ ´Ù¸¥ ±¸¼º¿ä¼Òµé(Ŭ·¡½º ´ÙÀ̾î±×·¥, ½ÃÄö½º ´ÙÀ̾î±×·¥)ÀÌ ¹ÞÀ» ¼ö ÀÖ´Â ¿µÇâÀÇ ¹üÀ§¸¦ ¼ø¹æÇâ ÃßÀûÀ» ÅëÇØ ÆľÇÇÏ°í, ±¸¼º¿ä¼ÒÀÇ º¯°æÀ¸·Î ÀÎÇØ Ãß°¡ÀûÀ¸·Î ¹ß»ýÇÒ ¼ö ÀÖ´Â º¯°æ °¡´É¼º¿¡ ´ëÇÑ ¿µÇ⠺м®Àº ¿ª¹æÇâ ÃßÀû °úÁ¤À» ÅëÇØ ¼øȯÀûÀ¸·Î ÀÌ·ç¾îÁø´Ù. º» ³í¹®ÀÇ °á°ú´Â ¿µÇ⠺м® ´ë»ó(»êÃâ¹°)À̳ª º¯°æ À¯Çü¿¡ Á¦ÇÑÀ» ¹ÞÁö ¾Ê¾Æ, ´Ù¾çÇÑ º¯°æ ¿äûÀ¸·Î ÀÎÇÑ ¿µÇ⠺м® ½Ã ±âÃÊÀûÀÎ °¡À̵å¶óÀÎÀ¸·Î È°¿ëÇÒ ¼ö ÀÖ´Ù.
¿µ¹®³»¿ë
(English Abstract)
Software is continuously changing during development and after development. When a change is required, it is difficult to precisely grasp the scope of impact intuitively. A systematic method is needed to accomplish the required change. The purpose of impact analysis on software change is to avoid missing any information by recognizing the ripple effect that the change might cause. This paper proposes a dynamic method that can easily identify the scope of change request by using the association between use-case scenarios and artifacts of UML modeling in object-oriented development environment. By using this approach, the scope of impact that the change might have on other components such as class diagram and sequence diagram in use-case scenarios can be identified by forward tracing. In addition, analysis of influence of possible further changes due to changes in other components can be identified iteratively through backward tracing. The results of this paper are not limited to impact analysis on artifacts and change type. They can also be used as basic guidelines during impact analysis for various change requests.
Å°¿öµå(Keyword) impact analysis   UML Models   software change   use-case scenario   ¿µÇ⠺м®   UML ¸ðµ¨   ¼ÒÇÁÆ®¿þ¾î º¯°æ   À¯½ºÄÉÀ̽º ½Ã³ª¸®¿À  
ÆÄÀÏ÷ºÎ PDF ´Ù¿î·Îµå