What are you people using to layout firmware requirements?
Recently, one of the projects i was working on just went sideways, one of the reasons was the requirements being thrown at the developer (mail/whatsap/spurious comments) by more than one stakeholder (usually contradicting themselves).
The requirement file ended up being a stinking pdf BLOB of contradictory not updated and sometimes redundant requirements.
I dont want this to happen again, so im curious how is everyone here managing "complex" system development?
Is there a clear winner in between Requirement Management software tools?
I am looking for a tool that also produces something that can be presented to nonTechnical stakeholders without too much translation.