Reflection:

The techniques used throughout a system's lifecycle to identify significant components and
their goals, requirements, and effects are referred to as "requirement engineering.” (Marcos,
2019.) Requirements Elicitation is significant for product as it serves the key process for
classifying product need. Key shareholders' requirements visions are discovered through the
elicitation development. Business analysts identify the real business requirements that would
drive the plan by asking the suitable questions of experts, enabling in-depth discussions, and
documenting findings. The purpose of requirement elicitation is to discover and communicate
to developers what users desire, how that information is acquired has a big impact on the
standard of the requirements that are created. Since it involves getting through
communication barriers and extracting user requests, gathering requirements can be difficult
the problem statement of the project is what information a user needs, and how could we
organize the web to provide it. For the Elicitation Technique Selection, we have selected
Conversational techniques. A conversational technique is an organized conversational
procedure that gathers a group of people to discuss a subject or an issue. These techniques
encourage a more organic information flow, which helps in discovering and prioritizing
consumer wants and offering perception into product development. Conversational
approaches include things like focus groups, surveys, brainstorming sessions, and interviews.
The benefits of this selection include Comprehensive Q&A Sessions Since it enables a
conversation between two or more parties about a subject of shared interest, the interview is
the most typical and traditional method of gathering needs. Further, we talked about
Requirements Elicitation Process. The data obtained during the requirement elicitation phase
is important to the success of the requirement formulation process. Several people are
registered to help in requirement elicitation, some of whom may or may not be affiliated with
the same organization. The first step was planning in which our interview questions were
developed based on our knowledge of the subject and the findings of our literature review.
After making sure that each question addressed the subject matter we had been studying, we
went over it again and deleted the irrelevant ones. Mock interviews were done by us. After
that we finalized the interview questions, we reached out to several individuals working for
various software firms through phone and email to schedule interviews. It enabled us to
communicate with five specialists in Pakistan and Denmark. In the documentation part, A
system's functional requirements specify the attributes and skills it must possess as well as
the actions it must do in response to specific inputs while non-functional limits are reflected
in restrictions on the development of systems, the standards that can be applied, etc.
References
Pacheco, C., García, I. and Reyes, M., 2018. Requirements elicitation techniques: a
systematic literature review based on the maturity of the techniques. IET Software, 12(4),
pp.365-378.
Aldave, A., Vara, J.M., Granada, D. and Marcos, E., 2019. Leveraging creativity in
requirements elicitation within agile software development: A systematic literature
review. Journal of Systems and Software, 157, p.110396.
Yaseen, M. and Farooq, U., 2018. Requirement Elicitation Model (REM) in the context of
global software development. Global Journal of Computer Science and Technology, 18(C2),
pp.37-41.