@INPROCEEDINGS{Antoniol05-TEFSE-FeatureTraceability,
   AUTHOR       = {Giuliano Antoniol and Ettore Merlo and 
      Yann-Ga�l Gu�h�neuc and Houari Sahraoui},
   BOOKTITLE    = {Proceedings of the 3<sup>rd</sup> ASE Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE)},
   TITLE        = {Feature Traceability in Object Oriented Software},
   YEAR         = {2005},
   OPTADDRESS   = {},
   OPTCROSSREF  = {},
   EDITOR       = {Jonathan I. Maletic and Giuliano Antonio and 
      Jane Cleland-Huang and Jane Huffman Hayes},
   MONTH        = {November},
   NOTE         = {6 pages.},
   OPTNUMBER    = {},
   OPTORGANIZATION = {},
   PAGES        = {73--78},
   PUBLISHER    = {ACM Press},
   OPTSERIES    = {},
   OPTVOLUME    = {},
   KEYWORDS     = {Topic: <b>Requirements and features</b>, 
      Venue: <i>TEFSE</i>},
   URL          = {http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf},
   PDF          = {http://www.ptidej.net/publications/documents/TEFSE05.ppt.pdf},
   ABSTRACT     = {Open source and industrial software very often lack 
      up-to- date documentation on where and how user observable 
      functionalities are implemented. This lack of documentation is 
      particularly hindering for large software. Moreover, as with any 
      software artifacts, user observable functionalities evolve and are 
      modified through software evolution activities. Modifications of one 
      functionality sometimes has unwanted and unexpected side effects on 
      other functionalities, causing these functionalities to fail or to 
      malfunction. In this position paper, we support the idea that a 
      traceability mapping between user observable functionalities and 
      source code constituents (such as classes, methods\ldots) 
      implementing the functionalities is essential to reduce software 
      evolution effort. We outline an approach to recover and to study the 
      evolution of features---subset of a software 
      constituents---responsible to implement a functionality.}
}

{"_id":"8N7cdZF2SGvsxCETc","bibbaseid":"antoniol-merlo-guhneuc-sahraoui-featuretraceabilityinobjectorientedsoftware-2005","downloads":0,"creationDate":"2018-01-17T20:29:42.578Z","title":"Feature Traceability in Object Oriented Software","author_short":["Antoniol, G.","Merlo, E.","Gu�h�neuc, Y.","Sahraoui, H."],"year":2005,"bibtype":"inproceedings","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Giuliano"],"propositions":[],"lastnames":["Antoniol"],"suffixes":[]},{"firstnames":["Ettore"],"propositions":[],"lastnames":["Merlo"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]},{"firstnames":["Houari"],"propositions":[],"lastnames":["Sahraoui"],"suffixes":[]}],"booktitle":"Proceedings of the 3^rd ASE Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE)","title":"Feature Traceability in Object Oriented Software","year":"2005","optaddress":"","optcrossref":"","editor":[{"firstnames":["Jonathan","I."],"propositions":[],"lastnames":["Maletic"],"suffixes":[]},{"firstnames":["Giuliano"],"propositions":[],"lastnames":["Antonio"],"suffixes":[]},{"firstnames":["Jane"],"propositions":[],"lastnames":["Cleland-Huang"],"suffixes":[]},{"firstnames":["Jane","Huffman"],"propositions":[],"lastnames":["Hayes"],"suffixes":[]}],"month":"November","note":"6 pages.","optnumber":"","optorganization":"","pages":"73–78","publisher":"ACM Press","optseries":"","optvolume":"","keywords":"Topic: <b>Requirements and features</b>, Venue: <i>TEFSE</i>","url":"http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/TEFSE05.ppt.pdf","abstract":"Open source and industrial software very often lack up-to- date documentation on where and how user observable functionalities are implemented. This lack of documentation is particularly hindering for large software. Moreover, as with any software artifacts, user observable functionalities evolve and are modified through software evolution activities. Modifications of one functionality sometimes has unwanted and unexpected side effects on other functionalities, causing these functionalities to fail or to malfunction. In this position paper, we support the idea that a traceability mapping between user observable functionalities and source code constituents (such as classes, methods…) implementing the functionalities is essential to reduce software evolution effort. We outline an approach to recover and to study the evolution of features—subset of a software constituents—responsible to implement a functionality.","bibtex":"@INPROCEEDINGS{Antoniol05-TEFSE-FeatureTraceability,\r\n AUTHOR = {Giuliano Antoniol and Ettore Merlo and \r\n Yann-Ga�l Gu�h�neuc and Houari Sahraoui},\r\n BOOKTITLE = {Proceedings of the 3^rd ASE Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE)},\r\n TITLE = {Feature Traceability in Object Oriented Software},\r\n YEAR = {2005},\r\n OPTADDRESS = {},\r\n OPTCROSSREF = {},\r\n EDITOR = {Jonathan I. Maletic and Giuliano Antonio and \r\n Jane Cleland-Huang and Jane Huffman Hayes},\r\n MONTH = {November},\r\n NOTE = {6 pages.},\r\n OPTNUMBER = {},\r\n OPTORGANIZATION = {},\r\n PAGES = {73--78},\r\n PUBLISHER = {ACM Press},\r\n OPTSERIES = {},\r\n OPTVOLUME = {},\r\n KEYWORDS = {Topic: <b>Requirements and features</b>, \r\n Venue: <i>TEFSE</i>},\r\n URL = {http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf},\r\n PDF = {http://www.ptidej.net/publications/documents/TEFSE05.ppt.pdf},\r\n ABSTRACT = {Open source and industrial software very often lack \r\n up-to- date documentation on where and how user observable \r\n functionalities are implemented. This lack of documentation is \r\n particularly hindering for large software. Moreover, as with any \r\n software artifacts, user observable functionalities evolve and are \r\n modified through software evolution activities. Modifications of one \r\n functionality sometimes has unwanted and unexpected side effects on \r\n other functionalities, causing these functionalities to fail or to \r\n malfunction. In this position paper, we support the idea that a \r\n traceability mapping between user observable functionalities and \r\n source code constituents (such as classes, methods\\ldots) \r\n implementing the functionalities is essential to reduce software \r\n evolution effort. We outline an approach to recover and to study the \r\n evolution of features---subset of a software \r\n constituents---responsible to implement a functionality.}\r\n}\r\n\r\n","author_short":["Antoniol, G.","Merlo, E.","Gu�h�neuc, Y.","Sahraoui, H."],"editor_short":["Maletic, J. I.","Antonio, G.","Cleland-Huang, J.","Hayes, J. H."],"key":"Antoniol05-TEFSE-FeatureTraceability","id":"Antoniol05-TEFSE-FeatureTraceability","bibbaseid":"antoniol-merlo-guhneuc-sahraoui-featuretraceabilityinobjectorientedsoftware-2005","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf"},"keyword":["Topic: <b>Requirements and features</b>","Venue: <i>TEFSE</i>"],"metadata":{"authorlinks":{"gu�h�neuc, y":"https://bibbase.org/show?bib=http%3A%2F%2Fwww.yann-gael.gueheneuc.net%2FWork%2FPublications%2FBiblio%2Fcomplete-bibliography.bib&msg=embed","guéhéneuc, y":"http://www.yann-gael.gueheneuc.net/"}}},"search_terms":["feature","traceability","object","oriented","software","antoniol","merlo","gu�h�neuc","sahraoui"],"keywords":["topic: <b>requirements and features</b>","venue: <i>tefse</i>"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}