Durán Toro, AmadorBernárdez Jiménez, BeatrizToro Bonilla, MiguelCorchuelo Gil, RafaelRuiz Cortés, AntonioPérez Castellanos, José Antonio2021-12-092021-12-091999Durán Toro, A., Bernárdez Jiménez, B., Toro Bonilla, M., Corchuelo Gil, R., Ruiz Cortés, A. y Pérez Castellanos, J.A. (1999). Expressing Customer Requirements Using Natural Language Requirements Templates and Patterns. En CSCC 1999: 3rd World Multiconference on Circuits, Systems, Communications and Computers (IEEE/WSES/IMACS) (3531-3536), Athens, Greece: WSEAS.960-8052-02-5https://hdl.handle.net/11441/128147Expressing customer requirements so they can be understood not only by requirements engineers but also by noncomputer professional customers is not an easy task. Natural language is frequently the usual choice for expressing customer requirements in spite of its well–known problems, but using more formal notations too early is a risky choice that can make requirements impossible to understand for customers and users. In addition, using natural language do not guarantee understanding. Requirements engineers do not usually have good writing skills, and sometimes requirements expressed in natural language are not understood because of the poor way they are written. In this paper, we propose to use requirements templates and patterns to improve requirements expression. We have identified two types of requirements patterns: linguistic patterns, which are very used, well– understood, sentences in natural language requirements descriptions that can be parameterized and integrated into templates, and requirements patterns, which are generic requirements templates that are found very often during the requirements elicitation process and that can be reused with some adaptation.application/pdf6engAttribution-NonCommercial-NoDerivatives 4.0 Internacionalhttp://creativecommons.org/licenses/by-nc-nd/4.0/Requirements EngineeringRequirements ElicitationRequirements PatternsRequirements ReuseExpressing Customer Requirements Using Natural Language Requirements Templates and Patternsinfo:eu-repo/semantics/conferenceObjectinfo:eu-repo/semantics/openAccess