AAAntonio Juarez Alencar

Antonio Juarez Alencar

*This is an algorithmically generated author record based on publicly available information.

Antonio Juarez Alencar has a total of 11 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    Risk Factors in the Software Deployment Phase: A Case Study Applied in two Brazilian Government Companies

    by Lidvaldo José Dos Santos, Sildenir Alves Ribeiro, Eber Assis Schmitz, Mônica Ferreira Da Silva, Antonio Juarez Sylvio Menezes De Alencar

    This work presents the results of a case study to identify the main risk factors in the software deployment phase involving two public Brazilian companies. The case study was developed through several on-site visits to monitor the deployment of the system adopted by companies and conduct interviews with team managers. The data were acquired mainly through questionnaires applied to the technical team (analysts and developers) involved with the software implementation. After acquiring the data, an empirical analysis was carried out, where the Risk Factors (RF) and the Containment Strategies (CS) identified in the literature were compared with the RF and CS found in the software deployment phase of the two companies. As a result, this work presents 11 risk factors and 14 Containment strategies found in the literature, in addition to a total of 9 RF and 9 CS recorded in the implementation of the software in companies A and B, which had not yet been cataloged in the literature.


  • Open Access

    Facilitators and barriers that influence Nursing Professionals in the Adoption of Information Systems:

    by Arlindo Souza Amaral Neto, Renato Montaleão Brum Alves, Mônica Ferreira da Silva, Éber Assis Schmitz, Antonio Juarez Alencar

    Through a systematic literature review, the current research aimed to acknowledge the main facilitators and barriers that influence the adoption of Information Systems by nursing professionals. Furthermore, it listed the principal theoretical models used to measure technology acceptance and the methods used to perform data collection. It was possible to see that TAM was the model with the highest frequency of appearance. It was also was possible to identify 19 (nineteen) facilitators and 23 (twenty-three) barriers reported in the selected studies. The findings allowed us to understand better how the phenomenon occurs, what can be worked on to improve technology acceptance, and allow new and in-depth studies to be carried out.


  • A Dynamic Job Shop Model for Scheduling Tasks in a Software Development Environment

    by Sildenir Alves Ribeiro, Eber Assis Schmitz, Mônica Fereira Da Silva, Antônio Juarez Sylvio Menezes De Alencar

    This work proposes a Dynamic Job Shop Scheduling (DJSS) model for scheduling the task in a software production environment. The aim is to organize the insertion of tasks in the shop in a precedence order previously defined that obeys the mapping of the critical path and the critical chain to identify constraints in the productive process. The complexity and dynamism of the software development environment require a mature and adjusted process that enables management throughout its extension. Therefore, the Unified Process (UP) was used in conjunction with the Theory of Constraints (TOC) in the Software Development Process (SDP). The UP requires an efficient model for the processing of activities, given by the set of independent variables involved in the process. For this reason, a model to programming the task based on dynamic scheduling was developed. The problem around the DJSS is to program the tasks in the shop in a way that allows to identify one or more production lines in the shop with constraints of capacity at runtime. A capacity constraint is any element that disturbs the productive process, causing L={Mi Aj} to have delivery (DA) of less than 100% of the artifacts, given by the set of jobs (jn) scheduled. The resource with capacity constraint limits the production of the machines in the production line, leading to bottlenecks in the production process. A bottleneck, in turn, is denoted by the production limitation of a machine (people) caused by one or more capacity constraints that imply maximum production, which in this case is defined by D={Mi, Aj=100%}. In this work, the maximum production is given by the set of tasks processed in each of the phases of the UP and according to the productive calendar, which delimits the deadline of each delivery and establishes the budget of hours for the shop. The set of tasks scheduled and "rescheduling" and properly processed in all phases define the total production of each machine. The use of DJSS facilitated the organization and management of insertion and rescheduling operations in the shop and as result, produced data to measure the effort/time that allowed identifying the bottleneck of the software production process.


  • Open Access

    FATORES DE RISCO NA FASE DE IMPLANTAÇÃO DE SOFTWARE: UMA REVISÃO DA LITERATURA

    by Lidvaldo José dos Santos, Sildenir Alves Ribeiro, Eber Assis Schmitz, Mônica Ferreira da Silva, Antônio Juarez Sylvio Menezes de Alencar

    No processo de implantação de software, inúmeras falhas podem ocorrer, comprometendo a entrega ao cliente, tais como a falta de recursos, o surgimento de novos requisitos e a não aceitação pelos usuários das mudanças impostas devido à implantação. Estas mudanças estão associadas à adoção de novas tecnologias ou uma nova metodologia de trabalho. Este artigo mostra os resultados de uma revisão da literatura com o intuito de identificar os principais fatores de risco envolvidos neste processo, suas causas e estratégias de contenção durante a entrega do software ao usuário final. A partir deste mapeamento, serão apresentados estudos primários que tratam os fatores de riscos na fase de implantação de projetos de software. A partir dos resultados obtidos, apresentamos onze fatores que visam contribuir na eficácia do gerenciamento de riscos de software durante a fase de implantação.


  • Open Access

    Testes Funcionais de Web Services RESTful a partir de Modelos UML

    by Thiago Silva-De-Souza, Alexandre Luis Correa, Eber Assis Schmitz, Antonio Juarez Alencar

    This paper presents an approach for RESTful Web Services test case generation. RESTful Web Services have features that are not fully covered by traditional software testing techniques. The proposed approach uses model transformation techniques to generate platform independent test cases from UML class models enriched with Object Constraint Language (OCL) constraints. These test cases are then transformed into platform specific test cases that can be used to verify the implementation of CRUD RESTful Web Services. An experimental study showed that the proportion of testers, using ad hoc techniques capable of achieving at least 95% coverage restrictions approach is covered by at most 20%. Este trabalho apresenta uma abordagem para geração de casos de teste de Web Services RESTful. A abordagem proposta utiliza técnicas de transformação de modelos para gerar casos de teste independentes de plataforma a partir de modelos de classes UML enriquecidos com restrições Object Constraint Language (OCL). Tais casos de teste são, então, transformados em casos de teste específicos de plataforma que podem ser usados para verificar a implementação de Web Services RESTful do tipo CRUD. Um estudo experimental mostrou que a proporção de testadores, utilizando técnicas ad hoc, capaz de alcançar ao menos 95% da cobertura de restrições cobertas pela abordagem é de no máximo 20%. Este trabalho apresenta uma abordagem para geração de casos de teste de Web Services RESTful. A abordagem proposta utiliza técnicas de transformação de modelos para gerar casos de teste independentes de plataforma a partir de modelos de classes UML enriquecidos com restrições Object Constraint Language (OCL). Tais casos de teste são, então, transformados em casos de teste específicos de plataforma que podem ser usados para verificar a implementação de Web Services RESTful do tipo CRUD. Um estudo experimental mostrou que a proporção de testadores, utilizando técnicas ad hoc, capaz de alcançar ao menos 95% da cobertura de restrições cobertas pela abordagem é de no máximo 20%.

  • Open Access

    Elaboration of use case specifications

    by F. G. Dias, E. A. Schmitz, M. L. M. Campos, A. L. Correa, A. J. Alencar