Abstract
Errors made during the requirements collection and analysis phase make it very difficult to maintain the software product and cost the company extra costs. The difficulty of directly collecting requirements from stakeholders is due to inconsistencies between the major stakeholder groups, as well as related factors in the collection of requirements itself, as well as the selected methodology for the process of converting stakeholder requirements into development requirements. As a solution, it is necessary to use a high level of prioritization in order to distinguish among many requirements the necessary for successful implementation of the product, as well as to correctly allocate compliance with the requirements in such a way that each group of stakeholders is satisfied, but at the same time setting the goals of the supersystem more priority than the goals of the subsystem. This article discusses the methodology of system engineering to solve issues related to the identification of possible contradictions of requirements.
 Keywords: System engineering, requirements engineering, business process, requirements, software product, analysis.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
