Show simple item record

dc.contributor.authorMichael, James Bret
dc.contributor.authorDrusinsky, Doron
dc.contributor.authorOtani, Thomas W.
dc.contributor.authorShing, Man-Tak
dc.date.accessioned2017-12-21T22:38:49Z
dc.date.available2017-12-21T22:38:49Z
dc.date.issued2011
dc.identifier.citationJ.B. Michael, D. Drusinsky, T.W. Otani, M.-T. Shing, " Verification and validation for trustworthy software systems," IEEE Software, v.28, no.6, (November-Decemeber 2011), pp. 86-92.en_US
dc.identifier.urihttp://hdl.handle.net/10945/56505
dc.descriptionThe article of record as published may be found at http://dx.doi.org/10.1109/MS.2011.151en_US
dc.description.abstractThe close interaction between high-integrity systems and their operating environments places a high priority on understanding and satisfying both functional requirements (what the software must do) and safety requirements (what the system must not do). However, traditional validation methods that test the delivered system’s behavior against customer expectations are ineffective (and too late) to assure requirement correctness. Validating requirements early in the system life cycle is increasingly important to organizations that implement capability-based acquisition. For instance, government organizations such as the US Department of Defense (DoD) now play the role of smart buyers whose job is to acquire a set of capabilities. This makes the task of assuring that the system developers correctly translate capabilities into system specifications even more vital. Without such assurance, the DoD can’t reasonably expect successful development of trustworthy software-intensive systems. The US Food and Drug Administration (FDA), on the other hand, plays the role of regulator with the responsibility of approving public use of, say, safety critical medical devices and investigating the cause of mishaps involving these devices. The FDA must ensure that the device behaves as the manufacturer specifies and that the manufacturer acts with due diligence in assessing its products’ trustworthiness - without source code or other detailed information about the systems’ implementation. These examples highlight the need for the continuous and proactive verification and validation (V&V) of complex and safety-critical software systems. This article presents a continuous, computer-aided process that uses statechart assertions, runtime execution monitoring, and scenario-based testing to specify and validate complex system requirements.en_US
dc.format.extent8 p.en_US
dc.publisherIEEEen_US
dc.rightsThis publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States.en_US
dc.titleVerification and validation for trustworthy software systemsen_US
dc.typeArticleen_US
dc.contributor.corporateNaval Postgraduate School (U.S.)en_US
dc.contributor.departmentElectrical and Computer Engineeringen_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record