Á¤º¸°úÇÐȸ³í¹®Áö (Journal of KIISE)
Current Result Document :
ÇѱÛÁ¦¸ñ(Korean Title) |
ÅäÇÈ ¸ðµ¨¸µ°ú ÀÌÇØ°ü°èÀÚ ¿ä±¸ »êÃâ¹°À» ÀÌ¿ëÇÑ ¿ä±¸»çÇ× ÀÚµ¿ ¿ì¼±¼øÀ§È |
¿µ¹®Á¦¸ñ(English Title) |
Automatic Prioritization of Requirements using Topic Modeling and Stakeholder Needs-Artifacts |
ÀúÀÚ(Author) |
ÀåÁ¾ÀÎ
¹éÁ¾¹®
Jong-In Jang
Jongmoon Baik
|
¿ø¹®¼ö·Ïó(Citation) |
VOL 43 NO. 02 PP. 0196 ~ 0203 (2016. 02) |
Çѱ۳»¿ë (Korean Abstract) |
¼ÒÇÁÆ®¿þ¾î °³¹ß¿¡ ÅõÀڵǴ ÀÚ¿øÀº ÇÑÁ¤µÇ¾î ÀÖÀ¸¹Ç·Î ¿ä±¸»çÇ×µéÀ» ¿ì¼±¼øÀ§ÈÇÏ¿© Áß¿äÇÑ ¿ä±¸»çÇ׺ÎÅÍ ÃæÁ·½ÃÄÑ¾ß ÇÑ´Ù. ±âÁ¸ ¿ä±¸»çÇ× ¿ì¼±¼øÀ§È ±â¹ýµéÀº Àΰ£ÀÇ ¼öµ¿ÈµÈ ÆÇ´Ü¿¡ ÀÇÁ¸ÇϹǷΠ¿ä±¸»çÇ×ÀÇ ¼ö°¡ ¸¹Àº °æ¿ì¿¡´Â Àû¿ëÇϱⰡ Èûµç È®À强 ¹®Á¦¿Í ÀÌÇØ°ü°èÀÚ °³°³ÀÎÀÇ ÆíÇâµÈ °¡Ä¡ÆÇ´Ü¿¡ ³ëÃâµÇ´Â ÆíÇ⼺ ¹®Á¦¸¦ °¡Áö°í ÀÖ´Ù. ÀÌ ¹®Á¦µéÀ» ÇØ°áÇÏ°íÀÚ º» ³í¹®Àº ¿ä±¸»çÇ× µµÃâ ´Ü°è¿¡¼ ¾ò¾îÁö´Â ÀÌÇØ°ü°èÀÚ ¿ä±¸ »êÃâ¹°°ú ÅؽºÆ®ÀÇ ÀǹÌÀû ÁÖÁ¦¸¦ Ã߸®ÇÏ´Â ÅäÇÈ ¸ðµ¨¸µ ±â¹ýÀ» ÀÌ¿ëÇÑ ÀÚµ¿ ¿ä±¸»çÇ× ¿ì¼±¼øÀ§È ±â¹ý, ToMSN(Topic Modeling Stakeholder Needs for requirements prioritization)À» Á¦¾ÈÇÑ´Ù. ÀÌ ±â¹ýÀ» »ç¿ëÀÚ 30,000¸í ±Ô¸ðÀÇ ½ÇÁ¦ ¼ÒÇÁÆ®¿þ¾î ¿ä±¸»çÇ× µ¥ÀÌÅÍ·Î Æò°¡ÇÑ °á°ú, Àΰ£ÀÇ °³ÀÔÀÌ ÇÊ¿ä ¾ø´Â ÀÚµ¿È °úÁ¤À¸·Î È®À强°ú ÆíÇ⼺ ¹®Á¦¸¦ ÇØ°áÇÔ°ú ´õºÒ¾î ¿ì¼±¼øÀ§È Á¤È®µµ ¶ÇÇÑ ±âÁ¸ ¼öµ¿È ±â¹ýµé°ú À¯»çÇÔÀ» È®ÀÎÇÒ ¼ö ÀÖ¾ú´Ù.
|
¿µ¹®³»¿ë (English Abstract) |
Due to the limitations of budget, resources, and time invested in a project, software requirements should be prioritized and be implemented in order of importance. Existing approaches to prioritizing requirements mostly depend on human decisions. The manual prioritization process is based on intensive interactions with the stakeholders, thus raising the issues of scalability and biased prioritization. To solve these problems, we propose a fully automated requirements prioritization approach, ToMSN (Topic Modeling Stakeholder Needs for requirements prioritization), by topic modeling the stakeholder needs-artifacts earned in the requirements elicitation phase. The requirements dataset of a 30,000-user system was utilized for the performance evaluation. ToMSN showed competitive prioritizing accuracy with existing approaches without human aids, therefore solving scalability and biased prioritization issues.
|
Å°¿öµå(Keyword) |
¿ä±¸»çÇ× ¿ì¼±¼øÀ§È
ÀÌÇØ°ü°èÀÚ ¿ä±¸
¿ä±¸°øÇÐ
ÅäÇÈ ¸ðµ¨¸µ
requirements prioritization
stakeholder needs
requirements engineering
topic modeling
|
ÆÄÀÏ÷ºÎ |
PDF ´Ù¿î·Îµå
|