Abstract
Applicability of formal methods in requirement capturing and analysis is determined to a great extent by how well the respective formalism matches the adopted engineering practice. Conventional notation of mathematical logic obviously has little chance to succeed as such formalization tool. A technology based on formalism of “basic protocols” derived from the modeling languages UML/MSC which became a de facto standard in the current engineering practice is described in this paper. It allows for automated test generation for software which guarantees 100% coverage of thus formalized requirements. Suite optimization w.r.t. various criteria borrowed from practice is discussed, as well as potential directions for further research.
Sign-in/Register to access full text options 
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 callDisclaimer: 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.
