QUESTION(S): In responding to your peers, focus on sections that were identified and discuss what type of feedback you should prepare for regarding that particular section when presenting a final requirements document. Discuss how to manage both positive and negative feedback of your design recommendation.
PEER POST # 1
System documentation is important but in the design phase it is critical. So important that it can be considered a contract on deliverables (Tilley & Rosenblatt, 2017, p. 224). I think of it as a blueprint which is used to attain buy in from stakeholders. As systems get more complex this final system requirement documentation becomes even more helpful. Here, we will answer a few questions, regarding how this is used in different ways.
Firstly, the stakeholders in my final project include the Board of Directors for my case study as well as key department figures and the company lawyer. A final system requirement should be written for a broad audience. Secondly, they should be a living document until a final version is approved. There will be multiple versions of the document during the crafting of it. Generally, only one final version should exist, in practice there may be exceptions to this goal.Lastly, it should include a introduction, description (interfaces and constraints), product functions, user characteristics, assumptions and dependencies, as well as specific requirements (BMC Software 2021). Of these, it is my opinion that the most important sections are the description of the systems purpose and then more so the specific requirements. This way the goal is clear and that the deliverables can be specified and later be used for accountability to ensure business goals are achieved.
PEER POST # 2
A final system requirements document is a set of documentation that describes the behavior and features of a software or system and it describes the system-level performance and functional requirements for a system (Javatpoint, 2024). The sections of a final system requirement can include the executive summary, introduction, general description, data storage requirements, production requirements, quality control requirements, monitoring and control requirements, security requirements, data services requirements, other requirements, requirements traceability, references, and acronyms (European Space Agency, 2012).
I believe that the most important sections are the executive summary, introduction, the functional requirements (data, production, quality control), and the security requirements. The executive summary and introduction provide context to the audience regarding the final system requirement. This allows the audience to understand its purpose and be aware of any relevant background information that ties back to the final system requirement. The functional requirements and the security requirements are important for the audience to understand to address the cybersecurity issues that lies within the company that my final project is based on. Ensuring that the most important sections are tailored to the target audience prevents further data breaches and cyber-attacks.
The audience of my final system requirement document are systems and security analysts, the chief information security officer (CISO), incident managers and responders, and information security specialists. Since my audience falls within the same department or have a similar level of knowledge and expertise regarding cybersecurity and the final system document, I do not believe that multiple versions of the document will be needed to communicate with the audience.
