Abstract
Test requirements, which are generally collected in multiple disparate formats throughout the life cycle of an electronic product, could be used in various applications that reduce test and development cycle times and increase the confidence in the final test program. Unfortunately, test requirements are seldom captured in a consistent format that may be processed by a computer, thus eliminating the possibility of using such requirements in an engineering application. Additionally, such an approach disallows test requirements captured in one segment of the product life cycle to be reused in subsequent life cycle stages. This paper describes a model-based methodology, specifically the Test Requirements Model (TeRM), which can be shown to facilitate the transfer of test-related product information between various stages of the life cycle. This transportability, in conjunction with an exchange format that can be processed by a computer, permits test requirement information to support value-added applications in the engineering process throughout the life cycle of a product.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.