{"title":"论关系映射任务中错误的主动识别","authors":"Camila Nunes","doi":"10.1145/1960314.1960347","DOIUrl":null,"url":null,"abstract":"1. RESEARCH PROBLEM AND MOTIVATION The activity of explicitly assigning a stakeholder’s concern to its corresponding elements in the source code is known as concern mapping (or concern assignment) [1]. This is one of the most recurring and common activities in software maintenance tasks. Even though many techniques (Section 3.1) partially support concern identification [2-5], the developers are always forced to exhaustively verify if the mappings are correct and complete. Otherwise, the developers can unwittingly miss or implement incorrect changes in the system modules. In addition, existing tools usually support concern identification only at the class and method level, which are not sufficient for many software change tasks.","PeriodicalId":353153,"journal":{"name":"Aspect-Oriented Software Development","volume":"70 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-03-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"4","resultStr":"{\"title\":\"On the proactive identification of mistakes on concern mapping tasks\",\"authors\":\"Camila Nunes\",\"doi\":\"10.1145/1960314.1960347\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"1. RESEARCH PROBLEM AND MOTIVATION The activity of explicitly assigning a stakeholder’s concern to its corresponding elements in the source code is known as concern mapping (or concern assignment) [1]. This is one of the most recurring and common activities in software maintenance tasks. Even though many techniques (Section 3.1) partially support concern identification [2-5], the developers are always forced to exhaustively verify if the mappings are correct and complete. Otherwise, the developers can unwittingly miss or implement incorrect changes in the system modules. In addition, existing tools usually support concern identification only at the class and method level, which are not sufficient for many software change tasks.\",\"PeriodicalId\":353153,\"journal\":{\"name\":\"Aspect-Oriented Software Development\",\"volume\":\"70 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2011-03-21\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"4\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Aspect-Oriented Software Development\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/1960314.1960347\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Aspect-Oriented Software Development","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1960314.1960347","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
On the proactive identification of mistakes on concern mapping tasks
1. RESEARCH PROBLEM AND MOTIVATION The activity of explicitly assigning a stakeholder’s concern to its corresponding elements in the source code is known as concern mapping (or concern assignment) [1]. This is one of the most recurring and common activities in software maintenance tasks. Even though many techniques (Section 3.1) partially support concern identification [2-5], the developers are always forced to exhaustively verify if the mappings are correct and complete. Otherwise, the developers can unwittingly miss or implement incorrect changes in the system modules. In addition, existing tools usually support concern identification only at the class and method level, which are not sufficient for many software change tasks.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
