Phần mềm-Ứng dụng

Testing tools should be introduced at a maturity level appropriate for their use. Each tool purchase should be evaluated individually. Firth and co-authors have proposed a set of six criteria useful for the acquisition of any type of software engineering tool [1]. These criteria, plus two addi tional criteria suggested by this author, are shown in Figure 14.1 and are summarized below. The summary includes appropriate questions to ask when evaluating a tool according to each criterion. 1. Ease of Use. Is the tool easy to learn? Is its behavior predictable? Is there meaningful feedback for the user? Does it have adequate error handling capabilities? Is the interface compatible with other tools already existing in the organization? 2. Power. Does it have many useful features? Do the commands allow the user to achieve their goals? Does it “understand” the objects itmanipulates? Does the tool operate at different levels of abstraction? Does it perform validation checks on objects or structures? 3. Robustness. Is the tool reliable? Does it recover from failureswithout major loss of information? Can the tool evolve and retain compati bility between old and new versions?