{"title":"Requirement Traceability in Software Development Process: An Empirical Approach","authors":"S. Sengupta, A. Kanjilal, S. Bhattacharya","doi":"10.1109/RSP.2008.14","DOIUrl":null,"url":null,"abstract":"One of the biggest challenges in the software industry is to ensure that a software product meets all user specifications. In this paper, we propose to establish traceability of functional requirements expressed in a SRS document among different UML diagrams that are used in requirement analysis and design phases. We have used Z notation as the formal language for representing the SRS and design artifacts and this formal notation is used to automatically establish trace paths based on certain rules. We present an implementation methodology based on XML for development of a prototype. A snapshot of some of the results based on a case study has been shown for illustration of our approach. Our approach will help in identifying missing requirements or incomplete requirement coverage as well highlight the impact points for effective change management of requirements.","PeriodicalId":436363,"journal":{"name":"2008 The 19th IEEE/IFIP International Symposium on Rapid System Prototyping","volume":"35 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"17","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2008 The 19th IEEE/IFIP International Symposium on Rapid System Prototyping","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RSP.2008.14","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 17
Abstract
One of the biggest challenges in the software industry is to ensure that a software product meets all user specifications. In this paper, we propose to establish traceability of functional requirements expressed in a SRS document among different UML diagrams that are used in requirement analysis and design phases. We have used Z notation as the formal language for representing the SRS and design artifacts and this formal notation is used to automatically establish trace paths based on certain rules. We present an implementation methodology based on XML for development of a prototype. A snapshot of some of the results based on a case study has been shown for illustration of our approach. Our approach will help in identifying missing requirements or incomplete requirement coverage as well highlight the impact points for effective change management of requirements.