Examinando por Autor "Zapata-Jaramillo, C. M. (Carlos Mario)"

Mostrando 1 - 4 de 4
  • Miniatura
    PublicaciónAcceso abierto
    Generación del diagrama de secuencias de UML 2.1.1 desde esquemas preconceptuales
    (2014-05-12) Zapata-Jaramillo, C. M. (Carlos Mario); Garcés, G. L. (Gilma Liliana)
    Sequence diagram is a conceptual schema for representing behavior of a system. For performing such a task, it employs the object spec from a scenario and the sequence of messages exchanged among the objects. These elements describe a transaction of the system. Several approaches try the automated generation of conceptual models (like sequence diagram). Some of them use natural language as a starting point, but they are focused on other diagrams. Some others are focused on sequence diagram, but they do not obtain elements like combined fragments describing several logical constraints of the system. Other approaches use source code as a starting point, but source code can be related to an advanced phase of the software development life cycle. In this paper we define a method based on heuristic rules for obtaining automatically the elements of the sequence diagram (including combined fragments) from pre-conceptual schemas. These heuristic rules are implemented in the AToM3 tool and applied in a case study.
  • Miniatura
    PublicaciónAcceso abierto
    Un método de ingeniería inversa de código JAVA hacia diagramas de secuencias de UML 2.0
    (2014-05-09) Zapata-Jaramillo, C. M. (Carlos Mario); Ochoa, O. A. (Óscar Andrés); Vélez, C.(Camilo)
    Software reverse engineering seems to be the process for helping software quality assurance and documentation in applications with low-quality analysis and design models. It also helps for decreasing maintenance cost and time. Currently, some CASE tools and research proposals assist analysts to develop reverse engineering process with UML diagrams as a result (especially class and sequence diagram). Some of them have reached experimental phases. Some others are focused more on class diagram and less on sequence diagram. A third group of CASE tools and proposals obtains sequence diagram, but the resulting diagram lacks some of the elements of the UML 2.0 specification. In this paper, we propose a method for automating the conversion of JAVA code into UML 2.0 sequence diagram, by means of the application of transformation rules for converting code elements to the diagram elements. We also present an example of the method application through a prototype named UNC-Inversor.
  • Miniatura
    PublicaciónAcceso abierto
    UNC-analista: hacia la captura de un corpus de requisitos a partir de la aplicación del experimento Mago de Oz
    (2014-05-08) Zapata-Jaramillo, C. M. (Carlos Mario); Olaya, N. (Natalí); Palacio, C. (Carolina)
    Requirements elicitation is one of the most important phases in software development process. A good requirements understanding can lead to better software products, achieving satisfaction of stakeholder needs. However, requirements-capture process is sometimes difficult for analysts, because of the face-to-face character of the meetings required for it and because of difficulties of people for expressing clearly their ideas. In this paper we present UNC-Analista, a proposal for Wizard-of-Oz experiment focused on the design of a dialogue-controlled system for helping the analyst labor in the requirements elicitation process. With this system will be possible to capture a requirements corpus, for leading a future development of an automatic requirements elicitation system.
  • Miniatura
    PublicaciónAcceso abierto
    Validación del método para la obtención automática del diagrama de objetivos desde esquemas preconceptuales
    (2014-05-08) Zapata-Jaramillo, C. M. (Carlos Mario); Lezcano-Rodríguez, L. A. (Luis Alfonso); Tamayo-Osorio, P. A. (Paula Andrea)
    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.