Internet Product reconfiguration

The loss of old system personnel, the system's business rules, the original requirements who are not clear, the requirements of documents, use documents, architecture documents are extremely scarce, become a bottomless pit, maintainability is very poor.

The old system more and more complex, latent rules too much, originally modify a small demand, inadvertently get online after the impact of a pile of users

The business architecture, http://www.aliyun.com/zixun/aggregation/9942.html "> Technology architecture of legacy systems cannot meet new business model needs

The old system performance can not meet the needs of the rapid development of the company's business

The product lifecycle of the old system is over, requiring an extended life cycle

Wait a minute

There is no standard answer to refactoring existing products or to recreate a new set of systems. Technical personnel are inclined to redo the new system, and are inclined to overestimate their own management capabilities, architectural design capabilities, we will be committed to the perfect structure, perfect product planning. But if you don't solve fundamental management problems, refactoring or re-doing is the same. These management issues include product planning capabilities, business architecture capabilities, project management capabilities, architectural management capabilities, architectural design capabilities, and so on.

In the case of the management ability has not improved, how to ensure that the new system does not fall into the old system "new system, commitment to perfect architecture-> management imbalance, system maintenance into chaos-> to redo the new system" the same fate. Good architecture is managed, not designed.

The first difficulty in product reconfiguration is the reverse engineering process phase, which must be clear about the legacy status of the existing system. For an online operating system, both refactoring and redo must go through this process

The second difficulty in product refactoring is the process of migrating old systems to refactoring systems. The biggest challenge is how to achieve grayscale switching without impacting existing customers. Both refactoring and redo must go through this process

3. Thoughts on product reconfiguration 4, reference

The Product Re architecture

Using RUP to reverse engineer legacy systems

The Art of software architecture

Source: http://www.yeeach.com/