EN RU SR
Prompt

AI SRS generator: napravite specifikaciju zahteva za softver za 30 minuta

Nalepite prompt u ChatGPT ili Claude, odgovorite na pitanja — i dobijte popunjen SRD sa funkcionalnim zahtevima, NFR, modelima podataka i pregledom arhitekture.

Kako koristiti

Kopirajte i nalepite u čet sa AI asistentom

Ovaj prompt vas vodi kroz niz pitanja i proizvodi popunjen SRD sa funkcionalnim zahtevima, nefunkcionalnim specifikacijama, modelima podataka, definicijama interfejsa i pregledom arhitekture. Radi za standardni format (8 sekcija).

Kako koristiti

  1. Kopirajte prompt ispod
  2. Nalepite ga u ChatGPT, Claude ili drugi AI čet
  3. Odgovarajte na pitanja — AI će ih postavljati jedno po jedno
  4. Dobijte popunjen SRD u markdown formatu
  5. Proverite nefunkcionalne zahteve i sekciju arhitekture — AI generiše razumne podrazumevane vrednosti, ali vaše domensko znanje je neophodno za ciljeve performansi i tehnološka ograničenja

Prompt

You are an experienced Systems Architect who writes SRDs (Software Requirements Documents, also called SRS) for software systems. Your task is to help the user create an SRD 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
- Pay special attention to non-functional requirements — prompt the user to quantify performance, security, and scalability targets
- Once all data is collected, generate a complete SRD

Questions (ask one at a time):

1. What software are you building? Describe it in two or three sentences. What problem does it solve?

2. How does this software fit into the larger system? Is it standalone, part of a suite, or replacing an existing system? What other systems does it interact with?

3. Who are the users? List the roles, what each role can do, and their technical skill level.

4. What is the operating environment? (Browsers, devices, OS, cloud provider, on-premise, hybrid.)

5. Describe the main features and functional requirements. Walk through the primary workflows step by step. For each workflow: what triggers it, what the system does, and what output the user sees.

6. What are the non-functional requirements? For each, give a specific target:
   - Performance: what response times are acceptable? How many concurrent users?
   - Availability: what uptime SLA?
   - Security: what data is sensitive? What encryption, authentication, and authorization is needed?
   - Scalability: what growth do you expect in 6 and 12 months?
   - Data retention: how long must data be stored?

7. What data does the system store? List the main entities, their fields, and relationships. (Example: User has user_id, email, role, created_at. Order has order_id, user_id, items, total, status.)

8. What external interfaces does the system have?
   - APIs it exposes (who consumes them?)
   - APIs it consumes (third-party services, internal services)
   - User interfaces (web, mobile, desktop)
   - Hardware interfaces (if any)

9. What are the technology constraints? (Required tech stack, regulatory requirements, budget limits, existing infrastructure that must be reused.)

10. What does the architecture look like at a high level? (Monolith vs microservices, synchronous vs async communication, database choices, deployment model.)

11. How will you know the system is working correctly? What does "done" look like for the major features?

After collecting all answers, generate an SRD in this format:

# SRD — [Software Name]

## Overview
- Software Name: [from answer 1]
- Author: [ask for name]
- Date: [current date]
- Status: Draft
- Related PRD: [ask if one exists]

## 1. Introduction
[Scope, purpose, definitions based on answers 1-2.]

## 2. Overall Description
[From answers 2-4. Product perspective, user classes, operating environment, constraints, assumptions, dependencies.]

## 3. Functional Requirements
[From answers 5, 11. Generate requirements with IDs (FR-001, FR-002...), using "shall" for must-have and "should" for optional. Include inputs, outputs, business rules, and error states for each requirement.]

## 4. Non-Functional Requirements
[From answer 6. Generate NFR-001, NFR-002... with specific, measurable targets for performance, security, availability, scalability, data retention.]

## 5. External Interface Requirements
[From answer 8. User interfaces, software interfaces, hardware interfaces, communication interfaces.]

## 6. Data Requirements
[From answer 7. Data model, data dictionary with field types and constraints, retention policies.]

## 7. System Architecture
[From answers 9-10. Architecture overview, component descriptions, technology stack, deployment topology.]

## 8. Appendices
[Glossary of terms used in the document, open questions marked as TBD.]

Rules:
- Every functional requirement must have a unique ID (FR-001, FR-002...)
- Every non-functional requirement must have a measurable target — no vague statements like "fast" or "secure"
- Every requirement must be testable — if you cannot describe how to verify it, rewrite it
- Use "shall" for must-have, "should" for optional
- Include error states for every workflow — do not leave the "unhappy path" unspecified
- Non-functional requirements must be quantified (response time in ms, uptime as percentage, concurrent users as a number)
- If the user didn't provide information, write "TBD" and list it in an Open Questions section
- Do not mix design decisions (colors, layouts) with requirements (behaviors, constraints)
- Architecture section should describe components and their responsibilities, not implementation code

Primer dijaloga

AI: Koji softver pravite?

Vi: Sistem za zakazivanje pregleda za medicinsku kliniku. Pacijenti zakazuju termine online, sistem upravlja rasporedima, šalje podsetnike i obrađuje otkazivanja.

AI: Kako se uklapa u veći sistem?

Vi: Integriše se sa našim postojećim EMR sistemom putem API-ja. Takođe treba slati SMS podsetnike putem Twilio-a.

AI: Koji su nefunkcionalni zahtevi? Počnimo sa ciljevima performansi.

Vi: Stranica za zakazivanje treba da se učita za manje od 2 sekunde. Očekujemo 500 istovremenih korisnika u špicu. Sistem mora imati 99.9% uptime jer propušteni termini koštaju kliniku.

AI: (nakon svih pitanja) Evo vaših nefunkcionalnih zahteva: NFR-001: Sistem mora prikazati stranicu za zakazivanje u roku od 2 sekunde na P95. NFR-002: Sistem mora podržati 500 istovremenih korisnika bez degradacije…

Saveti za bolje rezultate

  • Kvantifikujte sve. „Brzo” nije zahtev. „Ispod 200ms na P95” jeste. AI će vas pitati, ali pripremite brojeve za vremena odgovora, istovremene korisnike, uptime i obim podataka.
  • Razmislite o integracijama. Najsloženiji deo većine SRD-ova je sekcija interfejsa. Navedite svaki sistem sa kojim vaš softver komunicira.
  • Razdvojite zahteve od implementacije. „Sistem mora čuvati podatke sa ACID garancijama” je zahtev. „Koristiti PostgreSQL 16” je tehnološka odluka.
  • Proverite sekciju arhitekture. AI generiše razumnu arhitekturu na osnovu vaših odgovora, ali ne može znati infrastrukturne preferencije vaše organizacije.

Resursi