Analyze stakeholder needs into testable non-functional requirements using ISO/IEC 25010.
npx skills add https://github.com/AZANIR/qa-skills --skill qa-nfr-analyst
Please help me install this Agent Skill. Skill: qa-nfr-analyst Source: https://github.com/AZANIR/qa-skills/tree/main/.cursor/skills/qa-nfr-analyst Command: npx skills add https://github.com/AZANIR/qa-skills --skill qa-nfr-analyst
This Skill addresses the challenge of translating vague stakeholder expectations for non-functional aspects like performance, security, and usability into concrete, testable requirements that can be verified.
Analyze the provided requirements document to generate a Non-Functional Requirements Specification document.
High-intent search queries and answers about installing and using this skill.
To define testable non-functional requirements, you analyze qualitative stakeholder needs and map them to the ISO 25010 quality model, transforming them into quantifiable criteria with specific measurement methods and acceptance thresholds.
The ISO 25010 quality model for non-functional requirements is a framework covering performance efficiency, security, usability, reliability, maintainability, and portability, used to structure and evaluate software quality characteristics systematically.
To write measurable NFR criteria for performance and security, you translate qualitative goals into specific metrics, such as defining fast as a p95 response time under 500ms and secure as having zero OWASP Top 10 findings.
Yes, you can generate a full non-functional requirements specification by analyzing an existing requirements document, mapping stakeholder expectations to ISO 25010 categories, and outputting detailed criteria with measurement methods.
The best way to ensure non-functional requirements are verifiable during testing is to establish clear acceptance thresholds and defined measurement methods for each criterion, allowing testers to objectively confirm if the system meets the specified targets.
Yes, this approach works for API performance and security by mapping API-specific stakeholder expectations to the ISO 25010 model, generating quantifiable targets like maximum response times and vulnerability scan baselines for verification.
TykoDevConvert raw user input into an RFC 2119-prioritized SRS with acceptance criteria.
Imad-OuteDesign performance test scenarios and acceptance criteria from non-functional requirements.
dhar174Generate ISTQB and ISO 25010-aligned test strategies and QA plans for GitHub projects.
jabrenaCreate Architectural Decision Records for non-functional requirements using the ISO/IEC 25010:2023 quality model.
