52 add requirements in docs as code format with traceability to architecture elements #53
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First step with Weather Station example. Creating the reqs_repo file and an overview diagram.
…for the bi-directional traceability into the reqrepo for each req.
…ple for trace creation.
…n starting with a given alias.
…n starting with a given alias.
…rived_to req. needs to be done for derived_from too. further examples.
updated documentations and tests
DrMarkusVoss
deleted the
52-add-requirements-in-docs-as-code-format-with-traceability-to-architecture-elements
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 1.1.0
introduction of requirements-as-code