Geschreven door Johan van Seijen donderdag 29 april 2010 15:29
If you look at the figure below, what was the first thing that came to your mind..? Take ten seconds to formulate an answer.
I bet it wasn’t: “Thats a great mockup from a functional design about 3D-modelling in Google Earth”? But, as you might’ve guessed by now, that’s exactly what it is. What I’ve tried to do just now is try to expand your beliefs about what a “mockup” could be. For me software design is about taking the invisible and making it visible and that’s rule #1 from Test Driven Requirements engineering (TDR).
Lees meer: Test Driven Requirements: Rule #1 Visualize the Design
Computer magazine AppWorks just published series two of a  two-part about "Test Driven Requirements engineering", the article  written by our functional designer and tester Johan van Seijen.
In this article we will give an historical review of the rise and fall of a large scale sports message broker platform and how it was replaced by a solution that was orders of magnitude simpler. The intended audience for this article is mixed. The start of this article describes the problem and does not assume any in-depth technical knowledge. The paragraph describing the solution contains technical elements and assumes some technical affinity with the reader. The platform was installed in 2004 and finally “de-plugged” by Dexels in 2010.
Computer magazine AppWorks just published series one of a two-part about "Test Driven Requirements engineering", the article written by our functional designer and tester Johan van Seijen.


 
