Having a code review with them is always useful - knowing why and how they did the things they did is vital to future maintenance Documentation, obviously, and test cases are always useful, otherwise you'll end up having to implement your own. If they can't provide either, you should be worried :-).
Having a code review with them is always useful - knowing why and how they did the things they did is vital to future maintenance. Documentation, obviously, and test cases are always useful, otherwise you'll end up having to implement your own. If they can't provide either, you should be worried :-).
Before contract with software vendor expires, we need to secure existing applications they developed and be ready to anticipate problems without any help and support from the software vendor. Besides the source code, what should I know/ask/get from software vendor? (Just in case you want to know why we decide to stop the contract, because we don't trust them anymore.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.