Ask HN: How do you translate functional requirements to a technical plan?
1 comments
The old-fashioned systems engineering approach was to accomplish the translation of functional requirements into a plan (or preliminary design package) by using a combination of graphics (UI), diagrams, functional prototypes, pseudo-code, data descriptions, interface control, and other details or special-purpose tools that might be relevant to the application, e.g. special-purpose hardware, unique operating system, algorithm models, etc.
I've been in software engineering for about 15 years but never found a way to get to a well structured technical (implementation) plan from a set of functional requirements. Sure, I eventually get to a plan when asked, but I find my approach lacking structure and therefore each of my plans are structured differently, and am getting mixed results.
I consider myself very strong technically, familiar and experienced with many SE practices on both design/architecture and implementation side.
How do you approach work like this, and do you follow a specific structure?
Thank you.