You are aware of the prototyping concept. There are divided views about including GUI prototypes in the SRS. ?

You are given 2 options:-





鈥?GUI details should be included in SRS


鈥?GUI details should not be included in SRS





Give your answer in the favor of any one view with valid reasons and arguments.








The answer should be concise and it should not exceed more than 1 page.


|||An SRS is a definition of what the software will do and how it is expected to perform. Assuming that your SRS is not for server-side software that does not have a significant UI component, any client-side SRS would clearly be impacted by the UI definition.





In fact, the argument should not be a "to include"/"to not include", but should be an argument of degree. In fact, on certain client-side software projects, the UI would be the only thing to essentially define.





Having said all of that, it still depends. If you customers demands it, you have no choice. If your customer demands other details, and does not give you time to define the UI in the SRS, them you have no choice. But, I can tell you that I would not accept an SRS without a UI definition. To me, it is the equivalent of misspellings on a resum茅.