Feature Traceability in Object Oriented Software. Antoniol, G., Merlo, E., Guéhéneuc, Y., & Sahraoui, H. In Maletic, J. I., Antonio, G., Cleland-Huang, J., & Hayes, J. H., editors, Proceedings of the 3<sup>rd</sup> ASE workshop on Traceability in Emerging Forms of Software Engineering (TEFSE), pages 73–78, November, 2005. ACM Press. 6 pages.Paper abstract bibtex 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.
@INPROCEEDINGS{Antoniol05-TEFSE-FeatureTraceability,
author = {Giuliano Antoniol and Ettore Merlo and Yann-Ga{\"e}l Gu{\'e}h{\'e}neuc and Houari Sahraoui},
title = {Feature Traceability in Object Oriented Software},
booktitle = {Proceedings of the 3<sup>{rd}</sup> {ASE} workshop on Traceability in Emerging Forms of Software Engineering ({TEFSE})},
year = {2005},
month = {November},
editor = {Jonathan I. Maletic and Giuliano Antonio and Jane Cleland-Huang and Jane Huffman Hayes},
publisher = {ACM Press},
note = {6 pages.},
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.},
grant = {NSERC DG},
keywords = {Features and requirements ; TEFSE},
kind = {MIADR},
language = {english},
url = {http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf},
pdf = {http://www.ptidej.net/publications/documents/TEFSE05.ppt.pdf},
pages = {73--78}
}
Downloads: 0
{"_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/BibBase/guehene (automatically cleaned).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":[]}],"title":"Feature Traceability in Object Oriented Software","booktitle":"Proceedings of the 3<sup>rd</sup> ASE workshop on Traceability in Emerging Forms of Software Engineering (TEFSE)","year":"2005","month":"November","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":[]}],"publisher":"ACM Press","note":"6 pages.","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.","grant":"NSERC DG","keywords":"Features and requirements ; TEFSE","kind":"MIADR","language":"english","url":"http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/TEFSE05.ppt.pdf","pages":"73–78","bibtex":"@INPROCEEDINGS{Antoniol05-TEFSE-FeatureTraceability,\n author = {Giuliano Antoniol and Ettore Merlo and Yann-Ga{\\\"e}l Gu{\\'e}h{\\'e}neuc and Houari Sahraoui},\n title = {Feature Traceability in Object Oriented Software},\n booktitle = {Proceedings of the 3<sup>{rd}</sup> {ASE} workshop on Traceability in Emerging Forms of Software Engineering ({TEFSE})},\n year = {2005},\n month = {November},\n editor = {Jonathan I. Maletic and Giuliano Antonio and Jane Cleland-Huang and Jane Huffman Hayes},\n publisher = {ACM Press},\n note = {6 pages.},\n 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.},\n grant = {NSERC DG},\n keywords = {Features and requirements ; TEFSE},\n kind = {MIADR},\n language = {english},\n url = {http://www.ptidej.net/publications/documents/TEFSE05.doc.pdf},\n pdf = {http://www.ptidej.net/publications/documents/TEFSE05.ppt.pdf},\n pages = {73--78}\n}\n\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":["Features and requirements ; TEFSE"],"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":"https://bibbase.org/show?bib=http://www.yann-gael.gueheneuc.net/Work/BibBase/guehene%20(automatically%20cleaned).bib"}},"downloads":0,"html":""},"search_terms":["feature","traceability","object","oriented","software","antoniol","merlo","guéhéneuc","sahraoui"],"keywords":["features and requirements ; tefse"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}