Authors : Nakod Niharika

Volume/Issue : Volume 10 - 2025, Issue 7 - July

Google Scholar : https://tinyurl.com/y74bdxt2

DOI : https://doi.org/10.38124/ijisrt/25jul468

Note : A published paper may take 4-5 working days from the publication date to appear in PlumX Metrics, Semantic Scholar, and ResearchGate.

Note : Google Scholar may take 30 to 40 days to display the article.

Abstract : In areas where the failure of software entails disastrous consequences, like in the aerospace sector, automotive industry, medical sector and industrial control systems- software production is of primary importance.(10) This paper focuses on the importance of LDRA Tool Suite to attain high degree of software quality and strong security as well as demonstrate how, at a comparatively early stage of the development lifecycle, the entire potential of the LDRA suite may be utilized to uncover hidden flaws, coding standards, and possible security vulnerabilities in the code analysis with regard to the comprehensive testing of software by validation of its unit, integration and system level integration,(11) as well as the high level code coverage (e.g., MC/DC, statement and branch) which is of high importance when certification objectives are to be achieved.(12) This paper illustrates how LDRA tool Suite is useful in designing traceable and verifiable tracks to provide high-quality software reliability to face security risk, meet industry-specific safety or security standards and finally lead to predictable actions within any critical embedded systems.(13)

Keywords : Coding Standards, Security Vulnerabilities, Quality Metrics, Cyclomatic Complexity, LCSAJ Metrics, Equivalence Class Testing, Boundary Value Testing

References :

1. Hatton, L. (1994). Safer C: Developing Software for Safety-Critical Systems. McGraw-Hill.
2. Janssen, M., Von Knethen, A., & Von Knethen, B. (2022). Continuous Integration and Delivery: A Practical Guide for Software Teams. Springer.
3. Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach. McGraw-Hill Education.
4. Schneier, B. (2015). Data and Goliath: The Hidden Battles to Collect Your Data and Control Your World. W. W. Norton & Company.
5. Seacord, R. C., Long, M., & Mogul, J. C. (2013). The CERT C Coding Standard: 98 Rules for Developing Safe, Reliable, and Secure Systems. Addison-Wesley Professional.
6. Leveson, N. (2011). Engineering a Safer World: Systems Thinking Applied to Safety. MIT Press
7. McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, SE-2(4),308–320. https://doi.org/10.1109/TSE.1976.233837
8. LDRA.(2023).LDRA Test Suite and TBextreme Overview. https://www.ldra.com
9. Khurana, S., & Sharma, R. (2012). Software Testing Techniques and Tools. International Journal of Computer Science and Mobile Computing, 1(1), 47-54.
10. ISO 26262: Road Vehicles – Functional Safety. International Organization for Standardization, 2018.
11. DO-178C: Software Considerations in Airborne Systems and Equipment Certification. RTCA Inc., 2011.
12. MISRA C:2012 Guidelines for the Use of the C Language in Critical Systems. Motor Industry Software Reliability Association, 2012.

13. LDRA. (2020). LDRA Tool Suite for Safety-Critical Software Development. https://www.ldra.com