Tutorial: 16:15-17:45 (English)
Combining clojure.spec with design recipes
We share a method to systematically and comprehensively evolve a domain model, complementing use cases and “design recipes” with (clojure.spec-based) specifications. This approach facilitates finding inaccuracies at the edges of our in-growth domain, allowing us to: 1) supersede the de facto “tinker until it works” standard with a systematic “define-specify-verify (repeat)” cycle; and 2) complement the traditional mitigation of both internal and parameter validation errors.
Our approach combines the use of “design recipes”, use cases and “à la xDD” examples with (clojure.spec-based) specifications. The use of “design recipes” allows us to be systematic, while the usage of example-based use cases provide a comprehensive understanding of the domain. And when adding specifications to the mix, we end up empowered to verify compliance both at compile-time and at run-time.
This combination allows us to:
- move from a “tinker until it works” process to a “define-specify-verify (repeat)” cycle,
- find mistakes at the domain’s edge,
- count with specification-based generative tests, and
- automatic, specification-based documentation for the domain model
Instructions for running the tutorial code is here:
I found vital focusing on mentoring, couching teams for them to achieve coding standards of excellence. In a meanwhile I still write code for me to get in touch with the craft and to learn new paradigms as functional programming.
- Proactive and Self-Motivated Free Software and Free Culture geek.
- Interested in the Social Impact of Science and Technology.
- Contributions to Free Software, as part of globally distributed teams.
- Experienced both as a Researcher and as a Lecturer.
- Dedicated student mentor.
- International and Multicultural experience (Europe, South America, and Africa).