( en | de | ru )

 

Disambiguation of "Williams, Laurie A."

Author of the publication

copydeleteadd this publication to your clipboard
Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools.

, , and . ESEM, page 176-185. ACM / IEEE Computer Society, (2007)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

Laurie Koehler

Laurie Serrano

Laurie Brink

Simone Williams

Benjamin Williams

 

Other publications of authors with the same name

Experiments with Industry's "Pair-Programming" Model in the Computer Science Classroom., and . Computer Science Education, 11 (1): 7-20 (2001)Experiences in applying agile software development practices in new product development., , , , and . IASTED Conf. on Software Engineering and Applications, page 501-506. IASTED/ACTA Press, (2004)How have we evaluated software pattern application? A systematic mapping study of research design practices., , and . Inf. Softw. Technol., (2015)Towards improved security criteria for certification of electronic health record systems., , and . SEHC@ICSE, page 68-73. ACM, (2010)Strengthening the Case for Pair Programming., , , and . IEEE Software, 17 (4): 19-25 (2000)Empirical Findings in Agile Methods., , , , , , , , and . XP/Agile Universe, volume 2418 of Lecture Notes in Computer Science, page 197-207. Springer, (2002)Pair Programming: Experience the Difference., and . XP/Agile Universe, volume 2418 of Lecture Notes in Computer Science, page 271-272. Springer, (2002)Early estimation of defect density using an in-process Haskell metrics model., , , and . ACM SIGSOFT Softw. Eng. Notes, 30 (4): 1-6 (2005)Identifying the implied: Findings from three differentiated replications on the use of security requirements templates., , , , , , and . Empir. Softw. Eng., 22 (4): 2127-2178 (2017)To log, or not to log: using heuristics to identify mandatory log events - a controlled experiment., , , and . Empir. Softw. Eng., 22 (5): 2684-2717 (2017)