Phoenix of Hamble
Well-Known Member
again, for a major system, poor process...these are the sort of problems that a decent analyst captures upfront, and ensures that system developers code out problems, not code 'em in!.... they would make any pre-requisite data entry a compulsory, and prevent manual entry of data if a risk of this kind of thing exists... or perhaps ensure than any manual entry is chcked for uniqueness before final being committed to the permanent record.....
This is what I do all day every day.... there is no excuse for the situation they found themselves in... just very poor management of systems design and roll out.
I agree that many teams are all to often trying to make a system fit a process rather than vice versa... but these errors are more basic than that.
This is what I do all day every day.... there is no excuse for the situation they found themselves in... just very poor management of systems design and roll out.
I agree that many teams are all to often trying to make a system fit a process rather than vice versa... but these errors are more basic than that.