Abstract

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.

Full Text
Published version (Free)

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 call