Feature-Oriented Software Engineering

软件系统通常被认为是其组成特征，其中每个特征是可选的或递增的功能单元(例如，撤消、字数统计和跟踪变化是字处理软件中的特征)。软件开发人员使用功能作为将他们的工作分解为可以增量、并行或由第三方供应商执行的任务的标准。面向功能的软件工程使软件系统的增量开发和快速演化成为可能。缺点是，集成看似正交的功能可能会导致功能交互，其中一个功能意外地影响另一个功能的行为(例如，冲突的操作、紧急行为、违反的假设)。交互是功能丰富的软件产品中常见的问题。一个值得注意的例子是：在两起波音737 Max飞机坠毁事件中，输入传感器故障导致多个特征交互，其中臭名昭著的MCAS特征压倒了与飞机俯仰相关的其他特征(包括飞行员控制的特征)，迫使飞机俯冲。为了安全起见，软件工程师需要管理功能集成在一起时的行为。 这项建议调查了两种研究途径，以解决功能交互问题的不同方面。第一个重点是建立精确的系统范围分析，以检测大型功能丰富的软件系统中的功能交互。新的进步将被分析(1)检查实际的软件而不是模型或测试结果(2)在它们检测到的交互类型中是全面的，(3)规模到大型软件产品，以及(4)足够精确。 第二种研究途径追求更全面的方法来管理功能交互，方法是通过功能插入的软件体系结构。该体系结构协调和约束功能如何执行和通信，从而避免或解决某些类别的交互。管理交互的架构解决方案有可能确保功能的安全集成，从而减少工程师必须检测和解决的剩余交互的数量。 其结果将是在面向功能的设计和分析方面接受培训的技术和HQP，实现面向功能的软件工程一直承诺的开发人员生产率和产品质量的改进。

A software system is often thought of in terms of its constituent features, where each feature is an optional or incremental unit of functionality (e.g., undo, word count, and track changes are features in word processing software). Software developers use features as a criterion for decomposing their work into tasks that can be performed incrementally, in parallel, or by third-party vendors. Feature-oriented software engineering enables incremental development and rapid evolution of software systems. The downside is that integrating seemingly orthogonal features can result in feature interactions where one feature unexpectedly affects the behaviour of another (e.g., conflicting actions, emergent behaviours, violated assumptions). Interactions are common problems in feature-rich software products. As a notable example: in both of the Boeing 737 MAX aircraft crashes, a faulty input sensor led to multiple feature interactions in which the infamous MCAS feature overpowered other features related to the aircraft's pitch (including pilot-controlled features) and forced the aircraft into a nose dive. To be safe, software engineers need to manage how features behave when integrated together. This proposal investigates two avenues of research that address different aspects of the Feature Interaction Problem. The first focuses on establishing a precise system-wide analysis to detect feature interactions in large feature-rich software systems. Novel advancements will be analyses that (1) examine actual software rather than models or test results (2) are comprehensive in the types of interactions they detect, (3) scale to large software products, and (4) are adequately precise. The second research avenue pursues a more holistic approach to manage feature interactions, by means of a software architecture that the features plug into. The architecture coordinates and constrains how features can execute and communicate, thereby avoiding or resolving certain classes of interactions. An architectural solution to managing interactions has the potential of ensuring safe integration of features, thereby reducing the number of residual interactions that the engineer must detect and resolve. The result will be technologies and HQP trained in feature-oriented designs and analyses that realize the improvements in developer productivity and product quality that feature-oriented software engineering has always promised.