Comments on: Genesis: Bridging The Gap Between Requirements And Code http://elegantcode.com/2008/11/28/genesis-bridging-the-gap-between-requirements-and-code/?utm_source=rss&utm_medium=rss&utm_campaign=genesis-bridging-the-gap-between-requirements-and-code Sun, 12 Feb 2012 18:54:00 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: Davy Brion http://elegantcode.com/2008/11/28/genesis-bridging-the-gap-between-requirements-and-code/comment-page-1/#comment-38332 Davy Brion Sat, 29 Nov 2008 11:31:43 +0000 http://elegantcode.com/?p=1573#comment-38332 @Tobin the size of the bubbles is currently not related to the module size or anything like that... it just tries to fit all of the bubbles on the screen as clear as possible. But that's a good idea though. a tabular format was never really considered because the tool not only had to be valuable, but it certainly had to be cool... the 'wow factor' was a requirement :p I don't know if you've looked at the linked PDF (at the bottom of the post) but there are some more graphs in there... for instance, there's one where you can compare the uncovered requirements with the covered requirements on a timeline @David Yes, if you only have one test linked to a requirement then the requirement will be green. We've kinda made a sport out of linking as many good tests as possible to each requirement though ;) Although we have thought about adding some kind of way to define some sort of coverage percentage to a specific test... but we haven't really come up with a good solution to that yet. @Tobin

the size of the bubbles is currently not related to the module size or anything like that… it just tries to fit all of the bubbles on the screen as clear as possible. But that’s a good idea though.

a tabular format was never really considered because the tool not only had to be valuable, but it certainly had to be cool… the ‘wow factor’ was a requirement :p

I don’t know if you’ve looked at the linked PDF (at the bottom of the post) but there are some more graphs in there… for instance, there’s one where you can compare the uncovered requirements with the covered requirements on a timeline

@David

Yes, if you only have one test linked to a requirement then the requirement will be green.
We’ve kinda made a sport out of linking as many good tests as possible to each requirement though ;)

Although we have thought about adding some kind of way to define some sort of coverage percentage to a specific test… but we haven’t really come up with a good solution to that yet.

]]> By: David Starr http://elegantcode.com/2008/11/28/genesis-bridging-the-gap-between-requirements-and-code/comment-page-1/#comment-38305 David Starr Sat, 29 Nov 2008 05:01:02 +0000 http://elegantcode.com/?p=1573#comment-38305 I have to agree with the coolness factor of this approach. This strikes me as primarily a visualization of the mapping between implemented functionality and business requirements. Given the association between complete business requirement and passing tests, do the visualizations show 100% completion as the tests are being added incrementally? For instance, if I have only one test, bu it is passing, does the visualization show the feature as passing? Just curious. Thisis a very hard problem to solve as it gets to the idea of bridging the gaps between code and requirements with understanding of implementation on both side. Cool stuff, Davy. I have to agree with the coolness factor of this approach. This strikes me as primarily a visualization of the mapping between implemented functionality and business requirements.

Given the association between complete business requirement and passing tests, do the visualizations show 100% completion as the tests are being added incrementally?

For instance, if I have only one test, bu it is passing, does the visualization show the feature as passing? Just curious. Thisis a very hard problem to solve as it gets to the idea of bridging the gaps between code and requirements with understanding of implementation on both side.

Cool stuff, Davy.

]]> By: Tobin Harris http://elegantcode.com/2008/11/28/genesis-bridging-the-gap-between-requirements-and-code/comment-page-1/#comment-38259 Tobin Harris Fri, 28 Nov 2008 16:44:32 +0000 http://elegantcode.com/?p=1573#comment-38259 This looks very pretty - cool factor 100% :) I like the fact that the diagram depicts project scope at a high level. I also like how the relative size of the bubbles indicates module size. Are the units of size relative to LOC or use case points (effort)? Sticking my Tufte hat on, I have a few questions. Are you intentionally keeping the diagrams quite sparse? I feel like I want to see, for example, how much effort & schedule remains on these modules. Had you considered putting the data less funky tabular format, to help make it more concise and to make comparison easier? Total respect for the level of traceability you've got going on. I was thinking about how I'd get tracability between use cases and code the other day, and it looks like you've got a great solution. This looks very pretty – cool factor 100% :)

I like the fact that the diagram depicts project scope at a high level. I also like how the relative size of the bubbles indicates module size. Are the units of size relative to LOC or use case points (effort)?

Sticking my Tufte hat on, I have a few questions. Are you intentionally keeping the diagrams quite sparse? I feel like I want to see, for example, how much effort & schedule remains on these modules.

Had you considered putting the data less funky tabular format, to help make it more concise and to make comparison easier?

Total respect for the level of traceability you’ve got going on. I was thinking about how I’d get tracability between use cases and code the other day, and it looks like you’ve got a great solution.

]]>