Browse > Article
http://dx.doi.org/10.3745/KIPSTD.2006.13D.4.583

An Elicitation Approach of Measurement Indicator based an Product line Context  

Hwang Sun-Myung (대전대학교 컴퓨터공학과)
Kim Jin-Sam (한국전자통신연구원 임베디드소프트웨어연구단)
Publication Information
The KIPS Transactions:PartD / v.13D, no.4, 2006 , pp. 583-592 More about this Journal
Abstract
Software development based on product lines has been proved a promising technology that can drastically reduce cycle time and guarantee quality by strategically reusing quality core assets that belong to an organization. However, how to measure within a product line is different from how to measure within a single software project in that we have to consider the aspects of both core assets and projects that utilize the assets. Moreover, the performance aspects of overall project lines need to be considered within a product line context. Therefore, a systematic approach to measure the performance of product lines is essential to have consistent, repeatable and effective measures within a product line. This paper presents a context-based measurements elicitation approach for product lines that reflects the performance characteristics of product lines and the diversity of their application. The approach includes both detailed procedures and work products resulting from implementation of the procedures, along with their templates. To show the utility of the approach, this paper presents the elicited measurements, especially for technical management practices among product line practices. This paper also illustrated a real application case that adopt this approach. The systematic approach enables management attributes, i.e., measurements to be identified when we construct product lines or develop software product based on the product lines. The measurements will be effective in that they are derived in consideration of the application context and interests of stakeholders.
Keywords
Product; Product-Line; Core Asset; Measurement; Indicator; Context;
Citations & Related Records
연도 인용수 순위
  • Reference
1 D. Zubrow et al., Measures for Software Product Lines (CMU/SEI-2003-TN-031), Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2003
2 V.R. Basili, Using Measurement for Quality Control and Process Improvement, Second Annual SEPG Workshop, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, June, pp.21-22, 1989
3 R.E. Park, W.B. Goethert, W.A. Florae, A Goal-Driven Software Measurement - A Guidebook (CMU/SEI-96-HB-002, ADA313946), Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 1996
4 V.R. Basili and H.D. Rombach, The TAME Project: Towards Improvement-Oriented Software Environment, IEEE Transactions of Software Engineering, Vol.14, No.6, pp.758-773, June, 1988   DOI   ScienceOn
5 S. Kettemann, D. Muthig, and M. Anastasopoulos, Product Line Implementation Tecnologies: Component technologiy View, technical Report, No.015.03/E, IESE, March, 2003
6 International Organization for Standardization. Information technology - Process assessment - Part 1: Concepts and vocabulary. Reference number: ISO/IEC 15504-1: 2004(E). Geneva, Switzerland: International Organization for Standardization, 2004
7 International Organization for Standardization. Software engineering - Software measurement process. Reference number: ISO/IEC 15939: 2002 (E). Geneva, Switzerland: International Organization for Standardization, 2002
8 Software Engineering Institute. CMMI-SE/SW/IPPD/SS, v1.1 Capability Maturity Model Integration for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing, Continuous Representation, Version 1.1 (CMU/SEI-2002-TR-011), Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2002
9 Software Engineering Institute. CMMI-SE/SW/IPPD/SS, v1.1 Capability Maturity Model Integration for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing, Staged Representation, Version 1.1 (CMU/SEI-2002-TR-012), Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2002
10 Kyo C. Kang, Jaejoon Lee, and Patrick Donohoe, Feature Oriented Product Line Engineering, IEEE Software, 19(4):58-65, July/August, 2002   DOI   ScienceOn
11 D. Weiss, Software Synthesis: The FAST Process. In Proceedings of the International Conference on Computing in High Energy Physics(CHEP), September 1995
12 P. Clements and L. Northrop, Software Product Lines : Practices and Patterns, Addison Wesley, 2001
13 J. Bayer, O. Flege, P. Knauber, R. Laqua, D. Muthig, K. Schmid, T. Widen, and J.-M. Debaud, PuLSE: A methodology to Develop Software product Lines, Proceedings of the Fifth ACM SIGSOFT Symposium on Software Reusability (SSR'99), pp.122-131, Los Angeles, CA, USA, May, 1999   DOI
14 Colin Atkinson et. al., Component-based Product Line Engineering with UML, Component Software Series, Addison-Wesley, 2001
15 K. Kang, S. Cohen, J. Hess, W. Novak, and S. Peterson, Feature-Oriented Domain Analysis(FODA) Feasibility Study. Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University, November, 1990
16 K. Pohl, G. Bockle, F. van der Linden, Software Product Line Engineering : Foundations, Principles, and Techniques, Springer, 2005
17 J-C. Trigaux and P. Heymans, Software product Lines: State of art, 2003
18 D. Zubrow et al., Developing a Measurement Program for Software Product Lines, Tutorial Notes of the Third Software Product Line Conference (SPLC 2003), Boston, MA, USA, August 30-September 2, 2004
19 박창순 외, 임베디드 시스템 개발 프레임워크 구축, 정보통신부, 2006
20 D. Zubrow and G. Campbell., Basic Metrics for Software Product Lines (CMU/SEI-00-TN-012), Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2000