Conference Paper

Diseño de un Documento para la Elicitación y Especificación de Requerimientos: Caso Práctico

Conference: Cuarto Encuentro de Informática y Gestión

ABSTRACT En este trabajo se presenta el diseño de un documento para la elicitación y especificación de requerimientos. Se realiza un estudio de distintas metodologías para Ingeniería de Requerimientos (IR) y el estándar IEEE 830-1998. Posteriormente se aplica a un caso de estudio para evaluar su comportamiento. La principal contribución de este trabajo es presentar una propuesta de documento para la elicitación y especificación de requerimientos de software, basado en estándares de la industria. Los resultados iniciales permiten concluir que la aplicación de este documento en el caso de estudio, disminuye los problemas en el proceso de desarrollo de la organización estudiada.

Download full-text

Full-text

Available from: Mauricio Diéguez, Aug 28, 2015
3 Followers
 · 
624 Views
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Se presenta un marco metodológico de apoyo a la fase de requerimientos. Este incluye la definición de etapas y actividades de modo de obtener la especificación de la solución técnica que mejor apoye los objetivos de la organización. Esta última consideración provocará que los sistemas de información desarrollados se encuentren desde su concepción, alineados al negocio. Se entrega un método bien definido, al cual se le pueden adscribir distintas técnicas, incluyendo una guía para la captura de información mediante entrevistas con usuarios.
    01/2004;
  • [Show abstract] [Hide abstract]
    ABSTRACT: This paper presents a methodology for developing the requirements for general purpose scientific computing software. The first step in the methodology is to determine the general purpose scientific software of interest. The second step consists of a commonality analysis on this identified family of general purpose tools to document the terminology, commonalities and variabilities. The commonality analysis is then refined in the third step into a family of specific requirements documents. Besides fixing the variabilities and their binding times, each specific requirements document also shows the relative importance of the different nonfunctional requirements, for instance using the analytic hierarchy process (AHP). The new methodology addresses the challenge of writing validatable requirements by including solution validation strategies as part of the requirements documentation. To illustrate the methodology an example is shown of a solver for a linear system of equations
    14th IEEE International Conference on Requirements Engineering (RE 2006), 11-15 September 2006, Minneapolis/St.Paul, Minnesota, USA; 01/2006
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Introducing requirements engineering appears to involve a cultural change in organizations. Such a cultural change requires that requirements are defined and managed systematically, not only from a technical point of view, but also from the customers' and users' points of view. This paper describes experiences gained from four Finnish organizations that have started to introduce requirements engineering to their product development. The goal of this study was to evaluate which factors support, and which prevent, a cultural change. Linking business goals to technical requirements via user needs and user requirements was one of the key improvement actions that supported cultural change. Eliciting needs directly front real users and representing user requirements in the form of use cases were also key activities. However, bringing about a change of culture was challenging because both managers and product development engineers held beliefs that prevented active user need elicitation and systematic user requirement documentation.
    Requirements Engineering, 2002. Proceedings. IEEE Joint International Conference on; 02/2002
Show more