By Klaus Pohl
This textbook addresses scholars, execs, teachers and researchers attracted to software program product line engineering. With greater than a hundred examples and approximately a hundred and fifty illustrations, the authors describe intimately the basic foundations, rules and strategies of software program product line engineering.The authors are pros and researchers who considerably inspired the software program product line engineering paradigm and effectively utilized software program product line engineering ideas in undefined. they've got based this textbook round a finished product line framework.Software product line engineering has confirmed to be the paradigm for constructing a range of software program items and software-intensive structures in shorter time, at cheaper price, and with greater caliber. It enables platform-based improvement and mass customisation. The authors intricate at the key rules in the back of software program product line engineering: (1) the separation of software program improvement in certain methods, area and alertness engineering; (2) the categorical definition and administration of the variety of the product line throughout all improvement artefacts.As a pupil, you will discover a close description of the main tactics, their actions and underlying suggestions for outlining and dealing with software program product line artefacts. As a researcher or lecturer, you'll find a accomplished dialogue of the state-of-the-art organised round the finished framework. As a certified, you can find guidance for introducing this paradigm on your corporation and an outline of commercial reviews with software program product line engineering.
Read or Download Software Product Line Engineering: Foundations, Principles and Techniques PDF
Similar management information systems books
These days, internet purposes are virtually omnipresent. the net has develop into a platform not just for info supply, but in addition for eCommerce platforms, social networks, cellular prone, and disbursed studying environments. Engineering net purposes consists of many intrinsic demanding situations as a result of their allotted nature, content material orientation, and the requirement to lead them to to be had to a large spectrum of clients who're unknown upfront.
Integration Models: Templates for Business Transformation
This publication presents a confirmed method of EAI, supplying examples from real perform, and exploring the stairs to stick with for its daily implementation. initially designed for corporations present process major merger and acquisition job, Integration types have developed right into a operating toolkit for bridging the distance among company and technical types.
Service Engineering: Entwicklung und Gestaltung innovativer Dienstleistungen
Die schnelle und effiziente Realisierung innovativer Dienstleistungen stellt zunehmend einen Erfolgsfaktor für die Wettbewerbsfähigkeit von Dienstleistungsunternehmen dar. Dienstleistungen werden in der Praxis jedoch oft "ad hoc", d. h. ohne systematische Vorgehensweise, entwickelt. Das Konzept des "Service Engineering" beschreibt Vorgehensweisen, Methoden und Werkzeugunterstützung für die systematische Planung, Entwicklung und Realisierung innovativer Dienstleistungen.
Extra info for Software Product Line Engineering: Foundations, Principles and Techniques
Sample text
The input for product management consists of the company goals defined by top management. The output of product management is a product roadmap that determines the major common and variable features9 of future products as well as a schedule with their planned release dates. In addition, product management provides a list of existing products and/or development artefacts that can be reused for establishing the platform. Input and output Product management for software product lines differs from product management for single systems for the following reasons: Differences from single-system engineering The platform has an essential strategic meaning for the company.
Failing to introduce the required variability leads to additional costs for realising common and even variable parts in each product. Moreover, it is important to use an appropriate level of abstraction to define the variability of a product line. Ideally, the variability abstractions match the commonly used domain abstractions. Domain-related abstractions are known to the customers and developers and thus help them to understand the variability of the product line. Not knowing the domain leads to incorrect abstractions with the danger that they are not perceived by the stakeholders, and thus cause wrong choices, which have to be repaired afterwards.
This fact was exploited by employing software flexibly and adapting it at very late stages of development, thus easing many problems of system developers. Not much thought was spent on how software was produced. Outside the embedded system world, software was typically not regarded as being variable. Either a customer could buy a software system including all possible features one might ever need, or software was produced for a single purpose by order of a single customer. 7 See the introduction of [V.