Copyright © 2025 Authors retain the copyright of this article. This article is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

@article{167208,
        author = {SHRUTI KHATRI},
        title = {CATERING TO END -TO – END REQUIREMENT TRACEABILITY NEEDS IN RAIL SIGNALLING SYSTEMS},
        journal = {International Journal of Innovative Research in Technology},
        year = {2024},
        volume = {11},
        number = {3},
        pages = {616-622},
        issn = {2349-6002},
        url = {https://ijirt.org/article?manuscript=167208},
        abstract = {Requirements remain at the heart of all software development process models and not only do they help outline the system capabilities , but also provide the foresight for how the project would shape and how the outcome products may look like. The embodiment of requirements at various stages of system and software development help engineers understand the system to be developed , and also enables them to be more disciplined towards each and every phase of development and test cycles. This paper talks about how requirements can be traced from the inception of system definition down to the last stage of product development and delivery cycles. Requirement traceability has been a concern and a major dimensional hole in current technological practices. The need therefore is to understand the growing complexity and magna-city of development projects wherein rail vertical is also a significant player and impart standard process conformance  through requirement traceability and compliance. The paper discusses how better traceability techniques can be applied to Rail Signaling Systems for effective impact analysis, requirement control and change management.},
        keywords = {end-to-end-traceability, signaling systems , rail control ,automatic train protection ,traceability management, requirement traceability, systems engineering},
        month = {August},
        }