-
Notifications
You must be signed in to change notification settings - Fork 0
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
docs: 📝 aggregate quality requirements for software architecture #100
Conversation
introduction and solution strategy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice!! 🎉 I made some suggestion
software/introduction.qmd
Outdated
| Goals | Scenarios | | ||
|--------------------|----------------------------------------------------| | ||
| Beginner-friendly interfaces | We want non-technical users to use this, therefore it should be easy to learn and use. | | ||
| Comprehensive functionality and easy to use | All apps under the Seedcase banner should be able to do what we need them to do, with ease. | | ||
| Reliable and robust | As much as possible we want to simplify the applications and ensure that there is comprehensive error handling. | | ||
| Secure and legally compliant | Seedcase software currently targets health data, so it needs to be compliant with privacy and security laws. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is fine to not duplicate things at all and instead move this table over to the quality requirements page at the top as like a "summary" section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lwjohnst86 So leave nothing in the introduction about quality requirements?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@K-Beicher yea, since we can link to the document rather than have duplicate information.
Co-authored-by: Luke W. Johnston <lwjohnst86@users.noreply.github.com>
…github.com/seedcase-project/design into docs/quality-requirements-for-architecture
Description
Related Issues
Closes #11, #29, #93
See also Issues #29, #93
Reviewer Focus
This PR requires an in-depth review.
There is a link to the ISO standard at the start of the document, it may be useful to read through that before reviewing.
Checklist
For general documentation: