Tech, let me get this straight. You've never been to Charlotte, never called and talked to anyone at ALYD, never talked to any of ALYD's clients-- and you're making claims about ALYD's Smartcode technology??? Did your T/A tool tell you this? Are you another Randy G?
You asked:
Does ALYD have a way of telling a client that they don't have all his code, or do they just convert what they are given and send it back ?
Remediation (the part where the code is actually fixed) is only one part of the whole process. ALYD performs all sorts of tests on the code well before they even get to the remediation phase. If the code ain't complete, they send it back. With companies as large as McDonnel Douglas, for example, it's quite possible that copybooks for a given chuck of code are kept in different parts of the country. So, yes, incomplete code is a common problem and any Y2K company that does not check for code completeness is playing with fire.
You are also missing one other very important phase: code testing. ALYD checks to make sure the code sent to them actually works before they even begin to remediate it. After all, if it didn't work before, it ain't gonna work after.
After remediation, they run the code through another battery of other tests, again, for quality assurance. This all happens before the actual testing phase-- where the code is run as if in production. It's this phase where the Compuware alliance kicks in, although, again, I left out some intermediary things that both companies do -- together -- to assure the testing phase goes smoothly.
There are other phases I could discuss, but if you really care about all this, from what I recall, ALYD has a white paper on their technique on their web site.
I don't mind mind you asking "innocent" questions, but please don't try to imply through guessing the answers that you know something alarming about ALYD's technology the rest of us don't.
- Jeff |
