3 ms·

Here's the main problem with this: Where are the requirements? The COBOL doesn't have automated tests. When you port the COBOL to Java (whether automated or ma

Here's the main problem with this: Where are the requirements? The COBOL doesn't have automated tests. When you port the COBOL to Java (whether automated or manually) you aren't asking "where are the original requirements?". Contrast this with a "re-write". When you do a re-write you have to go back to the customer and whatever documentation you can find and figure out and re-document what the system should do. This can be far removed from what the system did in its original design docs, and can differ still from what people believe. This step of codifying tacit knowledge of the behaviour is important in the evolution of systems.

dragonwriter 7y ago
> The COBOL doesn't have automated tests. When you port the COBOL to Java (whether automated or manually) you aren't asking "where are the original requirements?". You should be asking where is the current documentation of the system specs, and in some cases you might even get something reasonably current and complete when you ask that, depending on how to use the change management process has been. > When you do a re-write you have to go back to the customer and whatever original documentation you have lying around and you have to figure out and document what the system does. Both what it does and (and this is where the customer is involved) what it is currently supposed to do.
- ryanmarsh 7y ago
  you might even get something reasonably current and complete when you ask that LOL depending on how to use the change management process has been ROFLOL what it is currently supposed to do I died