Usually I am using use case and natural language as shalland will methods for software requirements specification (SRS). I would like to know what SRS methods or approaches do you use? What are your favorites ones or gives the best results?
Re: SRS methods
In a regulated environment, "shall" and "shall not" is the only language allowed to distinguish requirements. Now this is my experience and I haven't seen anything different in other companies who are regulated.
Even non-regulated environments, the words "shall" and "shall not" were the accepted method for requirements. Use case identification is something else entirely and classified as such.
Not sure if this answers your question.