Automated Recognition of Low-Level Process: A Pilot Validation Study of Zorro for Test-Driven Development

Kou, Hongbing; Johnson, Philip M.

doi:10.1007/11754305_35

Cited by 7 publications

(6 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…They used T/P ratio (lines of test code verse lines of production code), testing effort against production effort, and cycle time distribution as indicators of TDD process conformance. This project precedes the Zorro software system (Kou and Johnson 2006), and in fact it stimulated our interest in studying low-level software process conformance. Unlike the prototype implementation of TestFirstGauge, which uses an Excel spreadsheet, Zorro is integrated into the Hackystat system and uses the JESS rule-based system (Friedman-Hill 2003).…”

Section: Research On Automated Inference Of Software Processmentioning

confidence: 99%

Operational definition and automated inference of test-driven development with Zorro

Kou

Johnson

Erdogmus³

2009

Autom Softw Eng

Self Cite

View full text Add to dashboard Cite

Test-driven development (TDD) is a style of development named for its most visible characteristic: the design and implementation of test cases prior to the implementation of the code required to make them pass. Many claims have been made for TDD: that it can improve implementation as well as design quality, that it can improve productivity, that it results in 100% coverage, and so forth. However, research to validate these claims has yielded mixed and sometimes contradictory results. We believe that at least part of the reason for these results stems from differing interpretations of the TDD development style, along with an inability to determine whether programmers actually follow whatever definition of TDD is in use. Zorro is a system designed to automatically determine whether a developer is complying with an operational definition of Test-Driven Development (TDD) practices. Automated recognition of TDD can benefit the software development community in a variety of ways, from inquiry into the "true nature" of TDD, to pedagogical aids to support the practice of test-driven development, to support for more rigorous empirical studies on the effectiveness of TDD in both laboratory and real world settings. This paper describes the Zorro system, its operational definition of TDD, the analyses made possible by Zorro, two empirical evaluations of the system, and an attempted case study. Our research shows that it is possible to define an operational definition of TDD that is amenable to automated recognition, and illustrates the architectural and design issues that must be addressed in order to do so. Zorro has Autom Softw Eng (2010) 17: 57-85 implications not only for the practice of TDD, but also for software engineering "micro-process" definition and recognition through its parent framework, Software Development Stream Analysis.

show abstract

Section: Research On Automated Inference Of Software Processmentioning

confidence: 99%

Operational definition and automated inference of test-driven development with Zorro

Kou

Johnson

Erdogmus³

2009

Autom Softw Eng

Self Cite

View full text Add to dashboard Cite

show abstract

“…They are mainly in the area of automated process discovery, modeling and monitoring, [1], [5], [6], [17].…”

Section: Related Workmentioning

confidence: 99%

“…The study presented in [17] aims at automatically assessing whether developers are indeed following a TDD (Test-Driven Development) process. The analyzed data is collected in a fully automated and non-intrusive way, only from specific development tools, [14].…”

Section: Related Workmentioning

confidence: 99%

“…The developer is considered to have followed a TDD process if she follows one of several predefined sequences of actions. The subjects in the experiment in [17] are 7 students in a laboratory environment working on developing an abstract data type.…”

Section: Related Workmentioning

confidence: 99%

“…We do not assume a specific model of behavioral patterns of the process (such as the finite state machines in [5]), nor predefined patterns of events, [1]. We intend tracking all the active time of the developer at her computer, rather than just the commit information, [6], or just the interaction with a specific development environment (such as Eclipse in [17]). …”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

An analysis of developers' tasks using low-level, automatically collected data

Coman¹

2007

The 6th Joint Meeting on European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software

View full text Add to dashboard Cite

In this paper, we describe our proposal of researching a way of automatically identifying developers' tasks, starting from their interaction with their computers. The data used is collected by a tool which is fully automated, non-intrusive and general enough to accommodate any application that the developers might be using. The method is based on previous researches regarding the behavior of developers and the structures of their tasks. We consider three levels, in decreasing order of complexity: tasks, activities and actions. Our approach has two steps: mapping from actions to activities and from activities to tasks. We describe our approach, our hypotheses, our planned methodology and our expected results. We point also to some of our preliminary results.

show abstract

Introducing Ubiquity in Noninvasive Measurement Systems for Agile Processes

Benedicenti

2017

Adaptive Mobile Computing

View full text Add to dashboard Cite

Automated Recognition of Low-Level Process: A Pilot Validation Study of Zorro for Test-Driven Development

Cited by 7 publications

References 13 publications

Operational definition and automated inference of test-driven development with Zorro

Operational definition and automated inference of test-driven development with Zorro

An analysis of developers' tasks using low-level, automatically collected data

Introducing Ubiquity in Noninvasive Measurement Systems for Agile Processes

Contact Info

Product

Resources

About