Modelling and Analysis of Feature-Oriented Software

面向特征的软件建模与分析

• 批准号: 155243-2012
• 负责人: Atlee, Joanne
• 金额: $ 2.48万
• 依托单位: University of Waterloo
• 依托单位国家: 加拿大
• 项目类别: Discovery Grants Program - Individual
• 财政年份: 2013
• 资助国家: 加拿大
• 起止时间: 2013-01-01 至 2014-12-31
• 项目状态: 已结题
• 来源: https://www.nserc-crsng.gc.ca/ase-oro/Details-Detailles_eng.asp?id=522585
• 关键词: Modelling; Analysis; Feature; Oriented; Software

Software systems are growing in size and complexity. The "scale" of large-scale systems no longer refers simply to large codebases but also to extreme variability, as characterized by features. Features are particularly relevant in software product lines, in which a family of related software products (e.g., smart phones, automotive software) shares a common set of mandatory features and products are differentiated by their variable (optional or alternative). When deriving a product from a selection of features, software developers must consider how the features interact. Some interactions are planned, some are innocuous, and others are harmful. For example, the software controllers for the braking features on the 2010 Toyota Prius interacted badly, reducing drivers' ability to brake and leading to 62 reported crashes and 12 injuries. To be safe, software developers analyze the consequences of all possible feature interactions, in order to find and fix the bad interactions. The Feature Interaction Problem is that the number of interactions to consider is exponential in the number of features. As a result, a software team finds that its work in developing new features is dominated by the tasks to detect, analyze, and verify interactions. A second problem is that software developers do not realize the full potential of feature-oriented development because verification is typically performed on derived products and it is too costly to verify all of the possible products. Instead, a small fraction of products are derived, verified and offered to customers.

软件系统在规模和复杂性上都在不断增长。大规模系统的“规模”不再简单地指大型代码库，还指以特征为特征的极端可变性。功能在软件产品线中特别相关，其中一系列相关软件产品(例如，智能手机、汽车软件)共享一组共同的强制功能，并且产品按其变量(可选或替代)进行区分。在从选定的功能派生产品时，软件开发人员必须考虑这些功能是如何交互的。有些互动是有计划的，有些是无害的，有些是有害的。例如，2010年丰田普锐斯刹车功能的软件控制器交互作用很差，降低了司机的刹车能力，导致62起撞车事故和12人受伤。为了安全起见，软件开发人员分析所有可能的功能交互的后果，以便发现并修复不良交互。功能交互问题是要考虑的交互数量与功能数量呈指数关系。因此，软件团队发现其开发新功能的工作主要由检测、分析和验证交互的任务主导。第二个问题是，软件开发人员没有意识到面向功能的开发的全部潜力，因为验证通常是在派生产品上执行的，并且验证所有可能的产品的成本太高。相反，一小部分产品被派生、验证并提供给客户。