A) what are the properties of good SRS document explain detail with
examples?
B) Discuss the various non-functional requirements and constraints that
are required to create a complete SRS document.
A) A good SRS document is correct (both in the material and grammar), it is complete (so it does not leave the reader questions or the feeling of incompleteness), consistent (different parts or sections of the document do not contradict each other, independent on design (meaning that the core structure of the document can be used for any implementation). A good example is a Tesla patent #11068064 "Method of selecting an application target window in a user interface."
B) There requirements describe how users can (not must) interact with the system, how it informs users about its activity, within what limits the system should load and send response to users.
Comments
Leave a comment