default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDLucas Layman
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
[j10]Lucas Layman
, Ron Vetter:
Generative Artificial Intelligence and the Future of Software Testing. Computer 57(1): 27-32 (2024)- 2023
- [i5]Lucas Layman, William Roden:
A Controlled Experiment on the Impact of Intrusion Detection False Alarm Rate on Analyst Performance. CoRR abs/2307.07023 (2023) - 2020
- [c31]Lucas Layman, Yang Song, Curry I. Guinn:
Toward Predicting Success and Failure in CS2: A Mixed-Method Analysis. ACM Southeast Regional Conference 2020: 218-225 - [c30]William Roden, Lucas Layman:
Cry Wolf: Toward an Experimentation Platform and Dataset for Human Factors in Cyber Security Analysis. ACM Southeast Regional Conference 2020: 264-267 - [c29]Yang Song, Yunkai Xiao, Jonathan Stephens, Emma Ruesch, Sean Roginski, Lucas Layman:
Suitability of SCS1 as a Pre-CS2 Assessment Instrument: A Comparison with Short Deliberate-practice Questions. ACM Southeast Regional Conference 2020: 313-314 - [i4]William Roden, Lucas Layman:
Cry Wolf: Toward an Experimentation Platform and Dataset for Human Factors in Cyber Security Analysis. CoRR abs/2002.10530 (2020) - [i3]Lucas Layman, Yang Song, Curry I. Guinn:
Toward Predicting Success and Failure in CS2: A Mixed-Method Analysis. CoRR abs/2002.11813 (2020)
2010 – 2019
- 2019
- [j9]Carl Sabottke, Daniel Chen, Lucas Layman, Tudor Dumitras:
How to trick the Borg: threat models against manual and automated techniques for detecting network attacks. Comput. Secur. 81: 25-40 (2019) - 2017
- [j8]Tim Menzies, William Nichols, Forrest Shull, Lucas Layman:
Are delayed issues harder to resolve? Revisiting cost-to-fix of defects throughout the lifecycle. Empir. Softw. Eng. 22(4): 1903-1935 (2017) - [j7]Rahul Krishna, Tim Menzies, Lucas Layman:
Less is more: Minimizing code reorganization using XTREE. Inf. Softw. Technol. 88: 53-66 (2017) - 2016
- [c28]Lucas Layman, Allen P. Nikora, Joshua Meek, Tim Menzies:
Topic modeling of NASA space system problem reports: research in practice. MSR 2016: 303-314 - [i2]Rahul Krishna, Tim Menzies, Lucas Layman:
Recommendations for Intelligent Code Reorganization. CoRR abs/1609.03614 (2016) - [i1]Tim Menzies, William Nichols, Forrest Shull, Lucas Layman:
Are Delayed Issues Harder to Resolve? Revisiting Cost-to-Fix of Defects throughout the Lifecycle. CoRR abs/1609.04886 (2016) - 2015
- [c27]Lucas Layman, Carolyn B. Seaman, Davide Falessi, Madeline Diep:
Ask the Engineers: Exploring Repertory Grids and Personal Constructs for Software Data Analysis. CHASE@ICSE 2015: 81-84 - [c26]Fayola Peters, Tim Menzies, Lucas Layman:
LACE2: Better Privacy-Preserving Data Sharing for Cross Project Defect Prediction. ICSE (1) 2015: 801-811 - [p2]Madeline Diep, Linda Esker, Davide Falessi, Lucas Layman, Michele A. Shaw, Forrest Shull:
Applying Software Data Analysis in Industry Contexts. The Art and Science of Analyzing Software Data 2015: 327-348 - 2014
- [j6]Lucas Layman, Victor R. Basili, Marvin V. Zelkowitz:
A Methodology for Exposing Risk in Achieving Emergent System Properties. ACM Trans. Softw. Eng. Methodol. 23(3): 22:1-22:28 (2014) - [c25]Lucas Layman, Sylvain David Diffo, Nico Zazworka:
Human factors in webserver log file analysis: a controlled experiment on investigating malicious activity. HotSoS 2014: 9 - [c24]Lucas Layman, Nico Zazworka:
InViz: instant visualization of security attacks. HotSoS 2014: 15 - 2013
- [j5]Tim Menzies, Andrew Butcher, David R. Cok, Andrian Marcus, Lucas Layman, Forrest Shull, Burak Turhan, Thomas Zimmermann:
Local versus Global Lessons for Defect Prediction and Effort Estimation. IEEE Trans. Software Eng. 39(6): 822-834 (2013) - [c23]Forrest Shull, Davide Falessi, Carolyn B. Seaman, Madeline Diep, Lucas Layman:
Technical Debt: Showing the Way for Better Transfer of Empirical Results. Perspectives on the Future of Software Engineering 2013: 179-190 - [c22]Lucas Layman, Gunnar Sigurdsson:
Using Amazon's Mechanical Turk for User Studies: Eight Things You Need to Know. ESEM 2013: 275-278 - [c21]Lucas Layman, Madeline Diep, Meiyappan Nagappan, Janice Singer, Robert DeLine, Gina Venolia:
Debugging Revisited: Toward Understanding the Debugging Needs of Contemporary Software Developers. ESEM 2013: 383-392 - [c20]Davide Falessi, Lucas Layman:
Automated classification of NASA anomalies using natural language processing techniques. ISSRE (Supplemental Proceedings) 2013: 5-6 - 2012
- [c19]Lucas Layman, Marvin V. Zelkowitz, Victor R. Basili, Allen P. Nikora:
Toward Baselining Software Anomalies in NASA Missions. ISSRE Workshops 2012: 13-14 - 2011
- [c18]Lucas Layman, Victor R. Basili, Marvin V. Zelkowitz, Karen L. Fisher:
A case study of measuring process risk for early insights into software safety. ICSE 2011: 623-632 - [p1]Burak Turhan, Lucas Layman, Madeline Diep, Hakan Erdogmus, Forrest Shull:
How Effective Is Test-Driven Development? Making Software 2011: 207-220 - 2010
- [j4]Forrest Shull, Grigori Melnik, Burak Turhan, Lucas Layman, Madeline Diep, Hakan Erdogmus:
What Do We Know about Test-Driven Development? IEEE Softw. 27(6): 16-19 (2010) - [c17]Victor R. Basili, Marvin V. Zelkowitz, Lucas Layman, Kathleen Coleman Dangle, Madeline Diep:
Obtaining valid safety data for software safety measurement and process improvement. ESEM 2010
2000 – 2009
- 2009
- [c16]Andrew Begel, Nachiappan Nagappan, Christopher Poile, Lucas Layman:
Coordination in large-scale software teams. CHASE 2009: 1-7 - 2008
- [c15]Laurie A. Williams, D. Scott McCrickard, Lucas Layman, Khaled Hussein:
Eleven Guidelines for Implementing Pair Programming in the Classroom. AGILE 2008: 445-452 - [c14]Lucas Layman, Gunnar Kudrjavets, Nachiappan Nagappan:
Iterative identification of fault-prone binaries using in-process metrics. ESEM 2008: 206-212 - [c13]Lucas Layman, Laurie A. Williams, Robert St. Amant:
MimEc: intelligent user notification of faults in the eclipse IDE. CHASE 2008: 73-76 - [c12]Lucas Layman, Nachiappan Nagappan, Sam Guckenheimer, Jeff Beehler, Andrew Begel:
Mining software effort data: preliminary analysis of visual studio team system data. MSR 2008: 43-46 - 2007
- [c11]Laurie A. Williams, Lucas Layman:
Lab Partners: If They're Good Enough for the Natural Sciences, Why Aren't They Good Enough for Us? CSEE&T 2007: 72-82 - [c10]Lucas Layman, Laurie A. Williams, Robert St. Amant:
Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools. ESEM 2007: 176-185 - [c9]Laurie A. Williams, Lucas Layman, Kelli M. Slaten, Sarah B. Berenson, Carolyn B. Seaman:
On the Impact of a Collaborative Pedagogy on African American Millennial Students in Software Engineering. ICSE 2007: 677-687 - [c8]Lucas Layman, Laurie A. Williams, Kelli M. Slaten:
Note to self: make assignments meaningful. SIGCSE 2007: 459-463 - 2006
- [j3]Lucas Layman, Laurie A. Williams, Daniela E. Damian, Hynek Bures:
Essential communication practices for Extreme Programming in a global software development team. Inf. Softw. Technol. 48(9): 781-794 (2006) - [j2]Lucas Layman, Laurie A. Williams, Lynn Cunningham:
Motivations and measurements in an agile case study. J. Syst. Archit. 52(11): 654-667 (2006) - [c7]Laurie A. Williams, Lucas Layman, Jason A. Osborne, Neha Katira:
Examining the Compatibility of Student Pair Programmers. AGILE 2006: 411-420 - [c6]Lucas Layman:
Changing Students' Perceptions: An Analysis of the Supplementary Benefits of Collaborative Software Development. CSEE&T 2006: 159-166 - [c5]Lucas Layman, Travis Cornwell, Laurie A. Williams:
Personality types, learning styles, and an agile approach to software engineering education. SIGCSE 2006: 428-432 - 2005
- [j1]Laurie A. Williams, Lucas Layman, Pekka Abrahamsson:
On establishing the essential components of a technology-dependent framework: a strawman framework for industrial case study-based research. ACM SIGSOFT Softw. Eng. Notes 30(4): 1-5 (2005) - [c4]Kelli M. Slaten, Sarah B. Berenson, Laurie A. Williams, Lucas Layman, Maria A. Droujkova:
Undergraduate Student Perceptions of Pair Programming and Agile Software Methodologies: Verifying a Model of Social Interaction. AGILE 2005: 323-330 - 2004
- [c3]Lucas Layman, Laurie A. Williams, Lynn Cunningham:
Exploring Extreme Programming in Context: An Industrial Case Study. Agile Development Conference 2004: 32-41 - [c2]Lucas Layman:
Empirical investigation of the impact of extreme programming practices on software projects. OOPSLA Companion 2004: 328-329 - 2003
- [c1]Keith B. Gallagher, Lucas Layman:
Are Decomposition Slices Clones?. IWPC 2003: 251-257
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 23:05 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
