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.

Sign up for GitHub

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

Jump to bottom

formating suggestion #88

Open

lseeman opened this issue Oct 8, 2024 · 0 comments

Labels

lseeman commented Oct 8, 2024

Change to formatting: Use embedded list structure as bellow in the document so that the semantics show what requirement is under what user need.

I have formatted the document at https://docs.google.com/document/d/1dFjMfobPdWUz0a-wm6NQKN_nRXVjSLvJlHcgFF0SnHc/edit to make it easier to follow so we can review it.

I made user needs distinguishable from requirements (The user needs are not bulleted). So you can jump from user need to user need, and see to which user need each REQ (requirement/pattern)uirement belongs to.
Key works in userneeds in bold
3 Explained what req is inline

JaninaSajka added the COGA label

JaninaSajka added the version++ label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment