Lucas Layman
  • Home
  • Publications
  • Publications
    • Topic Difficulty in a Python Data Structures Course: Student Perceptions and Performance
    • Designing, Implementing, and Evaluating a Municipal Water Quality Dashboard
    • Generative AI and the Future of Software Testing – A Virtual Roundtable
    • A Controlled Experiment on the Impact of Intrusion Detection False Alarm Rate on Analyst Performance
    • Interdisciplinary Collaboration among Nursing and Computer Science to Refine a Pharmacogenetics Clinical Decision Support Tool via Mobile Application
    • A Controlled Experiment on the Impact of Intrusion Detection False Alarm Rate on Analyst Performance
    • Refinement of a Pharmacogenomics App for Dosing Guidelines for Oncology: Findings from the Usability Evaluation
    • A Portable, Bluetooth-Enabled, Isometric Neck Assessment System
    • Coastal Eco Explorer: A Mobile Application for Ecology Education
    • Coastal Eco Explorer
    • Cry Wolf: Toward an Experimentation Platform and Dataset for Human Factors in Cyber Security Analysis
    • Suitability of SCS1 as a Pre-CS2 Assessment Instrument: A Comparison with Short Deliberate-practice Questions
    • Toward Predicting Success and Failure in CS2 : A Mixed-Method Analysis
    • How to trick the Borg: threat models against manual and automated techniques for detecting network attacks
    • The Cry Wolf Dataset - A repository of simulated IDS alerts for experimentation
    • The Cry Wolf IDS Simulator - An environment for conducting controlled experiments of cyber security analysis tasks
    • Less is More: Minimizing Code Reorganization using XTREE
    • Are delayed issues harder to resolve? Revisiting cost-to-fix of defects throughout the lifecycle
    • Topic Modeling of NASA Space System Problem Reports
    • Topic modeling of NASA space system problem reports research in practice
    • Applying Software Data Analysis in Industry Contexts: When Research Meets Reality
    • Ask the Engineers: Exploring Repertory Grids and Personal Constructs for Software Data Analysis
    • LACE2: Better Privacy-Preserving Data Sharing for Cross Project Defect Prediction
    • A Methodology for Exposing Risk in Achieving Emergent System Properties
    • Human Factors in Webserver Log File Analysis: A Controlled Experiment on Investigating Malicious Activity
    • InViz: Instant visualization of security attacks
    • Automated classification of NASA anomalies using natural language processing techniques
    • Debugging Revisited: Toward Understanding the Debugging Needs of Contemporary Software Developers
    • Local versus Global Lessons for Defect Prediction and Effort Estimation
    • Technical Debt: Showing the Way for Better Transfer of Empirical Results
    • Using Amazon's Mechanical Turk for User Studies: Eight Things You Need to Know
    • Toward Baselining Software Anomalies in NASA Missions
    • A Case Study of Measuring Process Risk for Early Insights into Software Safety
    • A Methodology for Exposing Software Development Risk in Emergent System Properties
    • A Methodology for Mapping System Engineering Challenges to Recommended Approaches
    • How Effective is Test Driven Development?
    • Obtaining Valid Safety Data for Software Safety Measurement and Process Improvement
    • The Role and Quality of Software Safety in the NASA Constellation Program
    • What Do We Know about Test-Driven Development
    • Coordination in large-scale software teams
    • Evaluation of Systems Engineering Methods, Processes and Tools on Department of Defense and Intelligence Community Programs
    • Iterative identification of fault-prone binaries using in-process metrics
    • Mining software effort data: A preliminary analysis of Visual Studio Team System Data
    • Addressing Diverse Needs through a Balance of Agile and Plan-driven Software Development Methodologies in the Core Software Engineering Course
    • Eleven Guidelines for Implementing Pair Programming in the Classroom
    • Information Needs of Developers for Program Comprehension during Software Maintenance Tasks
    • MimEc: Intelligent User Notification of Faults in the Eclipse IDE
    • Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools
    • Lab Partners: If They're Good Enough for the Sciences, Why Aren't They Good Enough for Us?
    • On the Impact of a Collaborative Pedagogy on African American Millennial Students in Software Engineering
    • Note to self: Make Assignments Meaningful
    • On the Impact of a Collaborative Pedagogy on African-American Millennial Students in Software Engineering
    • Personality types, learning styles, and an agile approach to software engineering education
    • Changing Students' Perceptions: An Analysis of the Supplementary Benefits of Collaborative Software Development
    • Essential Communication Practices for Extreme Programming in a Global Software Development Team
    • Examining the Compatibility of Student Pair Programmers
    • Intelligent User Notifaction to Expedite Awareness of Fault Code
    • Motivations and Measurements in an Agile Case Study
    • Personality Types, Learning Styles, and an Agile Approach to Software Engineering Education
    • On establishing the essential components of a technology-dependent framework
    • How and Why Collaborative Software Development Impacts the Software Engineering Course
    • Personality Profiles and Learning Styles of Advanced Undergraduate Computer Science Students
    • Rational Unified Process Evaluation Framework Version 1.0
    • Undergraduate Student Perceptions of Pair Programming and Agile Software Methodologies: Verifying a Model of Social Interaction
    • Empirical investigation of the impact of extreme programming practices on software projects
    • Exploring Extreme Programming in Context: An Industrial Case Study
    • Exploring the Use of a Safe Subset of Extreme Programming: An Industrial Case Study
    • Extreme Programming Evaluation Framework for Object-Oriented Languages -- Version 1.1
    • Identifying Potential Deficiencies in Agile Requirements Engineering Practices
    • Motivations and Measurements in an Agile Case Study
    • Toward a Framework for Evaluating Extreme Programming
    • Are decomposition slices clones?
    • Toward an XP Evaluation Framework

Identifying Potential Deficiencies in Agile Requirements Engineering Practices

Jan 1, 2004·
L Layman
· 0 min read
Type
Manuscript
Publication
North Carolina State University
publications
Last updated on Jan 1, 2004
Mypubs
← Extreme Programming Evaluation Framework for Object-Oriented Languages -- Version 1.1 Jan 1, 2004
Motivations and Measurements in an Agile Case Study Jan 1, 2004 →

© 2026 Lucas Layman. This work is licensed under CC BY NC ND 4.0

Made with Hugo Blox Kit. Build your site →