Using the PLE approach we built, at the domain engineering level, a WSbWA-specific lightweight product-line architecture and combined it, at the application engineering level, with an Agile Method that uses a domain-specific visual language with direct manipulation and extraction capabilities of web services to perform customization and calibration of a product or WSBWA for a specific customer.
This is in line with several industrial companies that, after more than 5-year experience in tailoring agile methods, still use and do not see big problems in using company-specific less agile system testing, validation and releasing practices (e.g., [24, 50]).
As an example, most of the empirical studies found by Dybå and Dingsøyr [25] are related to XP (76 %), while our survey indicates that most of the companies from our sample are using Scrum as the main agile method (51.2 % use Scrum and 22.5%% use Scrum/XP hybrid).
Earlier reviews [P1,P22] have found out that agile methods could be used in an embedded domain, but their use is not yet widespread.
Also, the used agile method from each article was mapped.
Instead of adapting some specific agile method, [P18] and [P26] used some agile practices in development.
The second development methodology is the agile method that is commonly used for game development.
In the review, the current state of agile methods is examined; the most often used agile method is found, and the challenges in adopting these methods in embedded systems are discussed.
There were many experience reports which stated that agile methods could be used in the embedded domain.
Kettunen and Laanti [P11] also have various pragmatic suggestions on how agile methods could be used in large-scale embedded software products based on industrial experience.
