论文标题
翻新需求工程：塑造要求工程作为职业的第一个想法
Renovating Requirements Engineering: First Thoughts to Shape Requirements Engineering as a Profession
论文作者
论文摘要
传统软件系统通常包含使用它们的组织的重要数据，因此应定期维护。理想情况下，组织应依靠需求工程师来了解和管理利益相关者需求和系统限制的变化。但是，由于时间和成本压力，并且非常关注实施，组织通常会选择放弃需求工程师，而是专注于临时错误修复和维护。该立场论文讨论了工程师可能会从其他类似角色中学到哪些要求的要求，这对于遗产系统的发展至关重要。特别是，我们比较了需求工程师（根据IREB），建筑师（根据德国法规）和产品所有者的角色（根据“ Scrum guide”）。我们讨论沿着四个维度的重叠：责任，自我陶瓷，核心活动和人工制品。最后，我们从这些相关领域中吸引了见解，以促进需求工程师作为杰出职业的概念。
Legacy software systems typically include vital data for organizations that use them and should thus to be regularly maintained. Ideally, organizations should rely on Requirements Engineers to understand and manage changes of stakeholder needs and system constraints. However, due to time and cost pressure, and with a heavy focus on implementation, organizations often choose to forgo Requirements Engineers and rather focus on ad-hoc bug fixing and maintenance. This position paper discusses what Requirements Engineers could possibly learn from other similar roles to become crucial for the evolution of legacy systems. Particularly, we compare the roles of Requirements Engineers (according to IREB), Building Architects (according to the German regulations), and Product Owners (according to "The Scrum-Guide"). We discuss overlaps along four dimensions: liability, self-portrayal, core activities, and artifacts. Finally we draw insights from these related fields to foster the concept of a Requirements Engineer as a distinguished profession.
