Are requirements engineering best practices the same for all industries?

Requirements engineering has become inescapable for industrial projects. But in every day life, project actors (acquirers, systems engineers, software engineers, information system analysts, domain experts, etc.) are facing multiple constraints: to meet project or company goals (quality, delays, costs), to define and balance requirements from various stakeholders, to use dedicated tools, to create traceability. And one of the key remaining questions is still: how to implement requirements engineering in the most efficient way? Various methods, techniques and tools have been tried out, adopted and optimized, good and bad experiences have been analyzed, know how has been gathered: industry has now developed a number of best requirements engineering practices. But does everyone have the same best practices? Do we need the same approach to elicit requirements, document, negotiate, validate, formalize or trace requirements when you integrate an ERP, when you develop a car, an air traffic control system, an aircraft or a satellite, or when you study the ergonomics of a mobile phone? This paper gathers experienced requirements engineers from various industries, to try learn a few new lessons on the adequacy of various best practices to various industrial sectors.