Abstract
The purpose of this paper is to provide insight into the theoretical concept of Requirements Engineering (RE) and the process of developing a shared understanding of software requirements. In this paper we argue that developing a shared understanding relies on a set of activities that is applied by the members involved in the process. Because of this, shared understanding is a subject matter or process that cannot be measured objectively. Additionally, in this paper we present the elements of RE that have been applied by analysts. There are several elements included in the RE process, which, if improved, could lead to the development of shared determination of software requirements. In this paper we discuss elements that occur as part of both of these processes of shared understanding and RE.
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.
