An Approach to Develop Requirement as a Core Asset in Product-Line

Mikyeong MOON; Keunhyuk YEOM

An Approach to Develop Requirement as a Core Asset in Product-Line

Mikyeong MOON, Keunhyuk YEOM

Full Text Views

0

Cite this

Summary :

The methodologies of product-line engineering emphasize proactive reuse to construct high-quality products more quickly that are less costly. Requirement engineering for software product families differs significantly from requirement engineering for single software products. The requirements for a product line are written for the group of systems as a whole, with requirements for individual systems specified by a delta or an increment to the generic set. Therefore, it is necessary to identify and explicitly denote the regions of commonality and points of variation at the requirement level. In this paper, we suggest a method of producing requirements that will be a core asset in the product line. Briefly, requirements for families of similar systems (i.e. domain) are collected and generalized which are then analyzed and modeled. The domain requirement as a core asset explicitly manages the commonality and variability. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity increased while significantly reducing error in the requirements.

Publication: IEICE TRANSACTIONS on Information Vol.E87-D No.12 pp.2744-2753

Publication Date: 2004/12/01

Publicized

Online ISSN

DOI

Type of Manuscript: PAPER

Category: Software Engineering

Cite this

Copy

Mikyeong MOON, Keunhyuk YEOM, "An Approach to Develop Requirement as a Core Asset in Product-Line" in IEICE TRANSACTIONS on Information, vol. E87-D, no. 12, pp. 2744-2753, December 2004, doi: .
Abstract: The methodologies of product-line engineering emphasize proactive reuse to construct high-quality products more quickly that are less costly. Requirement engineering for software product families differs significantly from requirement engineering for single software products. The requirements for a product line are written for the group of systems as a whole, with requirements for individual systems specified by a delta or an increment to the generic set. Therefore, it is necessary to identify and explicitly denote the regions of commonality and points of variation at the requirement level. In this paper, we suggest a method of producing requirements that will be a core asset in the product line. Briefly, requirements for families of similar systems (i.e. domain) are collected and generalized which are then analyzed and modeled. The domain requirement as a core asset explicitly manages the commonality and variability. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity increased while significantly reducing error in the requirements.
URL: https://global.ieice.org/en_transactions/information/10.1587/e87-d_12_2744/_p

Copy

@ARTICLE{e87-d_12_2744,
author={Mikyeong MOON, Keunhyuk YEOM, },
journal={IEICE TRANSACTIONS on Information},
title={An Approach to Develop Requirement as a Core Asset in Product-Line},
year={2004},
volume={E87-D},
number={12},
pages={2744-2753},
abstract={The methodologies of product-line engineering emphasize proactive reuse to construct high-quality products more quickly that are less costly. Requirement engineering for software product families differs significantly from requirement engineering for single software products. The requirements for a product line are written for the group of systems as a whole, with requirements for individual systems specified by a delta or an increment to the generic set. Therefore, it is necessary to identify and explicitly denote the regions of commonality and points of variation at the requirement level. In this paper, we suggest a method of producing requirements that will be a core asset in the product line. Briefly, requirements for families of similar systems (i.e. domain) are collected and generalized which are then analyzed and modeled. The domain requirement as a core asset explicitly manages the commonality and variability. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity increased while significantly reducing error in the requirements.},
keywords={},
doi={},
ISSN={},
month={December},}

Copy

TY - JOUR
TI - An Approach to Develop Requirement as a Core Asset in Product-Line
T2 - IEICE TRANSACTIONS on Information
SP - 2744
EP - 2753
AU - Mikyeong MOON
AU - Keunhyuk YEOM
PY - 2004
DO -
JO - IEICE TRANSACTIONS on Information
SN -
VL - E87-D
IS - 12
JA - IEICE TRANSACTIONS on Information
Y1 - December 2004
AB - The methodologies of product-line engineering emphasize proactive reuse to construct high-quality products more quickly that are less costly. Requirement engineering for software product families differs significantly from requirement engineering for single software products. The requirements for a product line are written for the group of systems as a whole, with requirements for individual systems specified by a delta or an increment to the generic set. Therefore, it is necessary to identify and explicitly denote the regions of commonality and points of variation at the requirement level. In this paper, we suggest a method of producing requirements that will be a core asset in the product line. Briefly, requirements for families of similar systems (i.e. domain) are collected and generalized which are then analyzed and modeled. The domain requirement as a core asset explicitly manages the commonality and variability. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity increased while significantly reducing error in the requirements.
ER -