DOI QR코드

DOI QR Code

OVM 중심 가변성 추적 방법에 대한 효용성 검증

Efficiency Validation for the OVM-based Variability Tracing Method

  • 이지현 (대전대학교 혜화리버럴아트칼리지) ;
  • 황선명 (대전대학교 컴퓨터공학과)
  • 투고 : 2015.05.11
  • 심사 : 2015.06.30
  • 발행 : 2015.06.30

초록

추적성은 이해당사자들이 변경으로 인한 산출물들 간의 영향을 분석하는데 필요한 정보를 제공하는 것을 주요 목적으로 한다. 단일 제품 개발과 달리 제품군(群)을 대상으로 하는 소프트웨어 프로덕트라인은 도메인 공학과 어플리케이션 공학의 두 개발 라이프사이클이 있으면서, 가변성과 두 라이프사이클 간의 추적성을 유지하고 관리해야 하기 때문에 그 복잡도가 매우 높다. 이에 개발 산출물과 별도로 가변성을 관리하는 직교적 가변성 모델을 중심으로 하는 가변성 추적성 유지 방법이 개념적으로 제안된 바 있다. 그렇지만, 이 방법이 소프트웨어 제품라인에서 필요로 하는 추적성을 모두 설정할 수 있는지에 대해서는 확인되지 않았다. 본 논문에서는 직교적 가변성 모델을 중심으로 하는 추적성 유지, 관리 방법이 필요한 추적성을 모두 지원하는지 예제를 통하여 검증하였다. 그 결과 OVM 중심 가변성 추적 방법은 변경으로 인해 영향을 받을 수 있는 산출물들의 범위를 한정하는 데는 문제가 없었다. 그렇지만, 변경으로 인해 실제 영향을 받는 구체적이고 정확한 산출물들을 추적하지는 못했다.

Traceability targets provision of information to stakeholders required for analyzing impacts among artifacts due to changes. Unlike single product development, in software product line developing the family of products the complexity of maintaining and managing traceability between two life cycles, domain and application engineering is so high. Accordingly, variability traceability management approach centred on orthogonal variability model that manages variability separated from development artifacts has been conceptually proposed, but its efficiency has not verified yet. This paper verifies whether orthogonal variability model based traceability can provide required traceability through an example. As the results, the OVM-based variability tracing method supports well to narrow down artifacts affected by the changes. However, the method does not support tracing the exact artifacts or exact part of an artifact affected by the change.

키워드

참고문헌

  1. H. U. Asuncion, F. Francois, and R. N. Taylor, "An end-to-end industrial software traceability tool," 6th Joint Meeting of the European Software Engineering Conference and ACM SIGSOFT Symposium on The Foundations of Software Engineering, New York, USA, pp. 115-124, 2007. (conference)
  2. A. Sousa, "Traceability support in software product lines," Master Thesis, Department of Information system and Computer Science, New University of Lisbon, 2008. (journal)
  3. UNL/FCT, Traceability Requirements, "Aspect-oriented, model-driven, product line engineering (AMPLE)," AMPLE Internal Documentation, 2007. (journal)
  4. K. Mohan and B. Ramesh, "Tracing variations in software product families. Communications of the ACM, Vol. 50, No. 12, pp. 68-73, 2007. (journal) https://doi.org/10.1145/1323688.1323697
  5. K. Pohl, G. Bockle, and F. van der Linden, Software Product Line Engineering: Foundations, Principles, and Techniques,: 1st ed., Springer-Verlag, Berlin, Heidelberg, 2005. (book)
  6. N. Anquetil, U. Kulesza, R. Mitschke, A. Moreira, J. C. Royer, A. Rummler and A. Sousa, "A model-driven traceability framework for software product lines," Software and Systems Modeling, Vol. 9, No. 4 pp. 427-451, 2007. (journal) https://doi.org/10.1007/s10270-009-0120-9
  7. J. G. Kim, S. W. Kang, and J. H. Lee, "A comparison of software product line traceability approaches from end-to-end traceability perspectives," International Journal of Software Engineering and Knowledge Engineering, Vol. 24, No.4, pp. 677-714, 2014. (journal) https://doi.org/10.1142/S0218194014500260
  8. W. Jirapanthong and A. Zisman, "XTraQue: Traceability for product line systems", Software and Systems Modeling, pp. 117-144, 2009. (journal)
  9. Kang, K. C., Cohen, S. G., Hess, J. A., Novak, W. E., Peterson, A. S., "Feature-Oriented Domain Analysis (FODA) Feasibility Study," SEI Technical Report, 1990. (Technical Report)
  10. K. Berg, J. Bishop, and D. Muthig, "Tracing Software Product Line Variability -- From Problem to Solution Space," Annual Conference of the South African Institute of Computer Scientists and Information Technologists(SAICSIT05), pp. 182-191, 2005. (conference)
  11. S. Mohalik, S. Ramesh, J-V. Millo, S.N. Krishna, and S.K. Narwane, "Tracing SPLs Precisely and Effciently", 16th international software product line conference, 2012. (conference)
  12. J. Cleland-Huang, R. Settimi and O. BenKhadra, "Goal-centric traceability for managing non-functional requirements," 27th International Conference on Software Engineering, pp. 362-371, 2005. (conference)
  13. M. Mirakhorli, Y. Shin, J. Cleland-Huang and M. Cinar, "A tactic-centric approach for automating traceability of quality concerns," 34th International Conference Software Engineering, pp. 639-649, 2012. (conference)
  14. M. Mirakhorli and J. Cleland-Huang, "Tracing non-functional requirements," Software and Systems Traceability, Springer-Verlag, pp. 299-320, 2012. (book)
  15. J. Lee and S. Hwang, "Value-Based Enterprise Architecture Framework: VBEAF," Journal of The Korea Industrial Information System Society, Vol. 19, No. 6, pp. 77-85, 2014. (journal)
  16. J. Lee and J. Chung, "Comparative Analysis of the Performance of Robot Sensors in the MSRDS Platform," Journal of The Korea Industrial Information System Society, Vol. 19, No. 5, pp. 57-68, 2014. (journal)
  17. S. Hong, E. Han, H. Lee, and J. Kim, "The Conceptual Model for a Co-creation Platform," Journal of The Korea Industrial Information System Society, Vol. 19, No. 3, pp. 127-136, 2014. (journal) https://doi.org/10.9723/jksiis.2014.19.3.127