Search the dblp DataBase

Publications of Author

1. Chih-Wei Ho, Michael J. Johnson, Laurie Williams, E. Michael Maximilien
   On Agile Performance Requirements Specification and Testing. [Citation Graph (0, 0)][DBLP]
   AGILE, 2006, pp:47-52 [Conf]
   
2. Laurie Williams, Lucas Layman, Jason Osborne, Neha Katira
   Examining the Compatibility of Student Pair Programmers. [Citation Graph (0, 0)][DBLP]
   AGILE, 2006, pp:411-420 [Conf]
   
3. Kelli M. Slaten, Sarah B. Berenson, Laurie Williams, Lucas Layman, Maria A. Droujkova
   Undergraduate Student Perceptions of Pair Programming and Agile Software Methodologies: Verifying a Model of Social Interaction. [Citation Graph (0, 0)][DBLP]
   AGILE, 2005, pp:323-330 [Conf]
   
4. Jiang Zheng, Brian Robinson, Laurie Williams, Karen Smiley
   Applying regression test selection for COTS-based applications. [Citation Graph (0, 0)][DBLP]
   ICSE, 2006, pp:512-522 [Conf]
   
5. Laurie 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. [Citation Graph (0, 0)][DBLP]
   ICSE, 2007, pp:677-687 [Conf]
   
6. Hema Srikanth, Laurie Williams, Jason Osborne
   System test case prioritization of new and regression test cases. [Citation Graph (0, 0)][DBLP]
   ISESE, 2005, pp:64-73 [Conf]
   
7. Mark Sherriff, Laurie Williams
   DevCOP: A Software Certificate Management System for Eclipse. [Citation Graph (0, 0)][DBLP]
   ISSRE, 2006, pp:375-384 [Conf]
   
8. Chih-Wei Ho, Laurie Williams
   Developing software performance with the performance refinement and evolution model. [Citation Graph (0, 0)][DBLP]
   WOSP, 2007, pp:133-136 [Conf]
   
9. Laurie Williams
   Debunking the Nerd Stereotype with Pair Programming. [Citation Graph (0, 0)][DBLP]
   IEEE Computer, 2006, v:39, n:5, pp:83-85 [Journal]
   
10. Lucas Layman, Laurie Williams, Daniela Damian, Hynek Bures
    Essential communication practices for Extreme Programming in a global software development team. [Citation Graph (0, 0)][DBLP]
    Information & Software Technology, 2006, v:48, n:9, pp:781-794 [Journal]
    
11. Michael Gegick, Laurie Williams
    On the design of more secure software-intensive systems by use of attack patterns. [Citation Graph (0, 0)][DBLP]
    Information & Software Technology, 2007, v:49, n:4, pp:381-397 [Journal]
    
12. Sarah B. Berenson, Kelli M. Slaten, Laurie Williams, Chih-Wei Ho
    Voices of women in a software engineering course: reflections on collaboration. [Citation Graph (0, 0)][DBLP]
    ACM Journal of Educational Resources in Computing, 2004, v:4, n:1, pp:- [Journal]
    
13. Lucas Layman, Laurie Williams, Lynn Cunningham
    Motivations and measurements in an agile case study. [Citation Graph (0, 0)][DBLP]
    Journal of Systems Architecture, 2006, v:52, n:11, pp:654-667 [Journal]
    
14. Laurie Williams, Lucas Layman
    Lab Partners: If They're Good Enough for the Natural Sciences, Why Aren't They Good Enough for Us? [Citation Graph (0, 0)][DBLP]
    CSEE&T, 2007, pp:72-82 [Conf]
    
15. Laurie Williams, Hakan Erdogmus, Richard W. Selby
    Roadmapping Working Group 4 Results. [Citation Graph (0, 0)][DBLP]
    Empirical Software Engineering Issues, 2006, pp:181-183 [Conf]
    
16. Lutz Prechelt, Laurie Williams
    Industry-Research Collaboration Working Group Results . [Citation Graph (0, 0)][DBLP]
    Empirical Software Engineering Issues, 2006, pp:153-157 [Conf]
    
17. Laurie Williams
    Structuring Families of Industrial Case Studies. [Citation Graph (0, 0)][DBLP]
    Empirical Software Engineering Issues, 2006, pp:134- [Conf]
    
18. Jiang Zheng, Brian Robinson, Laurie Williams, Karen Smiley
    A Lightweight Process for Change Identification and Regression Test Selection in Using COTS Components. [Citation Graph (0, 0)][DBLP]
    ICCBSS, 2006, pp:137-143 [Conf]
    
19. 
    Prioritizing software security fortification throughcode-level metrics. [Citation Graph (, )][DBLP]
    
    
20. 
    Is complexity really the enemy of software security? [Citation Graph (, )][DBLP]
    
    
21. 
    Proposing SQL statement coverage metrics. [Citation Graph (, )][DBLP]
    
    
22. 
    Ranking Attack-Prone Components with a Predictive Model. [Citation Graph (, )][DBLP]
    
    
23. 
    Prioritization of Regression Tests using Singular Value Decomposition with Empirical Change Records. [Citation Graph (, )][DBLP]
    
    
24. 
    Using In-Process Testing Metrics to Estimate Post-Release Field Quality. [Citation Graph (, )][DBLP]
    
    
25. 
    On the Effectiveness of Unit Test Automation at Microsoft. [Citation Graph (, )][DBLP]
    
    
26. 
    Pallino: automation to support regression test selection for cots-based applications. [Citation Graph (, )][DBLP]
    
    
27. 
    Privacy and security: what are you doing to keep the community safe? [Citation Graph (, )][DBLP]
    
    
28. 
    Examining the Relationships between Performance Requirements and "Not a Problem" Defect Reports. [Citation Graph (, )][DBLP]
    
    
29. 
    Improving Performance Requirements Specifications from Field Failure Reports. [Citation Graph (, )][DBLP]
    
    
30. 
    On preparing students for distributed software development with a synchronous, collaborative development platform. [Citation Graph (, )][DBLP]
    
    
31. 
    Predicting failures with developer networks and social network analysis. [Citation Graph (, )][DBLP]
    
    
32. 
    ROSE: a repository of education-friendly open-source projects. [Citation Graph (, )][DBLP]
    
    
33. 
    On establishing a benchmark for evaluating static analysis alert prioritization and classification techniques. [Citation Graph (, )][DBLP]
    
    
34. 
    An empirical model to predict security vulnerabilities using code complexity metrics. [Citation Graph (, )][DBLP]
    
    
35. 
    Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools. [Citation Graph (, )][DBLP]
    
    
36. 
    Sangam: a distributed pair programming plug-in for Eclipse. [Citation Graph (, )][DBLP]
    
    
37. 
    Empirical Software Change Impact Analysis using Singular Value Decomposition. [Citation Graph (, )][DBLP]
    
    
38. 
    Toward Non-security Failures as a Predictor of Security Faults and Failures. [Citation Graph (, )][DBLP]
    
    
39. 
    Protection Poker: Structuring Software Security Risk Assessment and Knowledge Transfer. [Citation Graph (, )][DBLP]
    
    
40. 
    Idea: Using System Level Testing for Revealing SQL Injection-Related Error Message Information Leaks. [Citation Graph (, )][DBLP]