Abstract
The paper focuses on a methodological approach to identifying software in special software for systems of critical applications. The approach relies on the analysis of the subject area associated with the functioning of such systems. The term ‘software bugs’ is local and depends on the system into which they are embedded. In this regard, the methodological approach to identifying software bugs is illustrated by an automated system for preparing data for aircraft flights. By software bugs, we mean malicious software that can affect the algorithms for the functioning of the system, disrupting the normal mode of its operation and causing significant damage to the goals of the system. To find where software bugs are likely to be embedded, we specified actions which consist in understanding the features of assessing the quality of each of the main elements of the system and the essence of software bugs, with account for the features of the automated data preparation system; describing the system and its specifics; determining the most likely place for embedding software bugs and conditions for their initialization.
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.
