Ask HN: Better tools for the software requirements / scoping phase?

Re:Ask HN: Better tools for the software requirements / scop... by adrianN on Monday September 24, 2018 @10:28AM (#18057948)

I've found that writing (pseudo-)code is absolutely necessary to find problems in the requirements. Often enough the requirements are self contradictory or just contain too many unnecessary corner cases. I've seen requirements that sounded really simple in the requirement doc, but turned out to be extremely hard to test because they implicitly defined a state machine with dozens of transitions.

[ Parent | on HN ]

Re:Ask HN: Better tools for the software requirements / scop... by beat on Monday September 24, 2018 @12:01PM (#18058793)

Yes, definitely. This applies a lot to infrastructure issues, too. But pseudocode or extremely simple test case code can do this a lot better than tossing something into production to find out if it sucks.

I suspect a lot of the HN hostility to proper requirements analysis is coming from writing trivial systems.

[ Parent | on HN ]

Re:Ask HN: Better tools for the software requirements / scop... by carlmr on Monday September 24, 2018 @10:41AM (#18058080)

Especially because English is often a terrible language to express requirements.

[ Parent | on HN ]

Re:Ask HN: Better tools for the software requirements / scop... by adrianN on Tuesday September 25, 2018 @03:22AM (#18064255)

Especially when it's written by people who aren't native speakers but work in a "we're a modern company now" environment.

[ Parent | on HN ]