Using Test-Driven Software Development Tools

Abacus, A.; Barker, Mike; Freedman, Paul L.

doi:10.1109/ms.2005.51

Cited by 2 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover it supports incremental updating in such a way that introducing new behavior through the debugger is not only possible but is actually advised [BDN + 09]. Indeed incremental updating through debugging encourages and supports agile development processes, and more specifically Test Driven Development (TDD) [ABF05]. In addition both the debugging and the reflecting facilities of Smalltalk are extensible.…”

Section: Existing Solutionsmentioning

confidence: 99%

See 1 more Smart Citation

Mercury: Properties and Design of a Remote Debugging Solution using Reflection.

Papoulias¹,

Bouraqadi²,

Fabresse³

et al. 2015

JOT

View full text Add to dashboard Cite

Remote debugging facilities are a technical necessity for devices that lack appropriate input/output interfaces (display, keyboard, mouse) for programming (e.g., smartphones, mobile robots) or are simply unreachable for local development (e.g., cloud-servers). Yet remote debugging solutions can prove awkward to use due to re-deployments. Empirical studies show us that on average 10.5 minutes per coding hour (over five 40-hour work weeks per year) are spent for re-deploying applications (including re-deployments during debugging). Moreover current solutions lack facilities that would otherwise be available in a local setting because it is difficult to reproduce them remotely. Our work identifies three desirable properties that a remote debugging solution should exhibit, namely: run-time evolution, semantic instrumentation and adaptable distribution. Given these properties we propose and validate Mercury, a remote debugging model based on reflection. Mercury supports run-time evolution through a causally connected remote meta-level, semantic instrumentation through the reification of the underlying execution environment and adaptable distribution through a modular architecture of the debugging middleware.

show abstract

Section: Existing Solutionsmentioning

confidence: 99%

“…Combining agile development [ABF05] with debugging in a single remote debugging session without the need of re-deployment.…”

Section: Experimental Settingmentioning

confidence: 99%

Mercury: Properties and Design of a Remote Debugging Solution using Reflection.

Papoulias¹,

Bouraqadi²,

Fabresse³

et al. 2015

JOT

View full text Add to dashboard Cite

show abstract

“…To deal with this situation both academics and software developers have strongly emphasized the need for methods, concepts and tools that favor the early delivery of functional parts of software systems that are valued by customers (Abacus et al, 2005;Nord and Tomayko, 2006). In this sense, the Incremental Funding Method, or IFM, is a financially responsible approach to requirement prioritization that increases the value creation of software projects (Denne and Cleland-Huang, 2004a;Denne and Cleland-Huang, 2004b).…”

Section: Introductionmentioning

confidence: 99%

MAXIMIZING THE BUSINESS VALUE OF SOFTWARE PROJECTS - A Branch & Bound Approach

Alencar¹,

Schmitz²,

Abreu³

et al. 2008

Proceedings of the Tenth International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

This work presents a branch & bound method that allows software managers to determine the optimum order for the development of a network of dependent software parts that have value to customers. In many different circumstances the method allows for the development of complex and otherwise expensive software from a relatively small investment, favoring the use of software development as a means of obtaining competitive advantage.

show abstract

Using Test-Driven Software Development Tools

Cited by 2 publications

References 0 publications

Mercury: Properties and Design of a Remote Debugging Solution using Reflection.

Mercury: Properties and Design of a Remote Debugging Solution using Reflection.

MAXIMIZING THE BUSINESS VALUE OF SOFTWARE PROJECTS - A Branch & Bound Approach

Contact Info

Product

Resources

About