-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add Communicability (first try ) #154
Conversation
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.
thanx for your contribution - really appreciated!
- "tags" MUST be from the 8 "properties" shown on the homepage. Please change the three you mentioned to "usable", maybe add "suitable". Please use NO COMMA here (it's a bug in our current implementation)
- we STRONGLY differentiate between definitions of quality attributes ("qualities"), which have to refer to "official" sources like ISO, wikipedia, known-books or similar
- the (measurable) requirements are distinct files, located under the "requirements" directory under the appropriate letter in a subdirectory "_posts". Maybe you just copy/paste one of the existing files.
- requirements should be MEASURABLE and therefore have a precise metric.
Hello, Thank you very much for the helpful feedback and clear instructions; I truly appreciate it. I will take some time to refine and improve the quality of my submissions based on your guidance. Best regards, |
@philipp, anything I can do to support your contribution? In case you need technical support, we can delegate this to @Per-Starke, who is eager to help out with Git, Markdown + Jekyll related issues. Just let us know, please! |
@VirtuOes Feel free to contact me / just write an issue and assign me to that If you, as Gernot said, need any help with Git, Markdown, Jekyll and so on, I' here to help :) |
@VirtuOes - any news or updates from your side? |
Hi @VirtuOes - I will add communicability as a quality and likewise add some of your examples, quoting your contribution. |
thanx to P.Hechler (@VirtuOes)
closed, content has been added, otherwise this communication is stale. Nevertheless, many thanx for contributing |
Hello,
I've just submitted a pull request where I've added a number of items, translated somewhat hastily, from my internal sources. These sources include 4-5 tenders related to medical software.
The contributions are primarily mapped to the "Qualitätsanforderung/Benutzerfreundlichkeit/*" categories.
I would greatly appreciate any feedback regarding the structure and process of my submission. This will help me to provide more relevant and useful content for the project in the future.
Kind regards,
Philipp