Defining DSL design principles for enhancing the requirements elicitation process
[EN] Requirements elicitation is concerned with learning and understanding of users w.r.t. a new software development. Frequently the methods employed for requirements elicitation are adapted from areas like social sciences that do not include executable (prototype based on) feedback. As a consequen...
| Autores: | , , , |
|---|---|
| Tipo de recurso: | artículo |
| Fecha de publicación: | 2012 |
| País: | España |
| Institución: | Universitat Politècnica de València (UPV) |
| Repositorio: | RiuNet. Repositorio Institucional de la Universitat Politécnica de Valéncia |
| Idioma: | inglés |
| OAI Identifier: | oai:riunet.upv.es:10251/43409 |
| Acceso en línea: | https://riunet.upv.es/handle/10251/43409 |
| Access Level: | acceso abierto |
| Palabra clave: | DSL Ingeniería de software Requerimientos de elicitación Software engineering Requirement elicitation LENGUAJES Y SISTEMAS INFORMATICOS |
| Sumario: | [EN] Requirements elicitation is concerned with learning and understanding of users w.r.t. a new software development. Frequently the methods employed for requirements elicitation are adapted from areas like social sciences that do not include executable (prototype based on) feedback. As a consequence, it is relative common to discover that the first release does not fit the requirements defined at the beginning of the project. Using domain-specific languages (DSLs) as an auxiliary tool for requirements elicitation is a commonly well accepted idea. Unfortunately, there are few works in the literature devoted to the definition of design principles to DSLs to be experienced in the frameworks of DSL developing such as ANTLR, Ruby and Curry. We propose to design principles for the DSL development (regardless of paradigm) wich are sufficient to model the domain in a requirements phase. Furthermore we enunciate a new profile for the requirements analyst and a set of elicitation steps. The use of DSLs not only give us an immediate feedback with the stakeholders; it also allows us to produce part of the real code. |
|---|