Browse > Article

(A Formal Model of Component Variability Types and Scope)  

소동섭 (숭실대학교 대학원 컴퓨터학과)
신규석 (한국정보통신기술협회)
김수동 (숭실대학교 컴퓨터학과)
Publication Information
Journal of KIISE:Software and Applications / v.30, no.5_6, 2003 , pp. 414-429 More about this Journal
Abstract
Component-based development(CBD) has been generalized in industry to master the complexity and reduce the development cost and time. However, current CBD practice is developing the component which is dependent on single application[l][2]. Therefore component variability is emphasized to reuse the component in many family members in a domain[8]. However, components are developed for the reason of replaceability rather than the reusability which is the main purpose of the component due to the insufficiency of the study of component variability definition and type[3]. In this paper, we formally specify the component variability reflecting the characteristics of the component to increase the component reusability. We define the logic variability which was recognized as the existing component variability and we propose all types of variability existing in the component by suggesting three more variability types. And we propose the component variability scope which makes us estimate and verify the number of cases of the variability when we customize the component. We propose these component variability types and scope through formal specification. By applying these techniques in developing components, we can develop high quality components reusable in many family members.
Keywords
CBD; CBD; Component; Variability Types; Variability Scope; Formal Specification;
Citations & Related Records
Times Cited By KSCI : 3  (Citation Analysis)
연도 인용수 순위
1 Coplien J., Hoffman D., Weiss D., 'Commonality and Variability in Software Engineering', IEEE Software, pp. 37-45, November 1998   DOI   ScienceOn
2 Object Management Group, OMG Unified Modeling Language Specification, OMG, September 2001
3 D'Souza D., Wills A., Objects, Components, and Frameworks with UML, Addison Wesley, 1999
4 HP Company, Engineering Process Summary: Fusion2.0, Hewlett-Packard Company, January 1998
5 Cheesman J., Daniels J. UML Components : A Simple Process for Specifying Component-Based Software, Addison Wesley, 2001
6 Grahn G., 'Transition from Conventional to Component-based Development', in Int'l Workshop on Component-Based Software Engineering, pp. 78-82, 1999
7 Veryad R., SCPIO: Aims, Principles and Structure, SCPIO Consortium, April 1998
8 Compuware Corp., UNIFACE Development Methodology V7.2, COMPUWARE Corp., 1998
9 Atkinson C, Bayer J., Bunse C, Kamsties E., Laitenberger O., Laqua R., Muthig D., Paech B., Wust J, Zettel J., Component-based Product Line Engineering with UML, Addison Wesley, 2001
10 Lee S., Yang Y., Cho E., Kim S. Rhew S., 'COMO: A UML-based Component Development Methodology', APSEC, pp. 54-61, 1999
11 Bachmann F., Bass Len, 'Managing Variability in Software Architecture,' at URL:http://www.sei.cmu.edu/plp/variability.pdf, Software Engineering Institute(SEI), 2001
12 Kang K. C, Cohen, S. G., Novak, W. E. and Peterson, A. S., 'Feature-oriented Domain Analy-sis(FODA) Feasibility Study', Technical Report CMU/SEI-90-TR-21, Software Engineering Insti-tute(SEI),' November 1990
13 Weiss D. M., and Lai C.T.R., Software Product Line Engineering: A Family Based Software Engineering Process, Addison Wesley, 1999