Walking on water and developing software from a specification are easy if both are frozen. – Edward V. Berard
I want to address this as it’s a topic that keeps coming up.
SRS contains “WHAT” the software is required to satisfy. It is the starting point for software design activities (whether it’s algorithm, design, user interface, tradeoffs). Just because it has the word “software” in it doesn’t mean it’s automatically owned by software.
It is a huge conflict of interest for the organization to have software function own the SRS for the software they’re implementing. This is essentially saying the software team will define what to implement, how to implement it, and guide test what to verify… it’s a fucking joke so please stop arguing
Leave a Reply