Hi MA Core member,

I am preparing some initial documents regarding the project scope and flow which shall be passed to the client also. The matter of course here is the client is quite unknown about the technical stuffs. She just described like "I can manage my site, products, follow-ups with my clients ..." in the initial project communication. Though I am clear about the picture, I need to provide the document to her so that I could ensure that the project shall not go beyond its scope. How should I do it??? Any specific terminology or way. I am afraid she coudl understand use case..Kindly advice.

Hi Vessela,

Nice hearing from you. What I am trying to prepare is something which should cut repetitive wok in the process and the same document can be used by both: our technical teams and the client . I was thinking about textual use case presentation in the SRS to describe the functional requirement, even I have done up with one more section as well. I am still not sure of including use case diagrams..as it might create a nightmare for her to understand the flow. I want make sure her what is going to be build and how she could get benefitted out of this. Also, I am eyeing on the usefulness of the product.But in the meantime, I want my developers to understand the conept/flow/objects from the same document. I am not seeing of preparing any seq. diagram for this. Kindly suggest.