Skip to content
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

capture requirements with traceability #120

Open
capsulecorplab opened this issue Aug 14, 2021 · 3 comments · May be fixed by #127
Open

capture requirements with traceability #120

capsulecorplab opened this issue Aug 14, 2021 · 3 comments · May be fixed by #127
Assignees
Labels
DocOps IT Operations for Documentation

Comments

@capsulecorplab
Copy link
Member

capsulecorplab commented Aug 14, 2021

stakeholder concerns & requirements page should be represented as both a collection of permalink-able statements, as well as a graphical requirements traceability diagram (as shown https://tetrabiodistributed.github.io/tetra/references/stakeholder-concerns-and-requirements/)

@capsulecorplab capsulecorplab self-assigned this Aug 14, 2021
@capsulecorplab
Copy link
Member Author

Capturing stakeholder needs in this manner will require a modeling language, s/a m30ml, for modeling stakeholder needs, user stories, supporting references, and their relationships https://github.com/Mach30/m30ml

@capsulecorplab
Copy link
Member Author

capsulecorplab commented Aug 24, 2021

The DOF repo itself already modeled in m30ml for modeling requirements in the form of stakeholder needs & user stories with metadata that includes derivedFrom elements for enabling requirements traceability

@capsulecorplab capsulecorplab changed the title capture stakeholder concerns and requirements as both a textual and graphical specification capture requirements with traceability Sep 4, 2021
@capsulecorplab capsulecorplab added the DocOps IT Operations for Documentation label Sep 4, 2021
@mmroden
Copy link
Collaborator

mmroden commented Sep 4, 2021

Need to write requirements as a set of user stories, which may take some time, ie, four hours or so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DocOps IT Operations for Documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants