Question

Do research to fully define what a final system requirement document is. What sections does your final system requirement document include? What do you believe are the most important sections, and why? Additionally, who is the audience of your final system requirement document? Are there multiple versions of the document to communicate to different audiences?

Answer 1

The system requirement document is the software requirement specification. Final system requirement document is the system requirements document will state “ what” the software can do. However, it won’t state “ how” the software will get it done. What the software is capable of doing is directly perceived by the end users. When the end user completes some type of action, then the software is expected to respond to those actions in an expected way. Similarly, when a request comes from an external system for a particular action then it should get a specific response. The requirements document does not address how the software responds to the particular request.

The final system requirement’s document should include the following elements:
A title page
Summary
Glossary
Use cases, scenarios, and mock-up's
An overview of the architecture