Provide a sample use case or template about hydra-works HOT 9 CLOSED

Agreed on a template before things get unwieldy. I don't have particularly strong opinions on user stories vs use cases in Issue discussion, if ideas are getting bounced back and forth. But if they go into the repo they should ideally follow a consistent format.

I'd ideally like to get our product owner and metadata staff involved in generating our use cases (or user stories) since they have more a more concrete understanding of the history and the 'why'. Having a template would make it much easier to bring them into this process.

from hydra-works.

FWIW, I only did gherkin in #10 because the contributing doc said so. I
understand the sentiment, but I think what we're trying to accomplish might
be more complex than what gherkin can capture coherently (hopefully that
doesn't start a holy war).

In that spirit, though, I do think use cases are critical, and, even more
important, that they be based on real items we're trying to shoehorn into
our systems right now. I've been part of enough (over-)modeling projects
over the years, where imagined complex corner cases get too much attention,
and the result is always difficult and fragile implementations that don't
scale or migrate well.

-Js

Sent via mobile. Please excuse typos, brevity, etc.
On Oct 8, 2014 6:54 PM, "Matthew Critchlow" [email protected]
wrote:

Agreed on a template before things get unwieldy. I don't have particularly
strong opinions on user stories vs use cases in Issue discussion, if ideas
are getting bounced back and forth. But if they go into the repo they
should ideally follow a consistent format.

I'd ideally like to get our product owner and metadata staff involved in
generating our use cases (or user stories) since they have more a more
concrete understanding of the history and the 'why'. Having a template
would make bringing them into this process much easier.

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

from hydra-works.

No worries, @jpstroop. Based on the projects you've been involved with over the years, would you recommend one format for these over another. I'm flexible and I think your concerns are ones worth keeping in mind.

from hydra-works.

Personally I'm OK with it being somewhat loose at the moment--my only requirements would be a summary (gherkin if you want) and a set of the aforementioned real-world example.

from hydra-works.

That seems reasonable. referencing real-world examples is a key distinction that should probably make its way into CONTRIBUTING as a requirement.

from hydra-works.

Gherkin was not the suggested language, though issue #6 used the language to explain the problem.

from hydra-works.

I found @mjgiarlo usage of bulleted assertions at the end of #14 clearer than gherkin. Perhaps we could each distill our use cases into a set of assertions and then see where they overlap.

from hydra-works.

Can we close this ticket? Are there any action items?

from hydra-works.

The conversation may have migrated elsewhere, but the ultimate result (whether we came up with a template or just started copying each other) is the contents of the use-cases directory in this repo.

from hydra-works.