-
VII Jornadas Iberoamericanas de Ingeniería de Software e Ingeniería del Conocimiento 2008, Guayaquil, Ecuador, January 30 - February 1, 2008. Proceedings; 01/2008
-
RASI. 01/2007; 4:117-124.
-
VI Jornadas Iberoamericanas de Ingeniería del Software e Ingeniería del Conocimiento-JIISIC'07, 31 de Enero al 2 de Febrero del 2007, Lima, Perú; 01/2007
-
RASI. 01/2007; 4:35-42.
-
[show abstract]
[hide abstract]
ABSTRACT: This paper introduces a proposal for supporting text interpretation process. This proposal is based on automatic generation of Entity-Relationship Diagram (ERD) from text. ERD is a conceptual schema used in software engineering. Furthermore, we present DER usability in text interpretation process, as well as techniques of Natural Language Processing and software engineering used in their automatic derivation. The obtained results show how DER can be a useful tool in text interpretation process assistance due to the supply of automatic inferences. This work is part of the magisterial research: “Method for class diagram operations recognition from conceptual graphs” finished in National University of Colombia under assessment of the Software Engineering Gr oup.
Avances en Sistemas e Informática. 01/2007;
-
Memorias de la IX Conferenci a Iberoamericana de Software Engineering (CIbSE 2006), La Plata, Argentina, Abril 24-28, 2006; 01/2006
-
MICAI 2006: Advances in Artificial Intelligence, 5th Mexican International Conference on Artificial Intelligence, Apizaco, Mexico, November 13-17, 2006, Proceedings; 01/2006
-
RASI. 01/2005; 2:27-39.
-
RASI. 01/2005; 2:1-8.
-
RASI. 01/2004; 1:7-19.
-
Avances en Sistemas e Informática, ISSN 1909-0056, Vol. 5, Nº. 1, 2008, pags. 189-198.
-
[show abstract]
[hide abstract]
ABSTRACT: Software engineers use development methods to guarantee on-time delivery, keeping to budget and quality in their software applications. There are two kinds of development methods: plan-driven and agile methods. Both of them still have problems; these refer to resolving problems instead of thinking about them, they use informal or semi-formal artefacts and they leave consistency management to the analysts. The UNC-method (a problem-based software development method) is defined in this paper. The UNC-method is currently being developed in the Universidad Nacional de Colombia; it has been used by students from the School of Systems as part of their training in methodological software development during the last five years. The UNC-method is a mixture of well-known artefacts (i.e. UML diagrams and graphical user interfaces) and non-traditional approaches (e.g. causeand-effect diagram, KAOS goal diagrams and pre-conceptual schemas) used in trying to overcome the aforementioned problems. A case study is also used for exemplification purposes. Los ingenieros de software emplean los métodos de desarrollo para garantizar la entrega puntual, el cumplimiento de los presupuestos y la calidad de las aplicaciones de software. Existen dos tipos de métodos de desarrollo: los dirigidos por planes, y los ágiles. Ambos, aún presentan problemas: se refieren a la solución en lugar de pensar en el problema, usan artefactos formales o semiformales y dejan el manejo de la consistencia en manos de los analistas. En este artículo se define UNC-Method, un método de desarrollo de software basado en problemas, que se viene desarrollando en la Universidad Nacional de Colombia y que se usa en la Escuela de Sistemas como parte del entrenamiento en desarrollo metodológico de software a los estudiantes de dicha universidad durante los últimos cinco años. UNC-Method combina artefactos tradicionales del desarrollo de software (como los diagramas de UML y las interfaces gráficas de usuario) con enfoques no tradicionales en dicha disciplina (como los diagramas causa-efecto, los diagramas de objetivos de KAOS y los esquemas preconceptuales) en un esfuerzo por resolver los problemas antes mencionados. Además, se ejemplifica el método con un caso de estudio.
Ingeniería e Investigación, ISSN 0129-5608, Vol. 29, Nº. 1, 2009, pags. 69-75.
