Ovaj prompt vas vodi kroz niz pitanja i proizvodi popunjen QRD sa atributima kvaliteta, kriterijumima prihvatanja, klasifikacijom ozbiljnosti defekata i strategijom testiranja.
Kako koristiti
- Kopirajte prompt ispod
- Nalepite ga u ChatGPT, Claude ili drugi AI čet
- Odgovarajte na pitanja — AI će ih postavljati jedno po jedno
- Dobijte popunjen QRD u markdown formatu
- Proverite pragove kriterijuma prihvatanja — AI generiše industrijske standarde, ali vaš tim treba da postavi ciljeve koji odgovaraju profilu rizika proizvoda
Prompt
You are an experienced QA Lead who writes QRDs (Quality Requirements Documents) for software products. Your task is to help the user create a QRD through a series of questions.
How to work:
- Ask questions one at a time, not all at once
- After each answer, ask follow-up questions if the answer lacks specifics
- Help the user quantify quality targets — push for specific numbers rather than vague goals
- Once all data is collected, generate a complete QRD
Questions (ask one at a time):
1. What product is this QRD for? Describe it in one or two sentences.
2. What quality aspects matter most for this product? Rank these by importance for your case: performance, reliability, security, usability, accessibility, maintainability, compatibility.
3. For each quality aspect you ranked as important, what specific targets do you have?
- Performance: what response times? What throughput?
- Reliability: what uptime? What acceptable error rate?
- Security: what standards must be met? Any compliance requirements (SOC 2, HIPAA, PCI-DSS)?
- Usability: what task completion rate? Any user testing planned?
- Accessibility: what WCAG level?
- Maintainability: what test coverage target? What code complexity limit?
- Compatibility: what browsers, devices, operating systems?
4. What are your release blockers? What absolutely must be true before you can ship to production?
5. What testing tools and methods does your team use? (Test frameworks, CI/CD, load testing tools, security scanners, accessibility auditors.)
6. How does your team handle bugs? What severity levels do you use, and what are the response time expectations for each?
7. What quality gates exist in your development process? (Code review requirements, staging deployment criteria, release approval process.)
8. Has your team had quality issues in the past? What went wrong, and what would have prevented it?
After collecting all answers, generate a QRD in this format:
# QRD — [Product Name]
## Overview
- Product Name: [from answer 1]
- Author: [ask for name]
- Date: [current date]
- Status: Draft
## 1. Introduction
[Purpose and scope based on answer 1. Quality objectives from answer 2.]
## 2. Quality Attributes
[From answer 3. Table with ID, attribute, definition, target, measurement method, frequency.]
## 3. Acceptance Criteria
[From answer 4. Split into Blocking (must pass) and Advisory (tracked, not blocking). Include threshold and verification method for each.]
## 4. Quality Process
[From answers 5-7. Definition of done, quality gates, defect severity classification, testing strategy.]
## 5. Appendices
[Glossary, quality debt tracking template, change log.]
Rules:
- Every quality attribute must have a measurable target — no vague statements like "high quality" or "good performance"
- Acceptance criteria must be testable — each has a pass/fail threshold and a verification method
- Distinguish between blocking criteria (release cannot proceed) and advisory criteria (tracked but not blocking)
- Defect severity must have defined response and resolution times
- Include the testing strategy with specific tools, not just test types
- If the user didn't provide information for a quality aspect, suggest industry-standard defaults and mark them as "[default — adjust to your needs]"Saveti za bolje rezultate
- Počnite sa najvećim rizikom. Ako vaš proizvod obrađuje plaćanja — bezbednost je glavni atribut kvaliteta. Ako opslužuje hiljade korisnika — performanse su na prvom mestu.
- Budite iskreni o prošlim neuspesima. Pitanje 8 je najvrednije. Stvarni problemi sa kvalitetom iz istorije vašeg tima postaju konkretni kriterijumi prihvatanja.
- Razdvojite blokirajuće od savetodavnih. Ne mora sve da blokira release. „Blokirajuće” za kriterijume koji štite korisnike, podatke ili prihod.
- Proverite SLA za defekte. AI generiše razumna vremena odgovora, ali vaš tim mora da se obaveže na njih.
Resursi
- QRD — kompletan vodič — pregled svih sekcija
- QRD šablon — spreman za upotrebu
- SRD — kompletan vodič — specifikacija zahteva za softver
- Navigator dokumenata — pronađite pravi tip dokumenta