Technological development has awakened interest on the part of the scientific community in researching to predict earthquakes. The article's objective is to know what variables, techniques, tools, and methodologies have been used in the different studies to predict earthquakes using machine learning techniques. To carry out the study, the Kitchenham methodology was used, which consists of three development phases: review planning, conducting, and reporting. In the planning phase, four research questions were posed; for this purpose, an exhaustive literature search was carried out. After carrying out the selection and exclusion criteria, the questions posed were developed, of which it was found that 15% of the variables to predict earthquakes were latitude, longitude, and depth. In comparison, 13% were the seismic magnitude. 17% of the most used techniques were Random Forest, followed by ...

This paper describes the implementation of a tool for automated generation of user stories from a graphical model. The objective-oriented modeling approach is applied, which uses the notation i*. The main rationale is that the business objective is not the one that changes, but the ways in which it can be achieved. Once the requirements are compiled through this model, user stories are generated automatically for later traceability. These comply with the basic standard proposed in agile methodologies ensuring that, when arriving at the hands of the developer, there are no ambiguities in either of the two perspectives: graphical and narrative. The results of the tests with developers and analysts, as well as the application of a questionnaire, showed that the proposed tool contributes directly to the establishment of precise, complete and consistent requirements, optimizing the time used ...

This paper describes the implementation of a tool for automated generation of user stories from a graphical model. The objective-oriented modeling approach is applied, which uses the notation i*. The main rationale is that the business objective is not the one that changes, but the ways in which it can be achieved. Once the requirements are compiled through this model, user stories are generated automatically for later traceability. These comply with the basic standard proposed in agile methodologies ensuring that, when arriving at the hands of the developer, there are no ambiguities in either of the two perspectives: graphical and narrative. The results of the tests with developers and analysts, as well as the application of a questionnaire, showed that the proposed tool contributes directly to the establishment of precise, complete and consistent requirements, optimizing the time used ...