Question

Closed. This question is seeking recommendations for books, tools, software libraries, and more. It does not meet Stack Overflow guidelines. It is not currently accepting answers.

我们不准许对书籍、工具、软件图书馆以及更多的图书馆征求建议的问题。你可以ed问这个问题,以便用事实和引言回答。

Closed 3 years ago.

Improve this question

我是新团队的一部分,他们试图从遗产代码基(也在 Java撰写)中开发一个新的 Java软件系统,该基数转至核心。出于公司的政治原因,我们可以 t笑旧的 Java,从新鲜开始。改观等于承认,他们花了两年时间开发的制度是完整的。这将导致在团队顶部(即发展管理员、项目经理、建筑师等)上进行滚动。因此,一支非常强烈的自我保护意识在团队的顶部中扎根,这意味着任何在改弦更张的思想都被抛弃。

This has lead to ask the following question: What would you say are the key processes, tools and software development techniques, a team would need to implement in order to successfully re-engineer/refactor a very rotten legacy code base into a good stable system? This must surely be possible. Are there any good books/websites on the matter?
Thanks

Answer 1

define a clear plan of what you re trying to achieve and where you re going
write tests for as much new and old code as you can to ensure you re preserving behaviour and creating a good test suite going forward
refactor small chunks at a time, it adds up eventually
work with discrete vertical slices of functionality if you can to prevent breaking changes cascading through the code
make sure you build regularly
use source control

基本上,从一开始就应该采用的所有公认的良好做法;

Answer 2

首先是古典:

Automated builds & deploy manager Unit tests Fitness tests

一旦有了这些事情,你就非常愿意重新思考和重写整个东西,就很容易要求这种非司法性的人,而不要怀疑你们的再意愿。

我以经验之声发言。

Answer 3

确实,我从

"There are some fundamental software engineering principles that every project should adopt, regardless of the particular methodology to which you might subscribe. They are:

Version control

Issue tracking

Automated, self-contained builds

Automated testing"

这可能有助于你走向方向,并为你不可原谅的终局工作建立一个起点。

Answer 4

我已成功利用 Enterprise/61/1 (EA)扭转工程大型源代码基础。

如果你不掌握目前状况的良好模式,这一工具就能够让你深刻了解当前的状况。它还提供了一个框架,以讨论哪些部分必须改变、哪些部分可以获救、哪些部分不需要触及。

Answer 5

Eclipse - it s refactoring capabilities are very powerful
Patience
Skills. It appears to me that almost every legacy system is bloated , rubbish , rotten or crap . While this is generally true, the non-legacy applications are the same, because the developers writing them are not skilled enough. So have in mind, that if you want to achieve something more than yet-another-rotten system, you have to be very careful with the team skills.

Answer 6

你也许最好把这一想法简单地视为一个新项目,而是以现有的法典为基础。 • 与有关各方合作,准确说明该制度的错误: 构造很差,设计不好,编码不好,不符合要求等(或以上所有)。视需要修改碎片的构造和设计,并制定一项计划,对碎片进行再设计/重造,使之达到良好的工作秩序。

您适用于新项目的所有最佳做法都在此明确适用:源源控制、自动单位和功能测试、持续整合、夜间建设、同行审查等。

友情链接