During the requirements elicitation process, a group of analysts and stakeholders identify, capture, and integrate requirements. Textual or graphic descriptions capturing the most relevant concepts from the domain of a software application development are generated. Commonly, the initial phases-iden...

Full description

Autores:
Tipo de recurso:
Fecha de publicación:
2014
Institución:
Universidad de Medellín
Repositorio:
Repositorio UDEM
Idioma:
spa
OAI Identifier:
oai:repository.udem.edu.co:11407/1393
Acceso en línea:
http://hdl.handle.net/11407/1393
Palabra clave:
Controlled language
Natural language
Requirements elicitation
Rights
restrictedAccess
License
http://purl.org/coar/access_right/c_16ec
Description
Summary:During the requirements elicitation process, a group of analysts and stakeholders identify, capture, and integrate requirements. Textual or graphic descriptions capturing the most relevant concepts from the domain of a software application development are generated. Commonly, the initial phases-identifying and capturing requirements expressed in natural language-are executed by using techniques in which high analyst intervention and comprehensive knowledge of the context and the problem domain are required. Thus, a subjective, ambiguous, and error-prone process is implied, causing losses in the generation of the initial domain models (specified in a controlled language). In this paper we provide a synthesis of trends and conceptual approaches found in the state of the art concerning the natural language transformation into controlled language during the requirements elicitation process. Finally, we propose a pre-conceptual schema for representing the conceptual framework of the transformation process.