I know that use cases define the user requirements, but what 'document' is used to detail the design requirements, including the navigation through the screens and business rules? In the past, our organization wrote 'user design documents' which detailed everything from beginning to end for a particular process. Everyone in IT was familiar and happy with this type of document. We were introduced to use cases and the team that I am on was responsible for writing them (all without any formal training). Now that we're failing in our project, some of the blame is being placed on the use case writers/requirements gatherers because we didn't document correctly. I'm at my wits end right now. Thanks all. Saving Changes...
