BibSLEIGH — traceability tag

traceability

traceability

Tag #traceability

234 papers:

ICSA-2019-ArcelliCPET #architecture #modelling #performance #runtime: Exploiting Architecture/Runtime Model-Driven Traceability for Performance Improvement (DA, VC, DDP, RE, MT0), pp. 81–90.
ICPC-2019-KuangG0M0ME #analysis #feedback #using: Using frugal user feedback with closeness analysis on code to improve IR-based traceability recovery (HK, HG, HH0, XM, JL0, PM, AE), pp. 369–379.
ICSME-2019-AungHS #interactive #using #visualisation: Interactive Traceability Links Visualization using Hierarchical Trace Map (TWWA, HH, YS), pp. 367–369.
ICSME-2019-MillsEBKCH #classification #learning: Tracing with Less Data: Active Learning for Classification-Based Traceability Link Recovery (CM, JEA, AB, GK, SC, SH), pp. 103–113.
SANER-2019-Jin #challenge #requirements: Forward and backward traceability: Requirements and challenges (Keynote) (ZJ), p. 3.
ESEC-FSE-2019-Cetin #developer #graph #identification #using: Identifying the most valuable developers using artifact traceability graphs (HAC), pp. 1196–1198.
ESEC-FSE-2019-KrugerCBLS #comprehension: Effects of explicit feature traceability on program comprehension (JK, GÇ, TB, TL, GS), pp. 338–349.
ESEC-FSE-2019-Sulun #graph #using: Suggesting reviewers of software artifacts using traceability graphs (ES), pp. 1250–1252.
ICSME-2018-AbukwaikBAB #automation #embedded: Semi-Automated Feature Traceability with Embedded Annotations (HA, AB, BKA, TB), pp. 529–533.
ICSME-2018-MillsEH #automation #classification #machine learning #maintenance: Automatic Traceability Maintenance via Machine Learning Classification (CM, JEA, SH), pp. 369–380.
MSR-2018-0002LM08 #debugging #information management #locality #requirements: Analyzing requirements and traceability information to improve bug localization (MR0, DL0, PM), pp. 442–453.
ECMFA-2018-RutleIKD #automation #co-evolution #graph transformation #modelling #using: Automatic Transformation Co-evolution Using Traceability Models and Graph Transformation (AR, LI, HK, ZD), pp. 80–96.
ASE-2018-FalessiPCC: Estimating the number of remaining links in traceability recovery (journal-first abstract) (DF, MDP, GC, GC), p. 953.
ICSE-2018-0002RGCM #automation: Traceability in the wild: automatically augmenting incomplete trace links (MR0, JR, JLCG, JCH, PM), pp. 834–845.
ICSA-2017-NassarS #fault #metric #predict #question: Traceability Metrics as Early Predictors of Software Defects? (BN, RS), pp. 235–238.
ICSA-2017-ZhengCA #architecture #consistency #product line #source code: Mapping Features to Source Code through Product Line Architecture: Traceability and Conformance (YZ, CC, HUA), pp. 225–234.
SANER-2017-KuangNHRLEM #dependence: Analyzing closeness of code dependencies for improving IR-based Traceability Recovery (HK, JN, HH0, PR, JL0, AE, PM), pp. 68–78.
ASE-2017-Mills #automation #classification #towards: Towards the automatic classification of traceability links (CM), pp. 1018–1021.
ESEC-FSE-2017-Mills #automation #classification: Automating traceability link recovery through classification (CM), pp. 1068–1070.
ICSE-2017-0004CC #learning #semantics #using: Semantically enhanced software traceability using deep learning techniques (JG0, JC, JCH), pp. 3–14.
FASE-2017-DiskinGC #model transformation: Traceability Mappings as a Fundamental Instrument in Model Transformations (ZD, AG, JC), pp. 247–263.
ICST-2017-Al-QahtaniER #api #approach #modelling #ontology #security #semantics: Recovering Semantic Traceability Links between APIs and Security Vulnerabilities: An Ontological Modeling Approach (SSAQ, EEE, JR), pp. 80–91.
WICSA-2016-SantosMMZ #architecture #named #research: BUDGET: A Tool for Supporting Software Architecture Traceability Research (JCSS, MM, IM, WZ), pp. 303–306.
ICSME-2016-DemuthKEM #automation #case study #consistency #experience #impact analysis #tool support: Introducing Traceability and Consistency Checking for Change Impact Analysis across Engineering Tools in an Automation Solution Company: An Experience Report (AD, RK, AE, DM), pp. 529–538.
SANER-2016-LozanoNJ: Managing Traceability Links with MaTraca (AL, CN, VJ), pp. 665–668.
BX-2016-Leblebici #approach #consistency #grammarware #graph grammar #towards: Towards a Graph Grammar-Based Approach to Inter-Model Consistency Checks with Traceability Support (EL), pp. 35–39.
ASE-2016-MaroAWS #guidelines #maintenance: Traceability maintenance: factors and guidelines (SM, AA, RW, JPS), pp. 414–425.
FSE-2016-NiuWG #requirements #using: Gray links in the use of requirements traceability (NN, WW0, AG), pp. 384–395.
ECSA-2015-TrubianiGE #analysis #architecture #modelling #nondeterminism #performance: Exploiting Traceability Uncertainty Between Software Architectural Models and Performance Analysis Results (CT, AG, AE), pp. 305–321.
ICSME-2015-NishikawaWFOM #transitive: Recovering transitive traceability links among software artifacts (KN, HW, YF, KO, RM), pp. 576–580.
CAiSE-2015-KhouriSB #approach #data transformation #lifecycle: Managing Data Warehouse Traceability: A Life-Cycle Driven Approach (SK, KS, LB), pp. 199–213.
CAiSE-2015-TsuchiyaWFOM #configuration management #feedback #interactive #requirements #using: Interactive Recovery of Requirements Traceability Links Using User Feedback and Configuration Management Logs (RT, HW, YF, KO, RM), pp. 247–262.
ICEIS-v2-2015-McharfiADBK #product line: Return on Investment of Software Product Line Traceability in the Short, Mid and Long Term (ZM, BEA, ID, AB, AK), pp. 463–468.
SPLC-2015-JiBAC #embedded #maintenance: Maintaining feature traceability with embedded annotations (WJ, TB, MA, KC), pp. 61–70.
REFSQ-2015-RempelM #agile #development #implementation #metric #requirements: Estimating the Implementation Risk of Requirements in Agile Software Development Projects with Traceability Metrics (PR, PM), pp. 81–97.
SAC-2015-MarquesRA #named #representation: TRL: a traceability representation language (AM, FR, WdLA), pp. 1358–1363.
SAC-2015-MarquesRA15a #process #requirements #towards: Towards a requirements traceability process centered on the traceability model (AM, FR, WdLA), pp. 1364–1369.
WICSA-2014-JavedZ #architecture #comprehension: The Supportive Effect of Traceability Links in Architecture-Level Software Understanding: Two Controlled Experiments (MAJ, UZ), pp. 215–224.
ICPC-2014-WaltersSSK #developer: Capturing software traceability links from developers’ eye gazes (BW, TS, BS, HHK), pp. 201–204.
ICEIS-v2-2014-ThommazoRROHWF #using: Using Artificial Intelligence Techniques to Enhance Traceability Links (ADT, RR, TRdO, GO, EMH, VW, SCPFF), pp. 26–38.
ECIR-2014-StangeN #collaboration #overview: Search Maps — Enhancing Traceability and Overview in Collaborative Information Seeking (DS, AN), pp. 763–766.
KMIS-2014-FrancoisMA #communication #design #email #problem #using: Discovering Problem-Solving Knowledge in Business Emails — Traceability in Software Design Using Computer Mediated Communication (RF, NM, HA), pp. 186–193.
ECMFA-2014-PfeifferRW #independence: Language-Independent Traceability with Lässig (RHP, JR, AW), pp. 148–163.
RE-2014-GervasiZ #mining: Supporting traceability through affinity mining (VG, DZ), pp. 143–152.
REFSQ-2014-NairVMTdB #analysis #problem #safety: Safety Evidence Traceability: Problem Analysis and Model (SN, JLdlV, AM, GT, LdlB, FB), pp. 309–324.
ASE-2014-GuoMPC #towards: Towards an intelligent domain-specific traceability solution (JG, NM, CP, JCH), pp. 755–766.
FSE-2014-Cleland-HuangRM #lightweight: Achieving lightweight trustworthy traceability (JCH, MR, PM), pp. 849–852.
FSE-2014-Kan #model checking #safety #verification: Traceability and model checking to support safety requirement verification (SK), pp. 783–786.
ICSE-2014-RempelMKC #consistency #guidelines: Mind the gap: assessing the conformance of software traceability to relevant guidelines (PR, PM, TK, JCH), pp. 943–954.
SAC-2014-OhK #architecture #requirements: A hierarchical model for traceability between requirements and architecture (JO, SK), pp. 1035–1042.
ECSA-2013-Kuster #architecture #design #modelling #validation: Architecture-Centric Modeling of Design Decisions for Validation and Traceability (MK), pp. 184–191.
CSMR-2013-AsgharMSS #metric #requirements #using: Maintainability-Based Requirements Prioritization by Using Artifacts Traceability and Code Metrics (MWA, AM, AS, GS), pp. 417–420.
CSMR-2013-PanichellaMMPOPL #how #using: When and How Using Structural Information to Improve IR-Based Traceability Recovery (AP, CM, EM, DP, RO, DP, ADL), pp. 199–208.
ICPC-2013-DiazBMOTL #using: Using code ownership to improve IR-based Traceability Link Recovery (DD, GB, AM, RO, ST, ADL), pp. 123–132.
ICSM-2013-DasguptaGMDP #automation #corpus #documentation: Enhancing Software Traceability by Automatically Expanding Corpora with Relevant Documentation (TD, MG, EM, BD, DP), pp. 320–329.
WCRE-2013-AliJH #co-evolution #requirements: Leveraging historical co-change information for requirements traceability (NA, FJ, AEH), pp. 361–370.
ICEIS-J-2013-AlvesSCCCWGBGC13a #named #semantics #tool support #web: Fairtrace: Applying Semantic Web Tools and Techniques to the Textile Traceability (BA, MS, FC, ALC, GC, DW, CG, BB, DG, PC), pp. 68–84.
ICEIS-v1-2013-AlvesSCCCWGBGC #named #semantics: Fairtrace — A Semantic-web Oriented Traceability Solution Applied to the Textile Traceability (BA, MS, FC, ALC, GC, DW, CG, BB, DG, PC), pp. 36–45.
SEKE-2013-CorreaOW #co-evolution #evolution #graph #metamodelling #modelling #towards: Towards Coupled Evolution of Metamodels, Models, Graph-Based Transformations and Traceability Links (CKFC, TCO, CW), pp. 747–752.
SEKE-2013-ThommazoOORWF #detection #network: Detecting traceability links through neural networks (ADT, TRdO, GO, RR, VW, SF), pp. 36–41.
SEKE-2013-Unkelos-ShpigelHL #deployment #information management #requirements: Enhancing Deployment Requirements’ Traceability via Knowledge Management Audit (NUS, IH, ML), pp. 574–577.
SPLC-2013-LinsbauerLE: Recovering traceability between features and code in product variants (LL, RELH, AE), pp. 131–140.
SPLC-2013-TsuchiyaKWKFY #requirements #source code: Recovering traceability links between requirements and source code in the same series of software products (RT, TK, HW, MK, YF, KY), pp. 121–130.
PEPM-2013-SulzmannNZ #abstraction #correctness: Traceability and evidence of correctness of EDSL abstractions (MS, JNF, AZ), pp. 71–74.
ER-BR-2013-FilhoLRS #named #tool support: RETRATOS: Requirement Traceability Tool Support (GACF, ML, AR, CS).
RE-2013-0004CB: Foundations for an expert system in domain-specific traceability (JG, JCH, BB), pp. 42–51.
RE-2013-MahmoudN #refactoring #requirements: Supporting requirements traceability through refactoring (AM, NN), pp. 32–41.
RE-2013-NairVS #overview #requirements #research: A review of traceability research at the requirements engineering conferencere@21 (SN, JLdlV, SS), pp. 222–229.
RE-2013-RempelMK #empirical: An empirical study on project-specific traceability strategies (PR, PM, TK), pp. 195–204.
REFSQ-2013-BouillonMP #overview #requirements: A Survey on Usage Scenarios for Requirements Traceability in Practice (EB, PM, IP), pp. 158–173.
REFSQ-2013-BreauxG #analysis #requirements #specification #using: Regulatory Requirements Traceability and Analysis Using Semi-formal Specifications (TDB, DGG), pp. 141–157.
REFSQ-2013-RempelMKP #bound #overview #requirements #taxonomy: Requirements Traceability across Organizational Boundaries — A Survey and Taxonomy (PR, PM, TK, IP), pp. 125–140.
SAC-2013-ZiftciK #requirements #semantics #testing: Test intents: enhancing the semantics of requirements traceability links in test cases (CZ, IK), pp. 1272–1277.
WICSA-ECSA-2012-GhabiE #architecture #modelling #nondeterminism: Exploiting Traceability Uncertainty between Architectural Models and Code (AG, AE), pp. 171–180.
WICSA-ECSA-2012-TauschPA #analysis #domain-specific language #named: TracQL: A Domain-Specific Language for Traceability Analysis (NT, MP, JA), pp. 320–324.
CSMR-2012-BorgWP #industrial #overview #research #student: Industrial Comparability of Student Artifacts in Traceability Recovery Research — An Exploratory Survey (MB, KW, DP), pp. 181–190.
ICPC-2012-MahmoudNX #approach #semantics: A semantic relatedness approach for traceability link recovery (AM, NN, SX), pp. 183–192.
ICSM-2012-AliSGA #empirical #requirements #using: An empirical study on requirements traceability using eye-tracking (NA, ZS, YGG, GA), pp. 191–200.
ICSM-2012-BavotaCLFOP #eclipse #named: TraceME: Traceability Management in Eclipse (GB, LC, ADL, SF, RO, AP), pp. 642–645.
ICSM-2012-KuangMHGHJE #comprehension #dependence #question #requirements #source code: Do data dependencies in source code complement call dependencies for understanding requirements traceability? (HK, PM, HH, AG, LH, JL, AE), pp. 181–190.
ICSM-2012-MaderE #maintenance #requirements: Assessing the effect of requirements traceability for software maintenance (PM, AE), pp. 171–180.
WCRE-2012-AngiusW #automation #named #open source: OpenTrace: An Open Source Workbench for Automatic Software Traceability Link Recovery (EA, RW), pp. 507–508.
SEKE-2012-AsuncionT #approach: A Holistic Approach to Software Traceability (HUA, RNT), pp. 412–417.
ICMT-2012-AmstelBS #model transformation #visualisation: Traceability Visualization in Model Transformations with TraceVis (MvA, MvdB, AS), pp. 152–159.
RE-2012-Cleland-HuangMMA #recommendation: Breaking the big-bang practice of traceability: Pushing timely trace recommendations to project stakeholders (JCH, PM, MM, SA), pp. 231–240.
RE-2012-GotelCHZEGA #research #roadmap: The quest for Ubiquity: A roadmap for software and systems traceability research (OG, JCH, JHH, AZ, AE, PG, GA), pp. 71–80.
RE-2012-KongHDD #case study #process: Process improvement for traceability: A study of human fallibility (WKK, JHH, AD, OD), pp. 31–40.
REFSQ-2012-LiM #case study #comparative #visualisation: Which Traceability Visualization Is Suitable in This Context? A Comparative Study (YL, WM), pp. 194–210.
ASE-2012-LedruVTB #testing: Test suite selection based on traceability annotations (YL, GV, TT, LdB), pp. 342–345.
ICSE-2012-DagenaisR #api #learning: Recovering traceability links between an API and its learning resources (BD, MPR), pp. 47–57.
ICSE-2012-Imtiaz #architecture #distributed #perspective: Architectural task allocation in distributed environment: A traceability perspective (SI), pp. 1515–1518.
ICSE-2012-KeenanCLCSMGPMHDMHH #named #research: TraceLab: An experimental workbench for equipping researchers to innovate, synthesize, and comparatively evaluate traceability solutions (EK, AC, GL, JCH, YS, EM, MG, DP, JIM, JHH, AD, DM, SH, DH), pp. 1375–1378.
ICSE-2012-MirakhorliSCC #approach #automation #quality: A tactic-centric approach for automating traceability of quality concerns (MM, YS, JCH, MÇ), pp. 639–649.
ICSE-2012-YuLHHKM #bidirectional #invariant #maintenance: Maintaining invariant traceability through bidirectional transformations (YY, YL, ZH, SH, HK, LM), pp. 540–550.
SAC-2012-SardinhaYNR #aspect-oriented #identification #named: EA-tracer: identifying traceability links between code aspects and early aspects (AS, YY, NN, AR), pp. 1035–1042.
ECSA-2011-AdersbergerP #architecture #consistency #named #uml: ReflexML: UML-Based Architecture-to-Code Traceability and Consistency Checking (JA, MP), pp. 344–359.
ICPC-J-2009-HammadCM11 #automation #evolution #identification: Automatically identifying changes that impact code-to-design traceability during evolution (MH, MLC, JIM), pp. 35–64.
CSMR-2011-Borg #evaluation #scalability: In Vivo Evaluation of Large-Scale IR-Based Traceability Recovery (MB), pp. 365–368.
CSMR-2011-Seibel #model management: From Software Traceability to Global Model Management and Back Again (AS), pp. 381–384.
ICPC-2011-AliGA #requirements #trust: Trust-Based Requirements Traceability (NA, YGG, GA), pp. 111–120.
ICPC-2011-LuciaPOPP #using: Improving IR-based Traceability Recovery Using Smoothing Filters (ADL, MDP, RO, AP, SP), pp. 21–30.
ICSM-2011-GethersOPL #information retrieval #on the #orthogonal: On integrating orthogonal information retrieval methods to improve traceability recovery (MG, RO, DP, ADL), pp. 133–142.
ICSM-2011-MirakhorliC #architecture #information management #maintenance #modelling #using: Using tactic traceability information models to reduce the risk of architectural degradation during system maintenance (MM, JCH), pp. 123–132.
ICSM-2011-QusefBOLB #concept #named #slicing #using: SCOTCH: Test-to-code traceability using slicing and conceptual coupling (AQ, GB, RO, ADL, DB), pp. 63–72.
WCRE-2011-AliGA #clustering #object-oriented #requirements #source code: Requirements Traceability for Object Oriented Systems by Partitioning Source Code (NA, YGG, GA), pp. 45–54.
WCRE-2011-KaushikTM #case study #debugging #testing: Reconstructing Traceability between Bugs and Test Cases: An Experimental Study (NK, LT, MM), pp. 411–414.
WCRE-2011-Qusef #concept #slicing: Recovering Test-to-Code Traceability Via Slicing and Conceptual Coupling (AQ), pp. 417–420.
CAiSE-2011-MateT #architecture #framework #metamodelling #modelling #requirements: A Trace Metamodel Proposal Based on the Model Driven Architecture Framework for the Traceability of User Requirements in Data Warehouses (AM, JT), pp. 123–137.
ICEIS-v2-2011-Jin-shiH #game studies: Establishing Food Traceability System based on Game Theory — From the Perspective of Retailers (WJs, LHj), pp. 368–372.
ICEIS-v3-2011-PanfilenkoLWL #architecture #enterprise: Traceability and Viewpoints in Enterprise Architectures (DP, RL, DW, PL), pp. 150–156.
RE-2011-GotelM #requirements: Out of the labyrinth: Leveraging other disciplines for requirements traceability (OG, SJM), pp. 121–130.
RE-2011-MahmoudN #clustering #named: TraCter: A tool for candidate traceability link clustering (AM, NN), pp. 335–336.
RE-2011-OhashiKTY #development #uml: A means of establishing traceability based on a UML model in business application development (KO, HK, YT, RY), pp. 279–284.
ASE-2011-ChenG #automation #documentation #retrieval: Improving automated documentation to code traceability by combining retrieval techniques (XC, JCG), pp. 223–232.
ASE-2011-MaderE #empirical #navigation #source code: Do software engineers benefit from source code navigation with traceability? — An experiment in software change management (PM, AE), pp. 444–447.
ICSE-2011-ChenHG #approach #automation: A combination approach for enhancing automated traceability (XC, JGH, JCG), pp. 912–915.
ICPC-2010-AversanoMT #component #process: Recovering Traceability Links between Business Process and Software System Components (LA, FM, MT), pp. 52–53.
ICPC-2010-OlivetoGPL #automation #equivalence #information retrieval #on the: On the Equivalence of Information Retrieval Methods for Automated Traceability Link Recovery (RO, MG, DP, ADL), pp. 68–71.
ICSM-2010-QusefOL #testing: Recovering traceability links between unit tests and classes under test: An improved method (AQ, RO, ADL), pp. 1–10.
MoDELS-v1-2010-MaderC #modelling #visual notation: A Visual Traceability Modeling Language (PM, JCH), pp. 226–240.
RE-2010-CuddebackDH #automation #case study #requirements: Automated Requirements Traceability: The Study of Human Analysts (DC, AD, JHH), pp. 231–240.
RE-2010-HillT #legacy #requirements #safety: Creating Safety Requirements Traceability for Assuring and Recertifying Legacy Safety-Critical Systems (JH, SRT), pp. 297–302.
RE-2010-Panis #deployment #requirements: Successful Deployment of Requirements Traceability in a Commercial Engineering Organization...Really (MCP), pp. 303–307.
ASE-2010-Chen #documentation #source code #visualisation: Extraction and visualization of traceability relationships between documents and source code (XC), pp. 505–510.
ICSE-2010-AsuncionAT #modelling #topic: Software traceability with topic modeling (HUA, AUA, RNT), pp. 95–104.
SAC-2010-EspinozaBG #approach #formal method #reuse: A formal approach to reuse successful traceability practices in SPL projects (AE, GB, JG), pp. 2352–2359.
ICST-2010-NaslavskyZR #modelling #named #testing: MbSRT2: Model-Based Selective Regression Testing with Traceability (LN, HZ, DJR), pp. 89–98.
CSMR-2009-RompaeyD #testing: Establishing Traceability Links between Unit Test Cases and Units under Test (BVR, SD), pp. 209–218.
CSMR-2009-Schwarz #approach #maintenance #towards: Towards a Comprehensive Traceability Approach in the Context of Software Maintenance (HS), pp. 339–342.
ICPC-2009-CapobiancoLOPP #on the: On the role of the nouns in IR-based traceability recovery (GC, ADL, RO, AP, SP), pp. 148–157.
ICPC-2009-HammadCM #automation #identification: Automatically identifying changes that impact code-to-design traceability (MH, MLC, JIM), pp. 20–29.
ICSM-2009-LuciaOT #analysis #empirical: The role of the coverage analysis during IR-based traceability recovery: A controlled experiment (ADL, RO, GT), pp. 371–380.
ICSM-2009-YoshikawaHS #natural language #ontology #source code #using: Recovering traceability links between a simple natural language sentence and source code using domain ontologies (TY, SH, MS), pp. 551–554.
WCRE-1999-CapobiancoLOPP99a #analysis #using: Traceability Recovery Using Numerical Analysis (GC, ADL, RO, AP, SP), pp. 195–204.
ICALP-v1-2009-Nies: Superhighness and Strong Jump Traceability (AN), pp. 726–737.
ICEIS-J-2009-NollR #concept #using: Concepts-Based Traceability: Using Experiments to Evaluate Traceability Techniques (RPN, MBR), pp. 539–550.
SEKE-2009-KongLLYW #feedback #refinement: A Requirement Traceability Refinement Method Based on Relevance Feedback (LK, JL, YL, YY, QW), pp. 37–42.
ECMDA-FA-2009-MaderGP #automation #maintenance: Enabling Automated Traceability Maintenance through the Upkeep of Traceability Relations (PM, OG, IP), pp. 174–189.
RE-2009-MaderGP #matter #motivation: Motivation Matters in the Traceability Trenches (PM, OG, IP), pp. 143–148.
RE-2009-OmoronyiaSRFW #case study #developer #navigation #source code: Use Case to Source Code Traceability: The Developer Navigation View Point (IO, GS, MR, JDF, MW), pp. 237–242.
ASE-2009-DenneyF #approach #documentation: A Verification-Driven Approach to Traceability and Documentation for Auto-Generated Mathematical Software (ED, BF), pp. 560–564.
CASE-2009-RamanathanRR: Achieving “handoff” traceability of complex system improvement (JR, RR, SR), pp. 641–646.
CSMR-2008-Oliveto #information retrieval: Traceability Management meets Information Retrieval Methods “Strengths and Limitations” (RO), pp. 302–305.
ICPC-2008-AbadiNS #specification: A Traceability Technique for Specifications (AA, MN, YS), pp. 103–112.
ICSM-2008-Inoue #maintenance: Software tag for traceability and transparency of maintenance (KI), pp. 476–477.
ICSM-2008-YuJM #maintenance: Traceability for the maintenance of secure software (YY, JJ, JM), pp. 297–306.
CAiSE-2008-SienaMLKPS #case study #effectiveness #modelling: Exploring the Effectiveness of Normative i* Modelling: Results from a Case Study on Food Chain Traceability (AS, NAMM, JL, IKK, AP, AS), pp. 182–196.
ICEIS-ISAS2-2008-ParvathyVB #analysis #case study #comparative #correlation #documentation: A Comparative Study of Document Correlation Techniques for Traceability Analysis (AGP, BGV, RB), pp. 64–69.
SEKE-2008-AssawamekinSP #automation #multi #ontology #requirements #using: Automated Multiperspective Requirements Traceability Using Ontology Matching Technique (NA, TS, CP), pp. 460–465.
SEKE-2008-TabaresAMAA #development #modelling: Traceability Models to Control an Aspectual Model-driven Development (MST, RA, AMDM, JA, FAI), pp. 399–404.
RE-2008-MaderGKP #automation #maintenance #named: traceMaintainer — Automated Traceability Maintenance (PM, OG, TK, IP), pp. 329–330.
RE-2008-MaderGP #maintenance #rule-based: Rule-Based Maintenance of Post-Requirements Traceability Relations (PM, OG, IP), pp. 23–32.
REFSQ-2008-GotelM: Macro-level Traceability Via Media Transformations (OG, SJM), pp. 129–134.
ASE-2008-JiangNCJC #automation #evolution #incremental #semantics: Incremental Latent Semantic Indexing for Automatic Traceability Link Evolution Management (HJ, TNN, IXC, HJ, CKC), pp. 59–68.
ASE-2008-LuciaOT #comparison #empirical #incremental #process: IR-Based Traceability Recovery Processes: An Empirical Comparison of “One-Shot” and Incremental Processes (ADL, RO, GT), pp. 39–48.
ASE-2008-MaderGP #automation #development #maintenance #modelling #process: Enabling Automated Traceability Maintenance by Recognizing Development Activities Applied to Models (PM, OG, IP), pp. 49–58.
ASE-2008-YuJS #development #tool support: Tools for Traceability in Secure Software Development (YY, JJ, JS), pp. 503–504.
ICSE-2008-LuciaOT #semantics: Adams re-trace: traceability link recovery via latent semantic indexing (ADL, RO, GT), pp. 839–842.
SAC-2008-FilhoZ: Traceability and completeness checking for agent-oriented systems (GACF, AZ), pp. 71–77.
ATEM-J-2006-ZhangWRH #approach #ontology #semantics: Ontological approach for the semantic recovery of traceability links between software artefacts (YZ, RW, JR, VH), pp. 185–203.
SLE-2008-DrivalosKPF #domain-specific language: Engineering a DSL for Software Traceability (ND, DSK, RFP, KJF), pp. 151–167.
QoSA-2007-MaderPR #process: Customizing Traceability Links for the Unified Process (PM, IP, MR), pp. 53–71.
ICPC-2007-KagdiMS #mining #repository: Mining Software Repositories for Traceability Links (HHK, JIM, BS), pp. 145–154.
ICSM-2007-OlivetoAMH #challenge: Software Artefact Traceability: the Never-Ending Challenge (RO, GA, AM, JHH), pp. 485–488.
CAiSE-2007-BlaauboerSA #requirements: Deciding to Adopt Requirements Traceability in Practice (FB, KS, MNA), pp. 294–308.
EDOC-2007-GalvaoG #modelling #overview: Survey of Traceability Approaches in Model-Driven Engineering (IG, AG), pp. 313–326.
ICEIS-DISI-2007-BlaszkowskaPW #case study: Logistics traceability for supply chain improvement — case study of SMMART project (PB, JP, MW), pp. 599–604.
SEKE-2007-FilhoZ #design #modelling: Traceability for Agent-Oriented Design Models and Code (GACF, AZ), pp. 552–558.
ECMDA-FA-2007-OlsenO #model-to-text: Scenarios of Traceability in Model to Text Transformations (GKO, JO), pp. 144–156.
RE-2007-EgyedGHB #lessons learnt #requirements: Value-Based Requirements Traceability: Lessons Learned (AE, PG, MH, SB), pp. 115–118.
ASE-2007-DagenaisBWR #evolution: Inferring structural patterns for concern traceability in evolving software (BD, SB, FWW, MPR), pp. 254–263.
ASE-2007-NaslavskyR #modelling #testing #using: Using traceability to support model-based regression testing (LN, DJR), pp. 567–570.
ESEC-FSE-2007-AsuncionFT #industrial: An end-to-end industrial software traceability tool (HUA, FF, RNT), pp. 115–124.
ESEC-FSE-2007-GrechanikMP #using: Recovering and using use-case-diagram-to-source-code traceability links (MG, KSM, DEP), pp. 95–104.
SAC-2007-NollR #ontology #using: Enhancing traceability using ontologies (RPN, MBR), pp. 1496–1497.
A-MOST-2007-NaslavskyZR #modelling #testing #towards: Towards traceability of model-based testing artifacts (LN, HZ, DJR), pp. 105–114.
CSMR-2006-LormansD #design #question #requirements: Can LSI help Reconstructing Requirements Traceability in Design and Test? (ML, AvD), pp. 47–56.
ICPC-2006-LuciaFOT #effectiveness #information retrieval #question: Can Information Retrieval Techniques Effectively Support Traceability Link Recovery? (ADL, FF, RO, GT), pp. 307–316.
ICPC-2006-LuciaOZP #empirical #information management #source code: Improving Comprehensibility of Source Code via Traceability Information: a Controlled Experiment (ADL, RO, FZ, MDP), pp. 317–326.
ICSM-2006-LuciaOS #approach #incremental: Incremental Approach and User Feedbacks: a Silver Bullet for Traceability Recovery (ADL, RO, PS), pp. 299–309.
ICSM-2006-LuciaPOZ #comprehension #named #using: COCONUT: COde COmprehension Nurturant Using Traceability (ADL, MDP, RO, FZ), pp. 274–275.
EDOC-2006-AlmeidaEI #consistency #development #modelling #requirements: Requirements Traceability and Transformation Conformance in Model-Driven Development (JPAA, PvE, MEI), pp. 355–366.
EDOC-2006-GorpAJ #2d #consistency #contract #framework #nondeterminism #platform #towards #visual notation: Towards 2D Traceability in a Platform for Contract Aware Visual Transformations with Tolerated Inconsistencies (PVG, FA, DJ), pp. 185–198.
ICEIS-AIDSS-2006-RosaGPSMLP: Frequency Calibrations with Conventional Time Interval Counters via GPS Traceability (JJGdlR, ILG, CGP, JMGS, AMM, MLR, VP), pp. 189–201.
RE-2006-ArkleyRB #information management: Tailoring Traceability Information to Business Needs (PA, SR, TB), pp. 234–239.
RE-2006-Cleland-Huang #delivery #how #question #requirements: Requirements Traceability — When and How does it Deliver more than it Costs? (JCH), p. 323.
RE-2006-LinLCSABBKDZ #automation #distributed #named #tool support: Poirot: A Distributed Tool Supporting Enterprise-Wide Automated Traceability (JL, CCL, JCH, RS, JA, GB, BB, OBK, CD, XZ), pp. 356–357.
ASE-2006-MurtaHW #architecture #evolution #implementation #named: ArchTrace: Policy-Based Support for Managing Evolving Architecture-to-Implementation Traceability Links (LGPM, AvdH, CMLW), pp. 135–144.
ASE-2006-NeumullerG #automation #case study #lessons learnt: Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learned (CN, PG), pp. 145–156.
CSMR-2005-LuciaFOT: ADAMS Re-Trace: A Traceability Recovery Tool (ADL, FF, RO, GT), pp. 32–41.
ECMDA-FA-2005-BoronatCR #automation #framework #model management: Automatic Support for Traceability in a Generic Model Management Framework (AB, JÁC, IR), pp. 316–330.
RE-2005-ArkleyR #problem: Overcoming the Traceability Benefit Problem (PA, SR), pp. 385–389.
RE-2005-Cleland-HuangSDZ #requirements: Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability (JCH, RS, CD, XZ), pp. 135–144.
ASE-2005-EgyedBHG #automation #trade-off: Determining the cost-quality trade-off for automated software traceability (AE, SB, MH, PG), pp. 360–363.
ICSE-2005-Cleland-HuangSKBC #non-functional #requirements: Goal-centric traceability for managing non-functional requirements (JCH, RS, OBK, EB, SC), pp. 362–371.
A-MOST-2005-BouquetJLPU #automation #generative #requirements #smarttech #testing #validation: Requirements traceability in automated test generation: application to smart card software validation (FB, EJ, BL, FP, MU), pp. 44–50.
ICSM-2004-LuciaFOT: Enhancing an Artefact Management System with Traceability Recovery Features (ADL, FF, RO, GT), pp. 306–315.
CIKM-2004-MasonCV #on the: On structuring formal, semi-formal and informal data to support traceability in systems engineering environments (PM, KC, PV), pp. 642–651.
SEKE-2004-NguyenMT #hypermedia #version control: Software Traceability via Versioned Hypermedia (TNN, EVM, CT), pp. 288–293.
RE-2004-Cleland-HuangZL #requirements: A Heterogeneous Solution for Improving the Return on Investment of Requirements Traceability (JCH, GZ, WL), pp. 230–239.
ASE-2004-RichardsonG #automation: Automating Traceability for Generated Software Artifacts (JR, JG), pp. 24–33.
SEKE-2003-MeshkatFC: Traceability and Decision Capture in Semi-structured Contexts (LM, MSF, SLC), pp. 647–654.
SEKE-2003-RichterAMF #information management: Tagging Knowledge Acquisition Sessions to Facilitate Knowledge Traceability (HR, GDA, CAM, HF), pp. 432–439.
SEKE-2003-SpanoudakisGZ #approach #machine learning #requirements: Revising Rules to Capture Requirements Traceability Relations: A Machine Learning Approach (GS, ASdG, AZ), pp. 570–577.
RE-2003-Becker #lifecycle #multi #requirements: Measuring Requirements Traceability from Multiple Angels at Multiple Lifecycle Entry Points (DB), p. 291.
RE-2003-JarkeFMS #process #requirements: Media-Assisted Product and Process Requirements Traceability in Supply Chains (MJ, OF, MM, MS), pp. 375–376.
RE-2003-Romanski #configuration management #requirements #safety: Requirements, Configuration Management and Traceability for Safety Critical Software (GR), p. 304.
ICSE-2003-MarcusM #semantics #using: Recovering Documentation-to-Source-Code Traceability Links using Latent Semantic Indexing (AM, JIM), pp. 125–137.
ICSM-2002-Knethen #embedded #evolution #requirements: Change-Oriented Requirements Traceability: Support for Evolution of Embedded Systems (AvK), pp. 482–485.
IWPC-2002-PentaGA: Traceability Recovery in RAD Software Systems (MDP, SG, GA), pp. 207–216.
SEKE-2002-Spanoudakis #adaptation: Plausible and adaptive requirement traceability structures (GS), pp. 135–142.
RE-2002-Cleland-HuangCSJHX #automation #query #requirements: Automating Speculative Queries through Event-Based Requirements Traceability (JCH, CKC, GS, KJ, HH, JX), pp. 289–298.
RE-2002-KnethenPKH #abstraction #requirements: Systematic Requirements Recycling through Abstraction and Traceability (AvK, BP, FK, FH), pp. 273–281.
ASE-2002-EgyedG #automation #paradigm #requirements: Automating Requirements Traceability: Beyond the Record & Replay Paradigm (AE, PG), pp. 163–171.
IWPC-J-1999-AntoniolCPT01: Design-code traceability recovery: selecting the basic linkage properties (GA, BC, AP, PT), pp. 213–234.
RE-2001-DorfmanC #experience #industrial #requirements: Early Experience with Requirements Traceability in an Industrial Environment (MD, RC), p. 265.
ICSE-2001-Egyed #approach: A Scenario-Driven Approach to Traceability (AE), pp. 123–132.
ICSE-2001-Streitferdt #product line: Traceability for System Families (DS), pp. 803–804.
FoSSaCS-2001-Morin #on the #sequence chart: On Regular Message Sequence Chart Languages and Relationships to Mazurkiewicz Trace Theory (RM), pp. 332–346.
ICSM-2000-AntoniolCCL #documentation #information retrieval #modelling: Information Retrieval Models for Recovering Traceability Links between Code and Documentation (GA, GC, GC, ADL), p. 40–?.
IWPC-2000-BianchiVF #case study #effectiveness #maintenance #modelling: An Exploratory Case Study of the Maintenance Effectiveness of Traceability Models (AB, GV, ARF), pp. 149–158.
WCRE-2000-AntoniolCC #behaviour #modelling: Traceability Recovery by Modeling Programmer Behavior (GA, GC, AC), pp. 240–247.
ICSM-1999-AntoniolCL #case study #evolution #maintenance #object-oriented: Maintaining Traceability During Object-Oriented Software Evolution: A Case Study (GA, GC, ADL), pp. 211–219.
IWPC-1999-AntoniolPTF #design #evolution #object-oriented: Evolving Object Oriented Design to Improve Code Traceability (GA, AP, PT, RF), pp. 151–160.
ICSM-1997-TryggesethN #architecture: Dynamic Traceability Links Supported by a System Architecture Description (ET, ØN), pp. 180–187.
RE-1997-FinkelsteinS #requirements: Requirements Traceability (AF, RS), p. 265.
RE-1997-GotelF #case study #industrial #requirements: Extended Requirements Traceability: Results of an Industrial Case Study (OG, AF), p. 169–?.
WPC-1996-BoldyreffBHMY #comprehension #maintenance: Greater Understanding Through Maintainer Driven Traceability (CB, EB, RMH, MM, EJY), p. 100–?.
DLT-1995-DiekertGP: Recent Developments in Trace Theory (VD, PG, AP), pp. 373–385.
RE-1995-MacfarlaneR #development #ide #requirements: Requirements traceability in an integrated development environment (IAM, IR), pp. 116–127.
RE-1995-RameshPSE #case study #implementation #requirements: Implementing requirements traceability: a case study (BR, TP, CS, ME), pp. 89–99.
TOOLS-EUROPE-1994-Barbier #lifecycle #object-oriented: Traceability in the Object-Oriented Software Life Cycle (FB), pp. 293–301.
ICRE-1994-GotelF #analysis #problem #requirements: An analysis of the requirements traceability problem (OCZG, AF), pp. 94–101.
RE-1993-RameshE #development #requirements: Issues in the development of a requirements traceability model (BR, ME), pp. 256–259.