default search action
Andrew Meneely
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
- [c30]Benjamin S. Meyers, Andrew Meneely:
Taxonomy-Based Human Error Assessment for Senior Software Engineering Students. SIGCSE (1) 2024: 840-846 - 2023
- [c29]Brandon N. Keller, Benjamin S. Meyers, Andrew Meneely:
What Happens When We Fuzz? Investigating OSS-Fuzz Bug History. MSR 2023: 207-217 - [i2]Brandon N. Keller, Andrew Meneely, Benjamin S. Meyers:
What Happens When We Fuzz? Investigating OSS-Fuzz Bug History. CoRR abs/2305.11433 (2023) - 2022
- [j8]Benjamin S. Meyers, Sultan Fahad Almassari, Brandon N. Keller, Andrew Meneely:
Examining Penetration Tester Behavior in the Collegiate Penetration Testing Competition. ACM Trans. Softw. Eng. Methodol. 31(3): 55:1-55:25 (2022) - 2021
- [c28]Benjamin S. Meyers, Andrew Meneely:
An Automated Post-Mortem Analysis of Vulnerability Relationships using Natural Language Word Embeddings. ANT/EDI40 2021: 953-958 - [c27]Nikolaos Alexopoulos, Andrew Meneely, Dorian Arnouts, Max Mühlhäuser:
Who are Vulnerability Reporters?: A Large-scale Empirical Study on FLOSS. ESEM 2021: 25:1-25:12
2010 – 2019
- 2019
- [c26]Nuthan Munaiah, Akond Rahman, Justin Pelletier, Laurie A. Williams, Andrew Meneely:
Characterizing Attacker Behavior in a Cybersecurity Penetration Testing Competition. ESEM 2019: 1-6 - [c25]Nuthan Munaiah, Andrew Meneely:
Data-driven insights from vulnerability discovery metrics. RCoSE-DDrEE@ICSE 2019: 1-7 - [c24]Benjamin S. Meyers, Nuthan Munaiah, Andrew Meneely, Emily Prud'hommeaux:
Pragmatic characteristics of security conversations: an exploratory linguistic analysis. CHASE@ICSE 2019: 79-82 - [i1]Nuthan Munaiah, Andrew Meneely:
Systematization of Vulnerability Discovery Knowledge: Review Protocol. CoRR abs/1902.03331 (2019) - 2018
- [j7]Christopher Theisen, Nuthan Munaiah, Mahran Al-Zyoud, Jeffrey C. Carver, Andrew Meneely, Laurie A. Williams:
Attack surface definitions: A systematic literature review. Inf. Softw. Technol. 104: 94-103 (2018) - [c23]Benjamin S. Meyers, Nuthan Munaiah, Emily Prud'hommeaux, Andrew Meneely, Josephine Wolff, Cecilia Ovesdotter Alm, Pradeep K. Murukannaiah:
A dataset for identifying actionable feedback in collaborative software development. ACL (2) 2018: 126-131 - 2017
- [j6]Nuthan Munaiah, Felivel Camilo, Wesley Wigham, Andrew Meneely, Meiyappan Nagappan:
Do bugs foreshadow vulnerabilities? An in-depth study of the chromium project. Empir. Softw. Eng. 22(3): 1305-1347 (2017) - [c22]Nuthan Munaiah, Benjamin S. Meyers, Cecilia Ovesdotter Alm, Andrew Meneely, Pradeep K. Murukannaiah, Emily Prud'hommeaux, Josephine Wolff, Yang Yu:
Natural Language Insights from Code Reviews that Missed a Vulnerability - A Large Scale Study of Chromium. ESSoS 2017: 70-86 - [c21]Nuthan Munaiah, Andrew Meneely, Pradeep K. Murukannaiah:
A Domain-Independent Model for Identifying Security Requirements. RE 2017: 506-511 - 2016
- [c20]Nuthan Munaiah, Andrew Meneely:
Beyond the Attack Surface: Assessing Security Risk with Random Walks on Call Graphs. SPRO@CCS 2016: 3-14 - [c19]Daniel E. Krutz, Nuthan Munaiah, Andrew Meneely, Samuel A. Malachowsky:
Examining the relationship between security metrics and user ratings of mobile apps: a case study. WAMA@SIGSOFT FSE 2016: 8-14 - [c18]Nuthan Munaiah, Andrew Meneely:
Vulnerability severity scoring and bounties: why the disconnect? SWAN@SIGSOFT FSE 2016: 8-14 - [c17]Iván Tactuk Mercado, Nuthan Munaiah, Andrew Meneely:
The impact of cross-platform development approaches for mobile applications from the user's perspective. WAMA@SIGSOFT FSE 2016: 43-49 - [p3]Andrew Meneely:
Security cannot be measured. Perspectives on Data Science for Software Engineering 2016: 255-259 - [p2]Andrew Meneely:
Actionable metrics are better metrics. Perspectives on Data Science for Software Engineering 2016: 283-287 - 2015
- [c16]Daniel E. Krutz, Andrew Meneely, Samuel A. Malachowsky:
An insider threat activity in a software security course. FIE 2015: 1-6 - [c15]Felivel Camilo, Andrew Meneely, Meiyappan Nagappan:
Do Bugs Foreshadow Vulnerabilities? A Study of the Chromium Project. MSR 2015: 269-279 - [p1]Andrew Meneely:
Analyzing Security Data. The Art and Science of Analyzing Software Data 2015: 215-229 - 2014
- [c14]Andrew Meneely, Alberto Rodriguez Tejeda, Brian Spates, Shannon Trudeau, Danielle Neuberger, Katherine Whitlock, Christopher Ketant, Kayla Davis:
An empirical investigation of socio-technical code review metrics and security vulnerabilities. SSE@SIGSOFT FSE 2014: 37-44 - 2013
- [c13]Andrew Meneely, Harshavardhan Srinivasan, Ayemi Musa, Alberto Rodriguez Tejeda, Matthew Mokary, Brian Spates:
When a Patch Goes Bad: Exploring the Properties of Vulnerability-Contributing Commits. ESEM 2013: 65-74 - [c12]Daniel E. Krutz, Andrew Meneely:
Teaching Web Engineering using a project component. FIE 2013: 1366-1368 - [c11]Andrew Meneely, Samuel Lucidi:
Vulnerability of the day: concrete demonstrations for software engineering undergraduates. ICSE 2013: 1154-1157 - 2012
- [j5]Andrew Meneely, Oluyinka Williams:
Interactive churn metrics: socio-technical variants of code churn. ACM SIGSOFT Softw. Eng. Notes 37(6): 1-6 (2012) - [j4]Andrew Meneely, Ben H. Smith, Laurie A. Williams:
Validating software metrics: A spectrum of philosophies. ACM Trans. Softw. Eng. Methodol. 21(4): 24:1-24:28 (2012) - 2011
- [j3]Yonghee Shin, Andrew Meneely, Laurie A. Williams, Jason A. Osborne:
Evaluating Complexity, Code Churn, and Developer Activity Metrics as Indicators of Software Vulnerabilities. IEEE Trans. Software Eng. 37(6): 772-787 (2011) - [c10]Andrew Meneely, Laurie A. Williams:
Socio-technical developer networks: should we trust our measurements? ICSE 2011: 281-290 - [c9]Andrew Meneely, Pete Rotella, Laurie A. Williams:
Does adding manpower also affect quality?: an empirical, longitudinal analysis. SIGSOFT FSE 2011: 81-90 - 2010
- [j2]Andrew Meneely, Laurie A. Williams:
On the Use of Issue Tracking Annotations for Improving Developer Activity Metrics. Adv. Softw. Eng. 2010: 273080:1-273080:9 (2010) - [j1]Laurie A. Williams, Andrew Meneely, Grant Shipley:
Protection Poker: The New Software Security "Game";. IEEE Secur. Priv. 8(3): 14-20 (2010) - [c8]Andrew Meneely, Laurie A. Williams:
Strengthening the empirical analysis of the relationship between Linus' Law and software security. ESEM 2010 - [c7]Andrew Meneely, Mackenzie Corcoran, Laurie A. Williams:
Improving developer activity metrics with issue tracking annotations. WETSoM 2010: 75-80
2000 – 2009
- 2009
- [c6]Andrew Meneely, Laurie A. Williams:
Secure open source collaboration: an empirical study of linus' law. CCS 2009: 453-462 - [c5]Laurie A. Williams, Michael Gegick, Andrew Meneely:
Protection Poker: Structuring Software Security Risk Assessment and Knowledge Transfer. ESSoS 2009: 122-134 - [c4]Andrew Meneely, Laurie A. Williams:
On preparing students for distributed software development with a synchronous, collaborative development platform. SIGCSE 2009: 529-533 - 2008
- [c3]Andrew Meneely, Laurie A. Williams, Edward F. Gehringer:
ROSE: a repository of education-friendly open-source projects. ITiCSE 2008: 7-11 - [c2]Andrew Meneely, Laurie A. Williams, Will Snipes, Jason A. Osborne:
Predicting failures with developer networks and social network analysis. SIGSOFT FSE 2008: 13-23 - 2006
- [c1]Jeremy D. Frens, Andrew Meneely:
Fifteen compilers in fifteen days. SIGCSE 2006: 92-96
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-24 22:54 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint