SRS šabloni: Standard i Agile
Dva SRD šablona za različite situacije. Kopirajte onaj koji vam treba, popunite sekcije, obrišite smernice.
Kako izabrati:
- Standard SRD — enterprise projekti, regulisane industrije, veliki timovi, formalno potpisivanje
- Agile SRS — agile timovi, iterativni razvoj, živi dokument u Git-u
Više o svakom formatu: SRD — kompletan vodič.
Standard SRD
Kompletan šablon sa osam sekcija, usklađen sa IEEE 830 / ISO 29148. Za projekte koji zahtevaju sveobuhvatne, proverljive zahteve.
# SRD — [Software Name]
## Overview
- **Software Name:**
- **Author:**
- **Date:**
- **Version:**
- **Status:** Draft / In Review / Approved
- **Related PRD:** [link]
- **Related FRD:** [link]
## 1. Introduction
### Purpose
What this document specifies and what software it describes.
### Scope
What is covered and what is explicitly excluded.
### Definitions and Acronyms
| Term | Definition |
|------|-----------|
| | |
### References
- PRD: [link]
- FRD: [link]
- Architecture doc: [link]
- Design system: [link]
### Document Overview
How this document is organized and how to read it.
## 2. Overall Description
### Product Perspective
How this software fits into the larger system. Is it standalone, part of a suite, or replacing an existing system?
### User Classes and Characteristics
| User Class | Description | Access Level | Technical Skill |
|-----------|-------------|-------------|----------------|
| | | | |
### Operating Environment
| Parameter | Specification |
|-----------|--------------|
| Browsers | |
| Devices | |
| Operating systems | |
| Cloud provider | |
| Runtime | |
### Design and Implementation Constraints
- [Technology constraints]
- [Regulatory constraints]
- [Budget constraints]
- [Timeline constraints]
### Assumptions
- [What you assume to be true]
### Dependencies
| Dependency | Type | Owner | Risk if Unavailable |
|-----------|------|-------|-------------------|
| | Service / Library / Team | | |
## 3. Functional Requirements
Use "shall" for must-have, "should" for optional requirements.
| ID | Requirement | Priority | Source | Acceptance Criteria |
|----|------------|----------|--------|-------------------|
| FR-001 | | Must / Should | PRD §X | |
| FR-002 | | | | |
### FR-001: [Requirement Name]
**Description:** [Detailed behavior description]
**Input:** [What triggers this behavior]
**Output:** [What the system produces]
**Business Rules:**
- [Rule 1]
- [Rule 2]
**Error States:**
- [What happens when X fails]
- [What happens when Y is invalid]
**Acceptance Criteria:**
- [Testable condition 1]
- [Testable condition 2]
## 4. Non-Functional Requirements
| ID | Category | Requirement | Target | Measurement |
|----|----------|-------------|--------|-------------|
| NFR-001 | Performance | | | |
| NFR-002 | Security | | | |
| NFR-003 | Availability | | | |
| NFR-004 | Scalability | | | |
| NFR-005 | Reliability | | | |
| NFR-006 | Maintainability | | | |
| NFR-007 | Accessibility | | | |
## 5. External Interface Requirements
### User Interface
- [UI specifications, screen flows, validation rules]
- [Link to wireframes/mockups in appendix]
### Software Interfaces
| System | Protocol | Data Format | Direction | Authentication |
|--------|----------|-------------|-----------|---------------|
| | REST / gRPC / MQ | | Inbound / Outbound / Both | |
### Hardware Interfaces
| Device | Protocol | Data Format | Purpose |
|--------|----------|-------------|---------|
| | | | |
### Communication Interfaces
| Interface | Protocol | Port | Security |
|-----------|----------|------|----------|
| | HTTPS / WSS / AMQP | | |
## 6. Data Requirements
### Data Model
[Entity-relationship description or diagram reference]
### Data Dictionary
| Entity | Field | Type | Required | Constraints | Description |
|--------|-------|------|----------|------------|------------|
| | | | Yes / No | | |
### Data Retention
| Data Category | Retention Period | Archival Policy | Deletion Policy |
|--------------|-----------------|----------------|----------------|
| | | | |
### Data Migration
[If replacing an existing system, describe data migration requirements]
## 7. System Architecture
### Architecture Overview
[High-level architecture diagram reference]
### Component Descriptions
| Component | Responsibility | Technology | Interfaces |
|-----------|---------------|------------|-----------|
| | | | |
### Deployment Topology
[Deployment diagram reference — environments, regions, scaling]
### Observability
| Aspect | Tool | Configuration |
|--------|------|--------------|
| Logging | | |
| Monitoring | | |
| Alerting | | |
| Tracing | | |
### API Contracts
[Reference to OpenAPI specs or inline endpoint definitions]
## 8. Appendices
### A. Glossary
| Term | Definition |
|------|-----------|
| | |
### B. Use Case Diagrams
[Links or embedded images]
### C. State Diagrams
[System state transitions]
### D. Open Questions (TBD)
| ID | Question | Owner | Target Date |
|----|----------|-------|-------------|
| | | | |
### E. Change Log
| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.0 | | | Initial draft |
### F. Sign-off
| Role | Name | Date | Signature |
|------|------|------|-----------|
| | | | |Agile SRS
Lagani šablon za iterativni razvoj. Organizovan po funkcionalnostima, dizajniran za čuvanje u Git-u pored koda.
Više: Agile SRS — vodič.
# SRS — [Product Name]
## Overview
- **Product:** [name]
- **Last updated:** [date]
- **Owner:** [name]
## Scope
[One paragraph: what the software does and does not do.]
## User Classes
| Role | Description | Access |
|------|-------------|--------|
| | | |
## Non-Functional Requirements (Global)
| ID | Category | Requirement | Target |
|----|----------|-------------|--------|
| NFR-001 | Performance | | |
| NFR-002 | Security | | |
| NFR-003 | Availability | | |
## Architecture Overview
[High-level diagram reference, technology stack, deployment model.]
## Constraints
- [Regulatory]
- [Budget]
- [Technology]
## Open Questions
| Question | Owner | Target Date | Status |
|----------|-------|-------------|--------|
| | | | Open / Resolved |
---
## Feature: [Feature Name]
### Context
[What user problem this solves. Link to PRD section or user story.]
### Functional Requirements
| ID | Requirement | Priority | Acceptance Criteria |
|----|------------|----------|-------------------|
| [FEAT]-FR-001 | | Must / Should | |
| [FEAT]-FR-002 | | | |
### Data Model
| Entity | Field | Type | Constraints |
|--------|-------|------|------------|
| | | | |
### API Contract
[Endpoint definitions or reference to OpenAPI spec]
### Edge Cases
- [What happens when X]
- [What happens when Y]
---
[Repeat "Feature" section for each feature module]Resursi
- SRD — kompletan vodič — kada koristiti Standard vs Agile
- Agile SRS — lagana specifikacija
- SRD generator — kreirajte SRD pomoću AI
- Navigator dokumenata — pronađite pravi tip dokumenta