VALIDACIÓN DEL MÉTODO PARA LA OBTENCIÓN AUTOMÁTICA DEL DIAGRAMA DE OBJETIVOS DESDE ESQUEMAS PRECONCEPTUALES
VALIDACIÓN DEL MÉTODO PARA LA OBTENCIÓN AUTOMÁTICA DEL DIAGRAMA DE OBJETIVOS DESDE ESQUEMAS PRECONCEPTUALES
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
Copyright statement
The authors exclusively assign to the Universidad EIA, with the power to assign to third parties, all the exploitation rights that derive from the works that are accepted for publication in the Revista EIA, as well as in any product derived from it and, in in particular, those of reproduction, distribution, public communication (including interactive making available) and transformation (including adaptation, modification and, where appropriate, translation), for all types of exploitation (by way of example and not limitation : in paper, electronic, online, computer or audiovisual format, as well as in any other format, even for promotional or advertising purposes and / or for the production of derivative products), for a worldwide territorial scope and for the entire duration of the rights provided for in the current published text of the Intellectual Property Law. This assignment will be made by the authors without the right to any type of remuneration or compensation.
Consequently, the author may not publish or disseminate the works that are selected for publication in the Revista EIA, neither totally nor partially, nor authorize their publication to third parties, without the prior express authorization, requested and granted in writing, from the Univeridad EIA.
Show authors biography
Según el CDM (Custom Development Method), el desarrollo de aplicaciones de software suele empezar con una fase de definición, en la cual se determinan los procesos que se realizan en la organización que requiere el software, los problemas que motivan tal desarrollo y, especialmente, los objetivos asociados con las diferentes áreas de la organización. En esta fase, el diagrama de objetivos de KAOS (Knowledge Acquisition Automated Specification) se suele utilizar para describir los objetivos de alto nivel de la organización y dividirlos paulatinamente en subobjetivos hasta alcanzar los requisitos y expectativas de los interesados. El grupo de Ingeniería de Software de la Escuela de Sistemas de la Universidad Nacional de Colombia desarrolló un método para automatizar la obtención del diagrama de objetivos de KAOS a partir de esquemas preconceptuales, que son diagramas que describen los procesos y el vocabulario de una organización que desee desarrollar una aplicación de software. En este artículo se realiza la validación de dicho método, empleando para ello tres casos de estudio incluidos en la literatura especializada.
Abstract: According to the Custom Development Method (CDM), the first phase of the software development process is commonly the definition phase. Processes related to the organization in which the software application is needed, problems that motivates the development process, and objectives associated with several organizational areas are determined in this phase. KAOS (Knowledge Acquisition Automated Specification) goal diagram is used in this phase to describe high-level organizational goals and then divide them into sub-objectives concerned with the stakeholder needs and expectations. Software Engineering group of the Escuela de Sistemas of the Universidad Nacional de Colombia developed a method to automate the KAOS goal diagram obtaining from Pre-conceptual Schemas, which are diagrams to describe the organizational processes and vocabulary linked with the software development. We use in this paper three case studies in order to validate such a method. The case studies are reported in specialized papers about this issue.
Article visits 287 | PDF visits 148
