Exploratory programming
 | This article relies largely or entirely on a single source. (March 2024) |
Exploratory programming, as opposed to implementation (programming), is an important part of the software engineering cycle: when a domain is not very well understood or open-ended, or it's not clear what algorithms and data structures might be needed for an implementation, it's useful to be able to interactively develop and debug a program without having to go through the usual constraints of the edit-compile-run-debug cycle. Languages such as APL, Cecil, Clojure, C#,[1] Dylan, Factor, Forth, F#, J, Java,[2] Julia, Lisp, Mathematica, Obliq, Oz, Prolog, Python, REBOL, Perl, R, Ruby, Scala, Self, Smalltalk, Tcl, and JavaScript, often in conjunction with an IDE, provide support for exploratory programming via interactivity, dynamicity, and extensibility.
Formal specification versus exploratory programming[edit]
For some software development projects, it makes sense to do a requirements analysis and a formal specification. For other software development projects, it makes sense to let the developers experiment with the technology and let the specification of the software evolve depending upon the exploratory programming.
Similarity to Breadboarding[edit]
A similar method of exploration is used in electronics development, called Breadboarding, in which various combinations can quickly be tried and revised, accepting the tradeoff that the result is definitely temporary in nature.
See also[edit]
Notes[edit]
- ^ through Microsoft Visual Studio
- ^ through its JShell read-eval-print loop interpreter introduced in version 9
References[edit]
- Rajib Mall (1 August 2004). Fundamentals of Software Engineering. PHI Learning Pvt. Ltd. p. 32. ISBN 978-81-203-2445-9.
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |