Suppose we’re looking at a system rewrite where the stakeholders have none of the original engineering documentation. (This isn't surprising; documentation becomes obsolete—or even misleading—as the system changes, and corresponding docs don't get updated.) What can we do? Here are some tactics to use—and risks to anticipate—when testing a system rewrite.
There are many reasons to consider modernizing your legacy software. But when doing so, it’s important to remember your customers who regularly use your product and to take their preferences, habits, and needs into consideration. Here are some practical tips to boost your chances of a smoother transition.