BibTeX
@MISC{_workshopsummary,
author = {},
title = {Workshop Summary},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
support the software process has focused on the process of developing and evolving a single software product. Increasingly, organizations are finding advantages in product-line software approaches, involving investments in domain engineering, product line architectures, and rapid applications composition with extensive use of commercial-off-the-shelf (COTS) and other reusable software assets. Recent books on software reuse and product line management [Jacobson-Griss-Jonsson, 1997; Poulin, 1997; Reifer, 1997] provide extensive evidence of the advantages: factors of 1.5 to 4 improvements in development time, factors of 1.5 to 6 in productivity, and factors of 2-10 in defect rates. Software product line management involves significant software process challenges: for example, large-scale software packages (COTS and in-house) often provide so much of an application system’s desired functionality that the most effective software approach is for the COTS/reuse capabilities to drive the requirements, rather thanthe traditional requirements-to-capabilities process model. Previous processes and some current process approaches have inhibited reuse. The waterfall model and top-down programming calculus approaches are good examples, as reuse has major bottom-up drivers. Some process maturity models and best-practice initiatives are reuse-insensitive. They are basically best practices for building one-off "stovepipe " systems. Some current process initiatives- EIA/IEEE J-STD-016, ISO/IEC 12207 – accommodate reuse overall, but are still light on guidance about how reuse affects intermediate milestones and
Keyphrases
workshop summary best-practice initiative previous process software reuse reuse affect intermediate milestone defect rate product-line software approach major bottom-up driver domain engineering extensive use extensive evidence product line architecture top-down programming calculus approach significant software process challenge process maturity model good example application system accommodate reuse current process approach software product line management single software product reusable software asset cot reuse capability product line management jacobson-griss-jonsson one-off stovepipe system recent book effective software approach iso iec software process rapid application composition development time large-scale software package waterfall model thanthe traditional requirements-to-capabilities process model
