KIPS Transactions on Software and Data Engineering (정보처리학회논문지:소프트웨어 및 데이터공학)

Korea Information Processing Society (한국정보처리학회)
권호 표지
DOI QR코드

DOI QR Code

Modeling Traceability Between Software Product Line Requirements and Architecture

소프트웨어 제품 라인의 요구사항과 아키텍처 간 추적성 모델링

  • Received : 2015.07.03
  • Accepted : 2015.08.18
  • Published : 2015.11.30
Download PDF
⟨ Previous Next ⟩

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.

추적성은 소프트웨어 개발자에게 소프트웨어 산출물에 대한 변경을 추적하게 해 준다. 소프트웨어 제품 라인 개발에 있어서의 추적성은 공통성과 가변성을 고려해야 하기 때문에, 개별 제품에서의 추적성보다 복잡하다. 과거 연구에서 제품 라인 개발에서의 제품 피처와 요구사항 간의 추적성 구축을 제시되었다. 그러나 요구사항과 아키텍처 설계 사이의 추적성 구축은 다 대 다 관계와 아키텍처 계층으로 인해 고려해야 할 요소가 더 많다. 본 논문은 이러한 요소들을 고려하여, 제품 라인 개발에서의 요구사항과 아키텍처 사이의 추적성을 모델링하는 체계적인 방법을 제공한다. 또한 사례연구를 통하여 이 방법이 효과적임을 보인다.

Keywords

References

  1. N. Anquetil, U. Kulesza, R. Mitschke, A. Moreira, J. C. Royer, A. Rummler, and A. Sousa. 2010. "A model-driven traceability framework for software product lines," Software & Systems Modeling, 9(4), (27, June): 427-451. doi:10.1007/s10270-009-0120-9.
  2. J. Bayer and T. Widen, "Introducing traceability to product lines," Product Family Engineering (PFE 2002), Bilbao, Spain, pp.127-147, 2002.
  3. K. Berg and D. Muthig, "Critical analysis of using feature models for variability management," Technical Report. University of Pretoria, May, 2005. [Internet], http://polelo.cs.up.ac.za/personal-pages/kathrin/index.
  4. H. Gomaa, "Designing software product lines with UML: from use cases to pattern-based software architectures," Addison Wesley, 2004.
  5. S. Kang, "A Formal Approach to Modeling Traceability between Platform-level Features and Requirements in Software Product Line Engineering," KAIST MS Thesis, Computer Science, Feb., 2011.
  6. K. Kang, S. Kim, J. Lee, K. Kim, G. J. Kim, and E. Shin., "FORM: A feature-oriented reuse method with domainspecific reference architectures," Annals of Software Engineering, Vol.5, pp.143-168, 1998. https://doi.org/10.1023/A:1018980625587
  7. S. Kang, J. Kim, S. Kang, and S. Eom, "A Formal Representation of Platform Feature-to-Requirement Traceability for Software Product Line Development," The 38th International Computer Software and Applications Conference, (COMPSAC 2014), Sweden 21-25 July, 2014.
  8. S. D. Kim, S. H. Chang and H. J. La, "Traceability Map: Foundations to Automate for Product Line Engineering," SERA, pp.340-347, 2005.
  9. A. J. Lattanze, "Architecting Software Intensive Systems: A Practitioner's Guide," Auerbach Publications, 2009.
  10. K. Pohl, G. Bockle, and F. V. D. Linden, "Software product line engineering: Foundations, Principles, and Techniques," Springer, 2005.
  11. B. Ramesh and M. Jarke, "Toward reference models for requirements traceability," IEEE Transactions on Software Engineering, Vol.27, pp.58-93, 2001. https://doi.org/10.1109/32.895989
  12. A. Sousa, Kulesza, U., Rummler, A., Anquetil, N., Moreira, R. M. A., Amaral, V., and Araujo, J. A., "A model-driven traceability framework to software product line development," ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, Sintef, Trondheim, pp.97-109. 2008.