• case-insensitive prefix search: default
  e.g., sig matches "SIGIR" as well as "signal"
• exact word search: append dollar sign ($) to word
  e.g., graph$ matches "graph", but not "graphics"
• boolean and: separate words by space
  e.g., codd model
• boolean or: connect words by pipe symbol (|)
  e.g., graph|network

Update May 7, 2017: Please note that we had to disable the phrase search operator (.) and the boolean not operator (-) due to technical problems. For the time being, phrase search queries will yield regular prefix search result, and search terms preceded by a minus will be interpreted as regular (positive) search terms.

found 38 matches

• 2020
• 
  Amjed Tahir, Jens Dietrich, Steve Counsell, Sherlock A. Licorish, Aiko Yamashita:
  A large scale study on how developers discuss code smells and anti-pattern in Stack Exchange sites. Inf. Softw. Technol. 125: 106333 (2020)
• 2018
• 
  Amjed Tahir, Aiko Yamashita, Sherlock A. Licorish, Jens Dietrich, Steve Counsell:
  Can you tell me if it smells?: A study on how developers discuss code smells and anti-patterns in Stack Overflow. EASE 2018: 68-78
• 
  Aiko Yamashita, Fábio Petrillo, Foutse Khomh, Yann-Gaël Guéhéneuc:
  Developer interaction traces backed by IDE screen recordings from think aloud sessions. MSR 2018: 50-53
• 2017
• 
  Jeffrey C. Carver, Henry Muccini, Aiko Yamashita:
  Distributed Teams, Developer Participation, and More. IEEE Softw. 34(3): 114-116 (2017)
• 
  Jeffrey C. Carver, Birgit Penzenstadler, Alexander Serebrenik, Aiko Yamashita:
  The Human Factor. IEEE Softw. 34(5): 90-92 (2017)
• 
  Aiko Yamashita, Alberto Arribas:
  Influential Factors for Interdisciplinary Software Development Teams in Industrial Settings: The Case of Informatics Lab. CIbSE 2017: 693-704
• 
  Aiko Yamashita, S. Amirhossein Abtahizadeh, Foutse Khomh, Yann-Gaël Guéhéneuc:
  Software evolution and quality data from controlled, multiple, industrial case studies. MSR 2017: 507-510
• 
  Fábio Petrillo, Hyan Mandian, Aiko Yamashita, Foutse Khomh, Yann-Gaël Guéhéneuc:
  How Do Developers Toggle Breakpoints? Observational Studies. QRS 2017: 285-295
• 
  Abhishek Sharma, Yuan Tian, Agus Sulistya, David Lo, Aiko Fallas Yamashita:
  Harnessing Twitter to support serendipitous learning of developers. SANER 2017: 387-391
• 2016
• 
  Magne Jørgensen, Aiko Yamashita:
  Cultural Characteristics and Their Connection to Increased Risk of Software Project Failure. J. Softw. 11(6): 606-614 (2016)
• 
  Aiko Yamashita, Leon Moonen, Tom Mens, Amjed Tahir:
  Report on the First International Workshop on Technical Debt Analytics (TDA 2016). QuASoQ/TDA@APSEC 2016: 58-63
• 
  Mel Ó Cinnéide, Aiko Yamashita, Steve Counsell:
  Measuring refactoring benefits: a survey of the evidence. IWoR@ASE 2016: 9-12
• 
  Francesca Arcelli Fontana, Jens Dietrich, Bartosz Walter, Aiko Yamashita, Marco Zanoni:
  Antipattern and Code Smell False Positives: Preliminary Conceptualization and Classification. SANER 2016: 609-613
• 
  Zéphyrin Soh, Aiko Yamashita, Foutse Khomh, Yann-Gaël Guéhéneuc:
  Do Code Smells Impact the Effort of Different Maintenance Programming Activities? SANER 2016: 393-402
• 
  Horst Lichter, Konrad Fögen, Thanwadee Sunetnanta, Toni Anwar, Aiko Yamashita, Leon Moonen, Tom Mens, Amjed Tahir, Ashish Sureka:
  Joint Proceedings of the 4th International Workshop on Quantitative Approaches to Software Quality (QuASoQ 2016) and 1st International Workshop on Technical Debt Analytics (TDA 2016) co-located with the 23rd Asia-Pacific Software Engineering Conference (APSEC 2016), Hamilton, New Zealand, December 6, 2016. CEUR Workshop Proceedings 1771, CEUR-WS.org 2016 [contents]
• 2015
• 
  Jeffrey C. Carver, Bora Çaglayan, Mayy Habayeb, Birgit Penzenstadler, Aiko Yamashita:
  Collaborations and Code Reviews. IEEE Softw. 32(5): 27-29 (2015)
• 
  Jeffrey C. Carver, Aiko Yamashita, Leandro L. Minku, Mayy Habayeb, Sedef Akinli Koçak:
  Software Quality, Energy Awareness, and More. IEEE Softw. 32(6): 98-100 (2015)
• 
  Francesca Arcelli Fontana, Vincenzo Ferme, Marco Zanoni, Aiko Yamashita:
  Automatic Metric Thresholds Derivation for Code Smell Detection. WETSoM@ICSE 2015: 44-53
• 
  Aiko Yamashita:
  Integration of SE Research and Industry: Reflections, Theories and Illustrative Example. SER&IP@ICSE 2015: 11-17
• 
  Aiko Yamashita:
  Experiences from performing software quality evaluations via combining benchmark-based metrics analysis, software visualization, and expert assessment. ICSME 2015: 421-428
• 
  Aiko Yamashita, Marco Zanoni, Francesca Arcelli Fontana, Bartosz Walter:
  Inter-smell relations in industrial and open source systems: A replication and comparative analysis. ICSME 2015: 121-130
• 2014
• 
  Aiko Yamashita:
  Assessing the capability of code smells to explain maintenance problems: an empirical study combining quantitative and qualitative data. Empir. Softw. Eng. 19(4): 1111-1143 (2014)
• 
  Aiko Fallas Yamashita, Leon Moonen:
  Assembling multiple-case studies: potential, principles and practical considerations. EASE 2014: 36:1-36:10
• 2013
• 
  Aiko Fallas Yamashita, Leon Moonen:
  To what extent can maintenance problems be predicted by code smell detection? - An empirical study. Inf. Softw. Technol. 55(12): 2223-2242 (2013)
• 
  Aiko Yamashita, Steve Counsell:
  Code smells as system-level indicators of maintainability: An empirical study. J. Syst. Softw. 86(10): 2639-2653 (2013)
• 
  Dag I. K. Sjøberg, Aiko Fallas Yamashita, Bente Cecilie Dahlum Anda, Audris Mockus, Tore Dybå:
  Quantifying the Effect of Code Smells on Maintenance Effort. IEEE Trans. Software Eng. 39(8): 1144-1156 (2013)
• 
  Aiko Fallas Yamashita, Leon Moonen:
  Exploring the impact of inter-smell relations on software maintainability: an empirical study. ICSE 2013: 682-691
• 
  Aiko Fallas Yamashita, Leon Moonen:
  Surveying developer knowledge and interest in code smells through online freelance marketplaces. USER@ICSE 2013: 5-8
• 
  Aiko Yamashita:
  How Good Are Code Smells for Evaluating Software Maintainability? Results from a Comparative Case Study. ICSM 2013: 566-571
• 
  Aiko Fallas Yamashita, Leon Moonen:
  Towards a Taxonomy of Programming-Related Difficulties during Maintenance. ICSM 2013: 424-427

skipping 8 more matches