1.0 KiB
1.0 KiB
NFR Design Plan - andreaslop-client (U2)
Steps
- Analyse NFR requirements (nfr-requirements.md, tech-stack-decisions.md)
- Evaluate question categories; no open questions (justification below)
- Generate
nfr-design/nfr-design-patterns.md - Generate
nfr-design/logical-components.md
Category evaluation (why no questions)
- Resilience: deploy resilience is inherited from
deploy-scp.yaml(atomic switch, health check, previous release kept); the new part is only the skip switch (NFR-DEP-02), which has one obvious design. - Scalability and performance: N/A for U2 (one small instance).
- Security: the token check, limiter and security event follow the answers Q3/Q4 and the existing
SecurityEventsand rate-limiting mechanisms; placement has one sensible solution. - Logical components: no new infrastructure; one validator, one controller change, one security event, one CSS theme, two CI jobs.
- Open verification items are listed in
nfr-design-patterns.mdand are settled by tests or the first test deploy.