Browse by Tags

• acceptance test

• Why Acceptance Tests Matter

  While consulting on a migration project I was refactoring the way to load country reference data when I noticed some oddities in the business rules for formatting phone and fax numbers. I had changed from loading based on hard-coded country codes to using... Posted okt 06 2006, 11:30 by Martin Jul with | with 1 comment(s) Filed under: mainframe migration, acceptance test

• Bug-by-Bug Compatibility

  When you are porting an old system you will often be confronted with the pragmatic decision to be bug-by-bug compatible with the old system at the integration points, since it is sometimes not feasible to fix the bugs in the clients to the system. On... Posted sep 29 2006, 11:30 by Martin Jul with | with 1 comment(s) Filed under: mainframe migration

• Don't Port the Dead Code

  Once upon a time when Gildenpfennig and I were porting a mainframe to .NET we received specifications for one of the integration points - to another mainframe that would still be running. So we set forth and started implementing. More and more "protocol"... Posted sep 22 2006, 11:30 by Martin Jul with | with 2 comment(s) Filed under: mainframe migration

• Don't Propagate a Bad Decision

  If you get data in a weird format, don't let that mistake propagate into your app. For example, I once worked on a legacy system that received data from an external source in a CSV file. Dates in this file were, split into three columns: day, month... Posted sep 15 2006, 11:30 by Martin Gildenpfennig with | with 1 comment(s) Filed under: mainframe migration

• Notes on Mainframe Migration

  Migration projects are often initiated with the objective to save on operational cost. And due to the ridiculous price of keeping a mainframe going the business case is often very attractive. The savings from this alone leads to the decision to do a one... Posted sep 12 2006, 11:58 by Martin Jul with | with 2 comment(s) Filed under: mainframe migration