Is your test software the goose that has laid its golden eggs or is your software misbehaving? Does it run amok? The purpose of this article is to provide an understanding of the software validation requirements, the validation rationale, and suggest independent tools that will allow you to develop your own test software validation process.
This article explains the development process of a proficiency testing programme that is suitable for electrical and mechanical safety tests. The process for testing the homogeneity and stability of specimens is also discussed.
This article will summarize the major changes of the new revision of ISO/IEC 17025-2005, present the new outline of the standard and will discuss the new concept of a “risk-based” approach of implementing requirements.
An EMC test engineer’s primary responsibility includes creating test plans, procedures, analyzing test data, generating test reports, and mitigating noncompliance challenges. Many times the EMC engineer must assume the role of a software test engineer and create test programs necessary to meet the project objectives.
Manufacturers and distributors of electronic and electrical devices are required to meet various Product Safety standards established by the United States, Canada, European Union, and various global agencies. Today manufacturers have multiple options for testing their product to various North American Standards through Nationally Recognized Testing Laboratories (NRTLs), as well as independent value added laboratories that have approvals for NRTL testing under a variety of programs. Good independent labs must be assessed to ISO 17025 for testing laboratories, similar to those requirements found under ISO 9000 requirements for manufacturers.