Provide trail from user story to concrete tools

[OliverFendt]

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)

[pellsiepen]

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.
Based on an action from the previous F2F meeting we are currently working on part of this topic in a smaller group, i.e. setting up the capabilities (glossary) and the mapping of architectural components in the unanimous understanding back to the capabilities (reverse mapping). Further, we would like to harmonize the terms and semantics also with regards to the "big picture" that you have created, ideally on the level of capabilities. The next step would then be to derive the needs and structure for necessary interfaces between components (finally mapping to APIs used by tools), which should ideally make use of the data types defined in the data model, thus closing the loop.
As there are still quite some needs for discussions we have been keeping the updates in the separate branch defining-capability-map for the moment. Any comments/suggestions are welcome.

[OliverFendt]

Great that there is already work available. I had a look at:
https://github.com/Open-Source-Compliance/Sharing-creates-value/blob/defining-capability-map/Tooling-Landscape/Unanimous-Understanding/OC-Reference-Tooling-Capabilities-Glossary.md

What we still have to add is the user story part to the capabilities and the capabilities -> concrete tools.