Many large corporations organize their products in product lines. These products differ in price, capacity and functionality but they also have remarkable similarities. They often share quality, user interface, brand image, service organization and many external interfaces. If these products are controlled by software then software product line techniques can be used in software development to systematically benefit from these differences and similarities. Products can share same software design. Product line software is difficult to design. Requirements for the future products can change, computing hardware and interfaces will evolve and new business opportunities may emerge outside the initial design scope. Large upfront investment into market analysis and flexible software design will decrease but not remove the risk of a poor design. Reuse benefits will more than compensate the extra investment but only if the design is successful. This research proposes a new development approach for software product lines called Goal driven design (GDD). In GDD requirements and design decisions are developed in parallel. This emphasizes the need to explore the design space by developing different alternatives both for requirements and design decisions. Alternative ways to approach a desirable result are compared, and the best is selected. Different products can be based on different alternatives. GDD uses an iterative process. The inner cycle in that iterative process is explorative. Alternative ways to approach product goals and alternative designs decisions are freely explored. The contributions that alternative design decisions have to product goals are noted, but the level of criticism is low. Outer cycle is constructive. Architecture and designs are created based on the ideas from the explorative phase. At times, it is necessary to develop alternative designs. These are carefully evaluated, and the most promising designs are selected as the basis for future work. This guides the developer to address requirements in order, consider variance early, and explore design space widely. This research shows that using this approach it would be possible to explicitly represent and order design decisions that are needed to build a software product line. It also shows with an example that this can be done while defining the first products supported by the new software product line. Description of an experience in applying GDD in a real mid scale project shows how this approach blends with agile development. Scaling is addressed by showing that similar models scale when applied for a large product line. Software development is changed by the practitioners. A study was conducted to find out that a group of software architects that have product line experience from different organizations consider this approach interesting.
|Translated title of the contribution||Goal driven design method for software product lines|
|Publication status||Published - 2013|
|MoE publication type||G4 Doctoral dissertation (monograph)|
- software product line
- software design
- design decisions