DOI QR코드

DOI QR Code

A Scoping Method to Implement Software Product Line for Inertial Navigation System

관성항법소프트웨어 SPL(Software Product Line) 구현을 위한 플랫폼 범위결정 기법

  • Received : 2021.01.28
  • Accepted : 2021.05.18
  • Published : 2021.07.31

Abstract

Software Product Line Engineering (SPLE) has been known as an efficient and effective software reuse methodology. One of the key activities of SPLE is scoping analysis, which determines the range of the features to be developed as reusable assets. Although several scoping methods has been reported, they are not sufficient to apply them to the defense domain. In this paper, we present a scoping method applicable to the defense domain, and present a case study for applying SPLE to inertial navigation weapon system. At first, the proposed method determines the range of candidate features to be applied for the platform. The range is then adjusted from the perspective of product benefit. The final range of features is decided through considering the total cost of a product line. We will demonstrate and evaluate the applicability of the proposed method by showing how we can decide the scope of features to be engineered for the navigation software product line.

SPLE (Software Product Line Engineering)는 소프트웨어 재사용 방법론 중의 하나이다. SPLE의 핵심적인 활동 중 하나는 재사용 가능한 자산 개발에 필요한 피처의 범위를 결정하는 활동이다. 기존 범위결정 방법은 국방 분야에 적용하는데 한계가 있어서, 본 논문에서는 무기체계 항법시스템에 적용 가능한 범위결정 방법을 제안하고, 그 적용 사례를 제시한다. 제안된 방법은 먼저 피처 이익 관점에서 플랫폼 적용 대상 피처의 범위를 결정한다. 그런 다음 제품 이익 관점에서 피처의 범위를 조정하고, 총 비용 관점에서 플랫폼 대상 피처와 제품라인에 포함될 피처의 최종 범위를 결정한다. 본 논문에서는 항법소프트웨어 제품라인에 대해 엔지니어링 할 피처의 범위를 결정하는 방법을 보여줌으로써 제안된 방법의 적용 가능성을 입증하고 평가한다.

Keywords

Acknowledgement

이 논문은 방위사업청 핵심SW과제 연구비에 의하여 연구되었음.

References

  1. O. H. Paek, S. K. Noh, M. K. Choi, and T. H. Lee, "A framework for software product line based development of weapon system software," Communications of KIISE, Vol.36, No.4, pp.19-27, 2018.
  2. K. Pohl, G. Bockle, and F. Van Der Linden, "Software Product line engineering: Foundations, principles, and techniques," Springer, 2005.
  3. S. Y. Park and S. D. Kim, "A systematic method for analyzing business cases in product line engineering," The KIPS Transactions: Part D, Vol.13-D, No.4, pp.565-572, 2006.
  4. F. J. Van der Linden, K. Schmid, and E. Rommes, "Software Product Lines in Action," Springer-Verlag Berlin Heidelberg, 2007.
  5. S. Apel, D. Batory, C. Kastner, and Saake, G. "Feature-oriented software product lines: Concepts and implementation," Springer-Verlag Berlin Heidelberg, 2013.
  6. J. Bayer et al., "PuLSE: A methodology to develop software product lines," Proceedings of the 1999 symposium on Software Reusability, pp.122-131, 1999.
  7. J. Bosch, "Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach," Addison-Wesley, 2000.
  8. J. Lee, S. Kang, and D. Lee, "A Comparison of Software Product Line Scoping Approaches," International Journal of Software Engineering and Knowledge Engineering, Vol.20, No.5, pp.637-663, 2010. https://doi.org/10.1142/S021819401000489X