Experiences with using ears for stakeholder requirements deve-lopment of the safe integration of unmanned aircrafts in the airspace project


  • Priscila Renata Silva Barros
  • Rebeca Camurça Coelho
  • Christopher Shneider Cerqueira
  • Geilson Loureiro




requirements, boilerplates, stakeholder


Requirements permeate the entire lifecycle of a system or product, from identifying the stakeholders’ needs to disposal, including verification and validation activities. Therefore, the process for the requirements development must be carefully observed and established in order to ensure that the requirements are complete, consistent, and correct. The use of an appropriate predefined structure can improve the requirements’ elicitation, enabling the reduction of ambiguities and the detection of duplications or omissions. Thus, this article proposes the use of syntax patterns during the development of the stakeholders’ requirements in the context of an airspace project. The result of applying the proposal of this article in a real case was a list of initial requirements in standardized language with their traceability guaranteed.


Arora, C.; Sabetzadeh, M.; Briand L. C.; Zimmer, F. Requirement boilerplates: Transi-tion from manually-enforced to automatically-verifiable natural language patterns. In: IEEE 4th International Workshop on Requirements Patterns (RePa), Karlskrona, Swe-den, 2014.

Barros, P.; Camurça, R.; Cerqueira, C; Loureiro, G. Using Controlled Natural Language to Capture Problem States from Stakeholders and Transform them into Models. In press.

Cerqueira, C. Class notes. 2023. Available in < http://cscerqueira.com.br/wp-content/uploads/2023/07/TE-2652023-01-INTRODUCAO-AO-CURSO-v2.pdf >.

Dick, J.; Hull, E.; Jackson, K. Requirements Engineering. Fourth Edition. Springer. 2017.

DoD. U.S. Department of Defense. DoD Instruction 5000.89 - Test and Evaluation. 2020.

FAA. Federal Aviation Administration. Test and Evaluation Handbook. Air Traffic Sys-tems T&E Services, ANG-E5. 2020.

GAO. U.S. Government Accountability Office. Best Practices. Increased Focus on Re-quirements and Oversight Needed to Improve DOD's Acquisition Environment and Weapon System Quality. 2008.

GAO. U.S. Government Accountability Office. Military Service Chiefs’ Concerns Re-flect Need to Better Define Requirements before Programs Start. 2015.

Hooks, I. Writing good requirements. In: INCOSE International Symposium. 1994.

INCOSE. Guide to Writing Requirements. INCOSE-TP-2010-006-04| VERS/REV:4. 2023

Mavin, A.; Wilkinson, P.; Harwood, A.; Novak, M. Easy Approach to Requirements Syntax. In: 17th IEEE International Requirements Engineering Conference. IEEE, 2009.

Moreira, G; Cerqueira, C; Pleffken, D. Aplicando Engenharia de Sistemas Baseada em Modelos para suportar Projetos Aeroespaciais Militares no Brasil. In: Simpósio de Apli

cações Operacionais em Áreas de Defesa (SIGE). 2022.

Zenun, M N; Loureiro, G. A Framework for Requirements Concurrent Engineering. In: Concurrent Engineering Approaches for Sustainable Product Development in a Multi-Disciplinary Environment: Proceedings of the 19th ISPE International Conference on Concurrent Engineering. Springer London, 2013.




How to Cite

Barros, P. R. S., Coelho, R. C., Cerqueira, C. S., & Loureiro, G. (2024). Experiences with using ears for stakeholder requirements deve-lopment of the safe integration of unmanned aircrafts in the airspace project. OBSERVATÓRIO DE LA ECONOMÍA LATINOAMERICANA, 22(1), 2876–2890. https://doi.org/10.55905/oelv22n1-152




Most read articles by the same author(s)