I am still trying to find a good balance for requirements format. I have looked at Gherkin in a few books on specifications. The Microsoft press book on softw

I am still trying to find a good balance for requirements format. I have looked at Gherkin in a few books on specifications. The Microsoft press book on software requirements lists every possible way to represent requirements. I am working through the book Telling Stories requirements book by Ben Rinzler. I still have not found anything ideal that would be easy enough to teach to a business side that has no training on writing requirements and still provide enough detail to the technical side. I am getting close to settling on some form of diagram, user story statements, and use cases with Gherkin.