Information Technology Reference
In-Depth Information
is having an accurate history of errors, faults, and defects associated with software
failures. The project risk explained here is in terms of an appraisal of risk relative to
software defects and enhancements (Paradkar, 2000).
The ISO 9000 series is used for software quality management. We will concentrate
on the verification and validation sections of ISO 9001. Table 19.5 14 shows the
differences between verification and validation with the ISO 9001 standard.
19.9
CONCLUSION
Many V&V methods and testing strategies were presented in this chapter. The Petri
Net method seems to provide practical and effective means for management and
maintenance of the domain knowledge system. The hybrid approach can boost the
performance and capacity of an SAT/BDD-based symbolic model checking. More-
over, this methodology enables the verification engineer to have much more control
over the verification process, facilitating a better debugging environment.
Testing strategies has a general role to uncover software errors and maintain
software quality. Testing begins at the module level and works outward toward
the integration of the entire system. Different testing techniques are required at
different stages of the software life cycle. The most successful technique would be
the traditional manual techniques because they are applied to all stages in the life
cycle. The cost of finding software errors increases by moving forward in the software
development; so for example, when the tester finds an error at an earlier stage, such as
the requirements phase, it will be much less costly than finding it at the deployment
phase.
Testing strategy has certain problems that might delay or stand against completing
the software as assumed. Simulation has a major cost related to customizing it to the
verification process, whereas the proof of correctness sometimes has the inability of
proving certain practice. Moreover, with the technology advancement, many problems
occur for different software environments that software engineers have to know how
to deal with to save time and money.
Verification and validation methods verify the software quality and testing the
software assures that, whereas V&V standards are available for use to clarify and
simplify rules of using any V&V method or any testing strategy.
REFERENCES
Bergeron, J (2003), Writing Testbenches: Functional Verification of HDL Model , 2nd ed;
Kluwer Academic, Boston, MA.
Civera, P. Conte, G. Del Corso, D. and Maddaleno, F. (1987), “Petri net models for the descrip-
tion and verification of parallel bus protocol,” Computer Hardware Description Languages
and their Applications , M.R. Barbacci and C.J. Koomen (Eds.), Elsevier, Amsterdam, The
Netherlands, pp. 309-326.
14 http://www.platinumregistration.com/kbfiles/VAL VER-ISO9k CMMI.pdf.
 
Search WWH ::




Custom Search