I need to proofread this document and determine if APA Development… I need to proofread this document and determine if APA Development Req

I need to proofread this document and determine if APA Development… I need to proofread this document and determine if APA Development Requirement Management Approach NameInstitutionDate                 Development Requirement Management ApproachDescription of the approach, including core activities, inputs, and outputs.          The approach is called the development requirement management approach. It is a set of techniques used for documenting, analyzing, prioritizing and agreeing on the requirements. It will enable the engineering team to have current approved conditions. In this approach, the engineering team will need to complete each project phase before moving to the next one. The core activities in this approach include planning the project requirements, outlining the requirements process, managing the requirement changes and tracking the project progress (Boulanger, 2016). Techniques and/or processes used in identifying stakeholders and requirements. The technique used in identifying stakeholders and requirements include;  Brainstorming. Brainstorming was used to determine the best stakeholders for the project. The team members brainstormed in which the information needed for the project was obtained. Experts did the interviews to find the best stakeholders. However, getting stakeholders with all the requirements needed for the project had to be done by the interview experts. How traceability and configuration control will be maintainedTraceability will be maintained by copying the acceptance criteria for each user story and then adding them to the requirements management system; traceability will also be maintained by conducting regular audits regarding compliance and regulations. In addition, the configuration will be maintained by classifying and managing systems by groups and subgroups and prioritizing actions (TRADEWIND, 2021).Benefits and risks of the approachBenefits of this approach include; This approach requires low costs of developments across the lifecycle. It is a cheap approach that will cost less money for the developers. This approach allows requirements traceability. It will enable the management team to fully view any changes in engineering requirements. Risks of this approach include; This approach comes with a risk of incorrect or missing links between the requirements. However, it can be a big challenge for the project owners. Another risk associated with this approach is the duplication of requirements between different documents.        ReferencesBoulanger. L.J. (2016). Requirement Management. Retrieved from; https://www.sciencedirect.com/topics/computer-science/requirements-managementTRADEWIND. (2021). JAIC. The Trade wind OTA Enterprise Office (operated by IN3), in conjunction with the Joint Artificial Intelligence Center (JAIC)    Engineering & Technology Industrial Engineering SYSE 530 Share QuestionEmailCopy link