Information Technology Reference
In-Depth Information
practice area. Methods to develop a re-usable base of core
assets and to develop products that use those core assets are
also discussed. To help organizations to develop SPLs, the
topic describes 29 practice areas that must be mastered. This
topic, however, presents an academic point of view; it lacks
real industry problems. The authors succeed in presenting a
pattern catalog for SPLE. The catalog includes, for instance,
each asset pattern, build pattern, product parts pattern,
assembly line pattern, product builder pattern, cold start
pattern, process pattern, and factory pattern.
8.2. Pohl, Böckle and Van der Linden's topic
The topic from Pohl
et al
. [POH 05b] gives a general
view and the foundations of SPLE, but it does not address
MDE techniques. It is an important work as it clearly
defines the concepts and the processes involved in product
line engineering. It covers most of the questions raised by
this engineering: variability modeling, documentation, testing,
requirements engineering, and traceability. Each process,
domain and application engineering, are split into four stages:
requirements, design, realization, and testing, which gives a
strong consistency to the approach. One chapter is dedicated
to variability management. The topic argues for an orthogonal
variability model and explains how to document variability in
artifacts. It also presents two key organizational aspects not
covered at all in our topic. Traceability is mentioned as an
important aspect in SPLE, but there is no part summarizing a
precise methodology to follow.
8.3. Gomaa's topic
The
Designing Software Product Lines with UML
[GOM 04]
proposes an extension of UML 2.0 to cope with software
families. It presents a UML-based analysis and design method
and uses the model-driven architecture concepts to develop
component-based software for product lines. As such, this
Search WWH ::
Custom Search