Identification of a reusable requirements structure for embedded products in a dynamic market environment

Customer requirement modeling and mapping of numerical control machine

“…Violante and Vezzetti 3 developed the integrated product life cycle management (PLM) requirement management tool based on the user strategy and by the Kano method to manage the CR. Hauksdo´ttir et al 4 proposed reusable CR rules. Li et al 5 proposed the theory of CR rating and determined the ultimate priority by the minimum deviation method.…”

“…Conduct the same operation on other columns, and no column meeting C 1^C2 Á Á Á^C 5 :C 6 = 1 is found, so b is the only core-value attribute, and core(r 4 ) = fbg M r 4 ð Þ= According to the degree of importance of CR in Table 4, I . K .…”

Challenges for Requirements Engineering of Cyber-Physical Systems in Distributed Environments

“…Finally, the different formalisms and tools of the involved disciplines have to be considered and integrated or replaced. Hauksdóttir et al [16] investigate the management of requirements for complex systems or products. They recognize requirement reuse as an enabler to increase efficiency and quality of Requirements Engineering and propose a structure for a reusable requirement specification.…”

“…For Requirements Engineering, this demands for a requirements structure that allows the specification of the CPS components from different domains and their interaction, as well as the reuse of requirements from previous CPS projects in a modular way. Hauksdóttir [16] defines a reusable requirements structure in a generic way, not focused on the specific characteristics of CPS, while Penzenstadler and Eckhardt [24] primarily focus on fostering information exchange between stakeholders.…”

“…Inadequate Requirements Engineering (RE) is one of the main sources for the failure of development projects and culminates in exceeding budgets, missing functionalities or even the abortion of the project [16]. Consequently, for dynamic systems with evolutionary requirements, the need for continuous interaction between the development process and the requirement elicitation process is inevitable for ensuring a consistent and traceable elicitation and management of requirements [17].…”