Hi,

Working as the main business/requirments analyst for our organisation, I have been in charge of collecting the requirements and sending them over to people who do the implementation.

These requirements revolve primarily around introducing changes to our website. These changes are documented as a user journey in form of screenshots (done by the design team) and text explaining how the expected behaviour would be. This is all generally derived from higher level requirements which are documented first and then broken down into smaller requirements and verified with business heads. This documentation is then sent over to the development team who come back with any queries and finally develop code for the website based on the document.

What is the opinion of the people on these forums regarding such an approach? I am not sure if these is a very widely used approach and was curious about what people think of this....appreciate your feedback and comments....Thanks

Hi:

At the more detail level, using screen shots is fine.    But remember that the real challenge is not so much documenting stand alone requirements, but, documenting the essential interrelationships between requirements.    With this in mind, what do your higher level requirements look like?    Do they focus on interrelationships between stand alone behavioral requirements?

Tony