Abstract

Software validation aims to ensure that a particular software product fulfils its intended purpose, and needs to be performed against both software requirement as well as its implementation (i.e. product). However, for diagnostic software (i.e. a diagnoser) performing online diagnosis against certain fault models and reports diagnosis decision, the underlying fault models are usually not explicitly specified, neither by formal language nor by descriptive language. The lack of formal representation of fault models leaves the intended purpose of the diagnostic software vague, making its validation difficult. To address this issue, the authors propose various model-based techniques that can generate concrete examples of the diagnoser's key properties. Such examples are represented in an intuitive and possibly visualised way, facilitating the designers/users to approve or disapprove the conformance of the diagnoser to the intended purpose. The proposed techniques work for validation of both the requirement and implementation that can be modelled as finite state machine, and are illustrated through applications on vehicle on-board diagnostic requirement.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

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.