Advantages

1- Uncover Implicit Message.

Observations offer insight into comprehensive implicit and nonverbal messages in formal
settings, system interactions, or typical workflows. observation is a great way to
understand how end-users do their daily work by showing the process rather than
verbalize, which helps in achievement of information [3]. Limitations of human memory
in documentation or interviews may cause stakeholders to fail to include essential
requirements for the success of the system during the documentation phase. By
uncovering these particular requirements which are not often not clearly specified,
Software development teams have the ability to guarantee that systems are developed in a
way that is genuinely in line with users' demands, real-world work methods, and user-
centric software solutions.
2- Able to Gain Better Conceptual Understanding.
By observing stakeholder in their natural and real work environment, software
development teams would gain invaluable insights and understanding into actual use of
equipment, workspace and resources. This direct observation method goes beyond the
limitations of practices that been reported by stakeholders that usually oversimplified or
idealized. It gives more accurate understanding of the requirements by exposing the real
context in which how user work, together with the particular possibilities and difficulties
they face. Furthermore, this immersion into the operational environment enables analysts
to understand how these processes function and to identify the necessary support
requirements, so it can meet the real world need of it users.
3- In Depth Insights
Gaining deep insight and yielding detailed workplace into the complex social and
organizational processes that exist in workplace is made possible by ethnography. By
facilitating the observation of stakeholder actions, behaviors and how their use the
system, ethnography enables the validation of existing information and assumption
against stakeholder’s real-world scenarios. When continuous observations are made, this
strategy is very effective since it keeps stakeholder’s behavior natural and undisturbed.
Disadvantages

1- Hawthorne Effect
The Hawthorne Effect refers to the fact that people will modify their behavior simply
because they are being observed [2]. In context observing software requirement
elicitation, the Hawthorne effect can be disadvantage because stakeholders may alter their
behavior or provide biased information when they are aware that they are being observed.
When stakeholders become aware of the researcher's presence and activities, it can
disrupt the community being studied and potentially affect their natural behavior. So this
issue lead to inaccurate or incomplete data due to the fakeness or exaggeration of
stakeholder’s actions.
2- Time Consuming Research Process
Thus, directing ethnographic research is lengthy and taxing job [1] due to demands
extensive periods of observation and interaction to gain deep insights into stakeholders'
behaviors, work practices, and organizational dynamics. The comprehensive character of
ethnographic research could not always be achievable within project schedules, which
could cause delays or sacrifices in the completeness of data collecting. Therefore, the
large time commitment needed for ethnography might be a big detriment to software
development teams trying to quickly and effectively gather requirements.
3- Limited scope of study
Small group or community may not provide large insight and information which
generalizable to larger populations. This limitation can lead to a skewed understanding of
software requirements, as the needs of a broader user base may not be adequately
represented. Consequently, the final product may suffer from reduced usability and
acceptance, potentially leading to lower adoption rates and customer satisfaction.
4- Invasive
The presence of the observer during the business process might disrupt it or distract the
stakeholders in their activity. Considering the fact that the observation might take quite a
long time, this may affect the overall performance of the stakeholders. In addition, the
unnecessary character of observation during software requirement elicitation may cause
stakeholders to behave differently by changing usual procedures which it could result in
inaccurate data collection.
References
[1] Khan, M. H. (2018). Ethnography: An Analysis of its Advantages and Disadvantages.
Social Science Research Network. https://doi.org/10.2139/ssrn.3276755

[2] Kenton, W. (2022, June 15). Hawthorne Effect Definition: How it works and is it real.
Investopedia. https://www.investopedia.com/terms/h/hawthorne-effect.asp

[3] Requirements elicitation: Issues and challenges. (2014, March 1). IEEE Conference
Publication | IEEE Xplore. https://ieeexplore.ieee.org/document/6828119