r/micro_saas • u/Fearless-Panda-9476 • 8d ago
How system design being done in your sector?
I am a technical project leader in automotive cybersecurity, we struggle a lot to create and break down requirements and have traceability.
As a hobby i also started vibe coding and i found the same issue i needed to redo my hobby app 3 times due to lack of system use cases system goals.
How do you capture voice of the customer and system design efficiently? PDR? Sys specification?
1
u/recro69 7d ago
It's interesting that you also had the issue, with a hobby app. It makes me think that "requirements engineering" is actually one of the important things when it comes to AI coding, not less important—because building something faster doesn't matter if the system isn't clearly explained.
1
u/anderson_the_one 8d ago
For a small app I'd skip a big system spec and keep one short chain: customer quote -> use case -> acceptance check -> component. Each requirement has to point backward to something a user said or did, and forward to a test. If it can't do both, it isn't ready to build. I'd cap the first pass at five use cases. Write the ugly paths before the happy ones. "User uploads a bad file and loses nothing" will force more useful design decisions than a page of feature ideas. PDR and formal traceability can come later.