首页> 外文会议>25th annual ACM conference on object oriented programming, systems, languages and applications 2010 >Stop the Software Architecture Erosion: Building better software systems
【24h】

Stop the Software Architecture Erosion: Building better software systems

机译:阻止软件架构侵蚀:构建更好的软件系统

获取原文
获取原文并翻译 | 示例

摘要

In lots of software projects unfortunately an architectural erosion happens over time. Modules which were independent, become interconnected, plugins finally depend on each other, and in general the architecture gets violated more and more. In this paper we will discuss how to avoid such architecture- and design-erosion and how an already eroded system can be fixed again. We will look at three different level of static analysis and examine architectural analysis in detail. Also typical use cases for architectural analysis are examined, followed by a collection of requirements for powerful tool support. The eclipse platform serves as case study and we look if, and how far architectural erosion happened there and if it can be fixed. Finally we discuss pros and cons of architectural analysis and conclude with an out view.
机译:不幸的是,随着时间的流逝,在许多软件项目中都会发生体系结构侵蚀。独立的模块相互连接,插件最终相互依赖,总的来说,架构受到越来越多的侵犯。在本文中,我们将讨论如何避免这种体系结构和设计侵蚀,以及如何重新修复已经侵蚀的系统。我们将研究静态分析的三个不同级别,并详细研究架构分析。还检查了体系结构分析的典型用例,然后收集了强大的工具支持的一系列要求。蚀平台用作案例研究,我们研究是否,以及那里发生的建筑侵蚀程度以及是否可以修复。最后,我们讨论了体系结构分析的利弊,并给出了结论。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号