{"title":"RE_PROV:用PROV建模需求来源","authors":"Yangfan He, Xiaojian Li","doi":"10.1109/APSEC.2016.069","DOIUrl":null,"url":null,"abstract":"Requirements are complex by nature. When describing something that has not been realized, users may find it difficult to interpret it accurately. Many problems cannot be discovered until some abstract concepts become concrete and some details have been confirmed. So checking the origination and processing history of the requirements and making adjustments are very normal practice. Requirement provenance records which have well-defined syntax and explicit semantics can provide solid support for requirement traceability analysis. By setting up the mapping between PROV and a typical requirement framework, this paper proposes RE_PROV, a novel model for the description of requirement provenance. The rationales of the mapping are explained and a comprehend example of an embedded software design is provided to show possible usage.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"12 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"RE_PROV: Modeling Requirement Provenance with PROV\",\"authors\":\"Yangfan He, Xiaojian Li\",\"doi\":\"10.1109/APSEC.2016.069\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Requirements are complex by nature. When describing something that has not been realized, users may find it difficult to interpret it accurately. Many problems cannot be discovered until some abstract concepts become concrete and some details have been confirmed. So checking the origination and processing history of the requirements and making adjustments are very normal practice. Requirement provenance records which have well-defined syntax and explicit semantics can provide solid support for requirement traceability analysis. By setting up the mapping between PROV and a typical requirement framework, this paper proposes RE_PROV, a novel model for the description of requirement provenance. The rationales of the mapping are explained and a comprehend example of an embedded software design is provided to show possible usage.\",\"PeriodicalId\":339123,\"journal\":{\"name\":\"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)\",\"volume\":\"12 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1900-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/APSEC.2016.069\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/APSEC.2016.069","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
RE_PROV: Modeling Requirement Provenance with PROV
Requirements are complex by nature. When describing something that has not been realized, users may find it difficult to interpret it accurately. Many problems cannot be discovered until some abstract concepts become concrete and some details have been confirmed. So checking the origination and processing history of the requirements and making adjustments are very normal practice. Requirement provenance records which have well-defined syntax and explicit semantics can provide solid support for requirement traceability analysis. By setting up the mapping between PROV and a typical requirement framework, this paper proposes RE_PROV, a novel model for the description of requirement provenance. The rationales of the mapping are explained and a comprehend example of an embedded software design is provided to show possible usage.