Drawio flowchart is the absolute key between the top level PRD docs and the low level software implementation.
PRD (Product Requirement Document)-> Basic product level documentation that can be given to business stakeholders and newly inducted technical stakeholders for product overview.
FRS (Functional Requirement Spec) -> Detailed breakdown of each function as noted from the PRD. Each function is described in as much vivid detail as possible.
SRS (System Requirement Spec) -> Division of functions across various hardware sub-systems. E.g. Frontend (e.g. mobile/desktop), BFF (e.g. CF/Akamai) , Backend (e.g. Hetzner), external suppliers (e.g. Razorpay payment gateway, SMS onboarding service) and special interface protocols (e.g. Android TV remote V2, ADB, SDB etc). Key is to split the functions across them so that each system can be designed seperately.
SwRS (Software requirement spec) -> Ensure each system flowchart is complete to define the complete nodes and their corresponding inputs and outputs. A rough estimate for the nodes in the flowchart is equivalent to the maximum number of files that needs to be created per system.
SDD (Software design spec) -> Ensure each SwRS node is decomposed into a single prompt in specified template that can be sent across to local LLM to iterate over. So each flowchart node from SwRS = one file that the SDD defines for local LLM.
Drawio flowchart is the absolute key between the top level PRD docs and the low level software implementation.
PRD (Product Requirement Document)-> Basic product level documentation that can be given to business stakeholders and newly inducted technical stakeholders for product overview.
FRS (Functional Requirement Spec) -> Detailed breakdown of each function as noted from the PRD. Each function is described in as much vivid detail as possible.
SRS (System Requirement Spec) -> Division of functions across various hardware sub-systems. E.g. Frontend (e.g. mobile/desktop), BFF (e.g. CF/Akamai) , Backend (e.g. Hetzner), external suppliers (e.g. Razorpay payment gateway, SMS onboarding service) and special interface protocols (e.g. Android TV remote V2, ADB, SDB etc). Key is to split the functions across them so that each system can be designed seperately.
SwRS (Software requirement spec) -> Ensure each system flowchart is complete to define the complete nodes and their corresponding inputs and outputs. A rough estimate for the nodes in the flowchart is equivalent to the maximum number of files that needs to be created per system.
SDD (Software design spec) -> Ensure each SwRS node is decomposed into a single prompt in specified template that can be sent across to local LLM to iterate over. So each flowchart node from SwRS = one file that the SDD defines for local LLM.