-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide trail from user story to concrete tools #74
Comments
Fully agree that we should have this tracing top-down, which also helps in shaping the requirements for new tools to be added, extensions/adaptations of existing tools to be made and/or the necessary interfaces. |
Great that there is already work available. I had a look at: What we still have to add is the user story part to the capabilities and the capabilities -> concrete tools. |
To make onboarding easier there should be documentation which describes the trail coming from user stories (what do I want/need to do) to capabilities of the different functional building blocks of the big picture (e.g. License & copyright scanner) and to a concrete instances of tools which implement the capabilities (this will also be a good base to identify needed glue code and/or APIs to be implemented in the concrete tools)
The text was updated successfully, but these errors were encountered: