An Operational Tool to Assess Configuration Lifecycle Maturity The use of product configurators is a wellestablished strategy for companies to support their productsu0027 different life cycle phases (engineering, sales, manufacturing, services). The configuration lifecycle management concept is highly relevant for complex configurable products. The business value gained comes in the form of improved leadtimes, quality, and costs; benefits perceived both internally by the company and externally by their customers, in the form of increased satisfaction. The size of these benefits is also related to the maturity of the organization with regards to configuration lifecycle management. Therefore, this paper examines an operational approach to assess the level of configuration lifecycle maturity. The focus is on how to guide manufacturing companies to achieve the full potentials from operating configurators across all lifecycle phases of their products. Furthermore, how to assess and improve the utilization of configurators across all productu0027s lifecycle phases within manufacturing companies will be elaborated. The findings of this paper are supplemented with a case study conducted at an engineering company that has been working with configurators for 10 years and it has now high emphasis on digitalization.

What should your runtime configuration framework do to help developers? The users or deployment engineers of a software system can adapt such a system to a wide range of deployment and usage scenarios by changing the value of configuration options, for example by disabling unnecessary features, tweaking performancerelated parameters or specifying GUI preferences. However, the literature agrees that the flexibility of such options comes at a price: misconfigured options can lead a software system to crash in the production environment, while even in the absence of such configuration errors, a large number of configuration options makes a software system more complicated to deploy and use. In earlier work, we also found that developers who intend to make their application configurable face 22 challenges that impact their configuration engineering activities, ranging from technical to managementrelated or even inherent to the domain of configuration engineering. In this paper, we use a prototyping approach to derive and empirically evaluate requirements for tool support able to deal with 13 (primarily technical) configuration engineering challenges. In particular, via a set of interviews with domain experts, we identify four requirements by soliciting feedback on an incrementally evolving prototype. The resulting xe2x80x9cConfig2Codexe2x80x9d prototype, which implements the four requirements, is then empirically evaluated via a user study involving 55 participants that comprises 10 typical configuration engineering tasks, ranging from the creation, comprehension, refactoring, and reviewing of configuration options to the quality assurance of options and debugging of configuration failures. A configuration framework satisfying the four requirements enables developers to perform more accurately and more swiftly in 70% and 60% (respectively) of the configuration engineering tasks than a stateofthepractice framework not satisfying the requirements. Furthermore, such a framework allows to reduce the time taken for these tasks by up to 94.62%, being slower for only one task.