Skip to main content Accessibility help
×
Hostname: page-component-848d4c4894-x24gv Total loading time: 0 Render date: 2024-05-02T03:28:56.651Z Has data issue: false hasContentIssue false

Epilogue

Published online by Cambridge University Press:  07 September 2011

Awais Rashid
Affiliation:
Lancaster University
Jean-Claude Royer
Affiliation:
Ecole des Mines de Nantes, France
Andreas Rummler
Affiliation:
SAP Research Center, Dresden
Get access

Summary

The book currently in your hands touches on a wide range of topics in the area of software product line engineering and offers unique solutions to particular problems appearing in the whole development cycle. We show how to semi-automatically derive feature models from requirements documents, dive deeper in modelling variability with a domain-specific language tailored for this purpose, and propose methodologies to develop items in a product-driven as well as in a solution-driven style. We also introduce aspects into core asset development, track changes and decisions in the development process and deal with potential conflicts and uncertainties. However, there is one thread that runs as a common theme through all chapters of this book: all the techniques and methodologies are centred around what we will call conventional software product line engineering. That means that a certain domain is analysed, and a number of components are produced, tested and later on assembled to form actual products, much like in a design–develop–compile–assemble style. It is easy to imagine how software running on modern smart phones, for instance, is developed this way. Other examples following this style can easily be found by looking around. However, the software landscape in which we are living has changed a lot in recent years. Software is no longer produced only by compiling source code, burning the final application onto a CD-ROM and delivering it to a customer. The Internet has opened the door to different styles of product delivery and consumption. Whole applications can be called by clicking a single link and a plethora of web services stands ready for delivering a wide range of functionalities never seen before.

The way of creating an application by consuming and composing services offered by different providers changes the style of application development and, therefore, also affects what we earlier called ‘traditional’ software product line engineering. For this reason new challenges will arise for SPLE that cannot be tackled by traditional solutions.

Type
Chapter
Information
Publisher: Cambridge University Press
Print publication year: 2011

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×