Quote:
Originally Posted by Terisa de morgan
The first part is the real problem. The system works as designed, but nobody says that the design is right, especially when you're changing a system and the new one perhaps is "very cool software"but it is worse designed than the previous one. You don't know how fast you are tired or saying to the IT guy that yes, it works as designed, but somebody has designed with his or her ass. And hey, I'm in both fields, as I design software but I use it. I'm very tired of those nice "features" which are a crappy design done by somebody who never has used the software.
|
So, I work as a consultant in software testing, in fact, I'm a lead assessor for an international testing framework. One of the things I'm constantly having to tell people is that testing isn't just debugging; it's verification that the software conforms to the design and, even more importantly, validation of the original design to ensure it's fit for purpose. We advise that design is subjected to static testing to ensure its suitability and that a user acceptance test level is carried out later to make sure that the software functions as its users want/need it to (as per the validated design).
Sounds like this didn't happen in your example. Put them in touch with me, I'll sort them out
