Á¤º¸Ã³¸®ÇÐȸ ³í¹®Áö ¼ÒÇÁÆ®¿þ¾î ¹× µ¥ÀÌÅÍ °øÇÐ
ÇѱÛÁ¦¸ñ(Korean Title) |
¼ÒÇÁÆ®¿þ¾î Á¦Ç° ¶óÀÎÀÇ ¿ä±¸»çÇ×°ú ¾ÆÅ°ÅØó °£ ÃßÀû¼º ¸ðµ¨¸µ |
¿µ¹®Á¦¸ñ(English Title) |
Modeling Traceability Between Software Product Line Requirements and Architecture |
ÀúÀÚ(Author) |
Seokhwan Eom
Sungwon Kang
Jingyu Kim
Seonah Lee
¾ö¼®È¯
°¼º¿ø
±èÁø±Ô
À̼±¾Æ
|
¿ø¹®¼ö·Ïó(Citation) |
VOL 04 NO. 11 PP. 0487 ~ 0498 (2015. 11) |
Çѱ۳»¿ë (Korean Abstract) |
ÃßÀû¼ºÀº ¼ÒÇÁÆ®¿þ¾î °³¹ßÀÚ¿¡°Ô ¼ÒÇÁÆ®¿þ¾î »êÃâ¹°¿¡ ´ëÇÑ º¯°æÀ» ÃßÀûÇÏ°Ô ÇØ ÁØ´Ù. ¼ÒÇÁÆ®¿þ¾î Á¦Ç° ¶óÀÎ °³¹ß¿¡ ÀÖ¾î¼ÀÇ ÃßÀû¼ºÀº °øÅ뼺°ú °¡º¯¼ºÀ» °í·ÁÇØ¾ß Çϱ⠶§¹®¿¡, °³º° Á¦Ç°¿¡¼ÀÇ ÃßÀû¼ºº¸´Ù º¹ÀâÇÏ´Ù. °ú°Å ¿¬±¸¿¡¼ Á¦Ç° ¶óÀÎ °³¹ß¿¡¼ÀÇ Á¦Ç° ÇÇó¿Í ¿ä±¸»çÇ× °£ÀÇ ÃßÀû¼º ±¸ÃàÀ» Á¦½ÃµÇ¾ú´Ù. ±×·¯³ª ¿ä±¸»çÇ×°ú ¾ÆÅ°ÅØó ¼³°è »çÀÌÀÇ ÃßÀû¼º ±¸ÃàÀº ´Ù ´ë ´Ù °ü°è¿Í ¾ÆÅ°ÅØó °èÃþÀ¸·Î ÀÎÇØ °í·ÁÇØ¾ß ÇÒ ¿ä¼Ò°¡ ´õ ¸¹´Ù. º» ³í¹®Àº ÀÌ·¯ÇÑ ¿ä¼ÒµéÀ» °í·ÁÇÏ¿©, Á¦Ç° ¶óÀÎ °³¹ß¿¡¼ÀÇ ¿ä±¸»çÇ×°ú ¾ÆÅ°ÅØó »çÀÌÀÇ ÃßÀû¼ºÀ» ¸ðµ¨¸µÇϴ ü°èÀûÀÎ ¹æ¹ýÀ» Á¦°øÇÑ´Ù. ¶ÇÇÑ »ç·Ê¿¬±¸¸¦ ÅëÇÏ¿© ÀÌ ¹æ¹ýÀÌ È¿°úÀûÀÓÀ» º¸ÀδÙ.
|
¿µ¹®³»¿ë (English Abstract) |
Traceability enables software developers to trace up the changes occurring in software artifacts. In software product line, traceability is more complex than traceability in a single product as commonality and variability should be considered. Modeling traceability between features and requirements has been proposed in the past. However, traceability between requirements and architecture has more factors to consider, including many-to-many mappings and hierarchical structure of architectures. This paper proposes a method of systematically constructing platform traceability between platform requirements and platform architecture. This paper also shows the efficacy of the proposed mechanism through case studies.
|
Å°¿öµå(Keyword) |
Software Product Line
Traceability
Platform
Requirements
Architecture
PFML
PLDT
¼ÒÇÁÆ®¿þ¾î Á¦Ç° ¶óÀÎ
ÃßÀû¼º
Ç÷§Æû
¿ä±¸»çÇ×
¾ÆÅ°ÅØó
PFML
PLDT
|
ÆÄÀÏ÷ºÎ |
PDF ´Ù¿î·Îµå
|