Business Requirements Document (BRD)¶
Normative requirements for the target behaviour of KADRY. This is the source for product, design, and engineering. The current code is described separately in implementation status and does not cancel a requirement.
How to read an identifier¶
| Prefix | Domain |
|---|---|
| FR-О | Rules shared by more than one role |
| FR-К | Candidate |
| FR-Р | Employer |
| FR-А | Administrator |
| UC-* | A scenario on one page, see use cases |
| NFR-* | A measurable non-functional requirement |
| П-* | A screen on the page map |
| T_ P_ N_ L_ W_ K_ F_ R_ Δ_ | An administrator parameter. Starting values are in chapter 09 |
Priority comes from the source label: MVP is needed for the demo, extra is additional scope. Criterion marks K1–K6 stay next to the priority.
Product language¶
The interface is Russian. In both locales of this documentation, buttons and statuses are quoted in Russian, as on screen: «Принять», «Не подтверждён», «Отправить приглашение».
Chapters¶
| # | Chapter | Contents |
|---|---|---|
| 1 | Authentication | Email, password, 2FA, roles, lockout |
| 2 | Candidate profile | Resume, PDF, privacy, FSP, deletion |
| 3 | Assessment | Survey, grade, proctoring, interview, category |
| 4 | Invitations and chat | Statuses, salary band, contacts, chat, meetings, reports |
| 5 | Matching | Need, shortlist, bank, invitation |
| 6 | Vacancies and tasks | Publishing, applications, take-homes, recurring tasks, closing |
| 7 | Admin | Patterns, leaks, proctoring, validation, audit log |
| 8 | User data | What is known about a person, and what is not used for ranking |
| 9 | Parameters | Starting values and open questions |
Also: NFR, brief coverage, specification.