QA Automation Tools such as cucumber, selenium, etc check the quality of code. Is there any tool available that provides knowledge regarding software quality requirements (a.k.a. Non-functional Requirements) analysis at early stage of Requirements Engineering.
Please share your experience.
Thanks
This paper aims to develop a knowledge audit (KA) model with the focus on knowledge assessment in the requirements elicitation process (REP) to allay the problems of REP regarding knowledge communication. A software prototype has been developed based on the model which assesses the existing knowledge in REP, this software or some similar software can be used to analyze the quality of requirements.
Article A knowledge audit model for requirement elicitation: A case ...
The software is developed using ontology, which has been explained in this pre-print paper. As soon as I get the paper published, I can share it with you.
Preprint The Use of Ontology in Support of a Knowledge Audit System f...
I hope the first article be helpful for you at this stage.
Regards.
https://arxiv.org/pdf/1602.05618
https://www.diva-portal.org/smash/get/diva2:811937/FULLTEXT02.pdf
https://www.evoketechnologies.com/blog/functional-non-functional-requirements-sdlc/
https://link.springer.com/content/pdf/10.1007%2F978-3-319-77243-1.pdf
Among the eight companies that I work(ed) with, none use any particular tool. NFRs are usually stored alongside with FRs and sometimes are tagged as NFR. Nothing more than that.
Few robust tools, but some well-defined methods.
Quality attribute requirements are strong related to software architecture. Validating the them, at early stages of the software development life cycle, is the focus of methods such as QAW (quality attribute work shop) and ATAM (architecture tradeoff analysis method).
Honestly, I have never seen a specialized tool for non-functional quality specific requirements that are non-technical. Also, I don't really see a need for a specific tool to track these. If a quality requirement is business related, it would easily be captured in the same tool for storing the business requirements (or user stories). Additionally, having a separate tool would create yet another process integration for ensuring the requirements are met. I can imagine that if there was a specific need to keep/track quality requirements separate, (i.e. for regulatory reasons), then I imagine that a separate project tracked in something like Jira would work well, and integration seamlessly into sprints. However, if the question is more related to technical quality requirements, by which I mean automated testing for quality, then there are many tools that accomplish this because the quality testing "requirements" are actual code to perform unit and functional tests. This "testing code" would be stored in the same place as the source control system, though perhaps in a separate repository. Since the current paradigm is to continuously test for quality, it is not as if the "quality requirements" are met once and then the project moves on. It is necessary to test and re-test for quality with every release.
No such tools are used for quality requirements ...but some methods are used..
- Badges
- Science topic
- Similar topics
- Human-Computer Interaction
- Collaboration