Case study

Reconnaissance techniques to support feature location using RECON2

Suhaimi Ibrahim, Norbik Bashah Idris, Aziz Deraman

    Research output: Chapter in Book/Report/Conference proceedingConference contribution

    3 Citations (Scopus)

    Abstract

    Change requests are often formulated into concepts or features that a maintainer can understand. One of the main issues faced by a maintainer is to know and locate "where does this program implement feature X". However, these features are implicitly available in the code and scattered elsewhere that make them undoubtedly difficult to manage. A technique called software reconnaissance was originally inspired by industrial maintainers about the need for better ways of locating software features in large systems. This paper presents the authors' experience in using the software reconnaissance technique and tool called RECON2, developed by the university of West Florida. Our objective is to understand how the technique and tool work and to further suggest some enhancements with respect to software understanding strategies.

    Original languageEnglish
    Title of host publicationProceedings - Asia-Pacific Software Engineering Conference, APSEC
    PublisherIEEE Computer Society
    Pages371-378
    Number of pages8
    Volume2003-January
    ISBN (Print)0769520111
    DOIs
    Publication statusPublished - 2003
    Event10th Asia-Pacific Software Engineering Conference, APSEC 2003 - Chiang Mai, Thailand
    Duration: 10 Dec 200312 Dec 2003

    Other

    Other10th Asia-Pacific Software Engineering Conference, APSEC 2003
    CountryThailand
    CityChiang Mai
    Period10/12/0312/12/03

    Keywords

    • Change request
    • Concept location
    • Dynamic analysis
    • Software reconnaissance
    • Software understanding

    ASJC Scopus subject areas

    • Software

    Cite this

    Ibrahim, S., Idris, N. B., & Deraman, A. (2003). Case study: Reconnaissance techniques to support feature location using RECON2. In Proceedings - Asia-Pacific Software Engineering Conference, APSEC (Vol. 2003-January, pp. 371-378). [1254391] IEEE Computer Society. https://doi.org/10.1109/APSEC.2003.01254391

    Case study : Reconnaissance techniques to support feature location using RECON2. / Ibrahim, Suhaimi; Idris, Norbik Bashah; Deraman, Aziz.

    Proceedings - Asia-Pacific Software Engineering Conference, APSEC. Vol. 2003-January IEEE Computer Society, 2003. p. 371-378 1254391.

    Research output: Chapter in Book/Report/Conference proceedingConference contribution

    Ibrahim, S, Idris, NB & Deraman, A 2003, Case study: Reconnaissance techniques to support feature location using RECON2. in Proceedings - Asia-Pacific Software Engineering Conference, APSEC. vol. 2003-January, 1254391, IEEE Computer Society, pp. 371-378, 10th Asia-Pacific Software Engineering Conference, APSEC 2003, Chiang Mai, Thailand, 10/12/03. https://doi.org/10.1109/APSEC.2003.01254391
    Ibrahim S, Idris NB, Deraman A. Case study: Reconnaissance techniques to support feature location using RECON2. In Proceedings - Asia-Pacific Software Engineering Conference, APSEC. Vol. 2003-January. IEEE Computer Society. 2003. p. 371-378. 1254391 https://doi.org/10.1109/APSEC.2003.01254391
    Ibrahim, Suhaimi ; Idris, Norbik Bashah ; Deraman, Aziz. / Case study : Reconnaissance techniques to support feature location using RECON2. Proceedings - Asia-Pacific Software Engineering Conference, APSEC. Vol. 2003-January IEEE Computer Society, 2003. pp. 371-378
    @inproceedings{c39226d70a3c44ae968ed95b896c5369,
    title = "Case study: Reconnaissance techniques to support feature location using RECON2",
    abstract = "Change requests are often formulated into concepts or features that a maintainer can understand. One of the main issues faced by a maintainer is to know and locate {"}where does this program implement feature X{"}. However, these features are implicitly available in the code and scattered elsewhere that make them undoubtedly difficult to manage. A technique called software reconnaissance was originally inspired by industrial maintainers about the need for better ways of locating software features in large systems. This paper presents the authors' experience in using the software reconnaissance technique and tool called RECON2, developed by the university of West Florida. Our objective is to understand how the technique and tool work and to further suggest some enhancements with respect to software understanding strategies.",
    keywords = "Change request, Concept location, Dynamic analysis, Software reconnaissance, Software understanding",
    author = "Suhaimi Ibrahim and Idris, {Norbik Bashah} and Aziz Deraman",
    year = "2003",
    doi = "10.1109/APSEC.2003.01254391",
    language = "English",
    isbn = "0769520111",
    volume = "2003-January",
    pages = "371--378",
    booktitle = "Proceedings - Asia-Pacific Software Engineering Conference, APSEC",
    publisher = "IEEE Computer Society",

    }

    TY - GEN

    T1 - Case study

    T2 - Reconnaissance techniques to support feature location using RECON2

    AU - Ibrahim, Suhaimi

    AU - Idris, Norbik Bashah

    AU - Deraman, Aziz

    PY - 2003

    Y1 - 2003

    N2 - Change requests are often formulated into concepts or features that a maintainer can understand. One of the main issues faced by a maintainer is to know and locate "where does this program implement feature X". However, these features are implicitly available in the code and scattered elsewhere that make them undoubtedly difficult to manage. A technique called software reconnaissance was originally inspired by industrial maintainers about the need for better ways of locating software features in large systems. This paper presents the authors' experience in using the software reconnaissance technique and tool called RECON2, developed by the university of West Florida. Our objective is to understand how the technique and tool work and to further suggest some enhancements with respect to software understanding strategies.

    AB - Change requests are often formulated into concepts or features that a maintainer can understand. One of the main issues faced by a maintainer is to know and locate "where does this program implement feature X". However, these features are implicitly available in the code and scattered elsewhere that make them undoubtedly difficult to manage. A technique called software reconnaissance was originally inspired by industrial maintainers about the need for better ways of locating software features in large systems. This paper presents the authors' experience in using the software reconnaissance technique and tool called RECON2, developed by the university of West Florida. Our objective is to understand how the technique and tool work and to further suggest some enhancements with respect to software understanding strategies.

    KW - Change request

    KW - Concept location

    KW - Dynamic analysis

    KW - Software reconnaissance

    KW - Software understanding

    UR - http://www.scopus.com/inward/record.url?scp=49349101865&partnerID=8YFLogxK

    UR - http://www.scopus.com/inward/citedby.url?scp=49349101865&partnerID=8YFLogxK

    U2 - 10.1109/APSEC.2003.01254391

    DO - 10.1109/APSEC.2003.01254391

    M3 - Conference contribution

    SN - 0769520111

    VL - 2003-January

    SP - 371

    EP - 378

    BT - Proceedings - Asia-Pacific Software Engineering Conference, APSEC

    PB - IEEE Computer Society

    ER -