In your initial post, use your readings and further 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?
this can be some of your references:
Inflectra. (2018, March 1). What is a system requirements specification (SRS)? Retrieved from https://www.inflectra.com/ideas/topic/requirements-definition.aspx
Logtenberg, T. (2017, July 16). BRD, PRD, TRD… The case of the confusing requirements. Medium. Retrieved fromhttps://medium.com/@TylerLogtenberg/brd-prd-trd-the-case-of-the-confusing-requirements-cebd5e54ff2b
Pavlovic, A. (n.d.). Requirements deliverables: Target your audience [Blog entry]. Seilevel. Retrieved from http://www.seilevel.com/requirements/requirements-deliverables-target-your-audience
Tilley, S. (2016, February 5). Systems Analysis and Design, 11th Edition [VitalBook file]. Cengage Learning. Available from https://www.cengage.com/c/systems-analysis-and-design-11e-tilley
Wensel, S. (2003, October 13). Writing requirements documentation for multiple audiences. Stickyminds. Retrieved fromhttps://www.stickyminds.com/article/writing-requirements-documentation-multiple-audiences