首页> 外文会议>International Workshop on Software Measurement;International Conference on Software Process and Product Measurement >Identifying and Managing Complex Modules in Executable Software Design Models-Empirical Assessment of a Large Telecom Software Product
【24h】

Identifying and Managing Complex Modules in Executable Software Design Models-Empirical Assessment of a Large Telecom Software Product

机译:识别和管理可执行软件设计模型中的复杂模块-大型电信软件产品的经验评估

获取原文

摘要

Using design models instead of executable code has shown itself to be an efficient way of increasing abstraction level of software development. However, applying established code-based software engineering methods to design models can be a challenge - due to different abstraction levels, the same metrics as for code are not applicable for the design models. One of practical challenges in using metrics at the model level is applying complexity-prediction formulas developed using code-based metrics to design models. The existing formulas do not apply as they do not take into consideration the behavior part of the models - e.g. State charts. In this paper we address this challenge by conducting a case study at one of the large telecom products at Ericsson with the goal to identify which metrics can predict complex, hard to understand and hard to maintain software modules based on their design models. We use both statistical methods like regression to build prediction formulas and qualitative interviews to codify expert designers' perception of which software modules are complex. The results of this case study show that such measures as the number of non-self-transitions, transition per states or state depth can be combined in order to identify software units that are perceived as complex by expert designers. Our conclusion is that these metrics can be used in other companies to predict complex modules, but the coefficients should be recalculated per product to increase the prediction accuracy.
机译:使用设计模型代替可执行代码已显示出它本身是提高软件开发抽象水平的有效方法。但是,将已建立的基于代码的软件工程方法应用于设计模型可能是一个挑战-由于不同的抽象级别,与代码相同的度量不适用于设计模型。在模型级别使用度量的实际挑战之一是将使用基于代码的度量开发的复杂度预测公式应用于设计模型。现有公式不适用,因为它们未考虑模型的行为部分-例如状态图。在本文中,我们通过在爱立信的一种大型电信产品上进行案例研究来应对这一挑战,目标是确定哪些指标可以根据其设计模型来预测复杂,难以理解和难以维护的软件模块。我们使用两种统计方法(例如回归法)来构建预测公式,并使用定性访谈来整理专家设计人员对哪些软件模块是复杂的看法。该案例研究的结果表明,可以结合使用非自跃迁数量,每个状态的跃迁或状态深度之类的度量,以识别专家设计人员认为复杂的软件单元。我们的结论是,这些指标可以在其他公司中用于预测复杂的模块,但是应该针对每种产品重新计算系数以提高预测的准确性。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号