Bacharelado em Ciência da Computação (Sede)
URI permanente desta comunidadehttps://arandu.ufrpe.br/handle/123456789/6
Siglas das Coleções:
APP - Artigo Publicado em Periódico
TAE - Trabalho Apresentado em Evento
TCC - Trabalho de Conclusão de Curso
Navegar
5 resultados
Resultados da Pesquisa
Item Os efeitos da (in)felicidade no processo dedesenvolvimento de software(2019) Falcão, Tiago Coutinho; Marinho, Marcelo Luiz Monteiro; http://lattes.cnpq.br/3362360567612060; http://lattes.cnpq.br/8796523691341550In the software development process, the main actor responsible for directly impacting production is the individual.With the increase of literature and professional experiences,as well as the importance of studying the human being, recent studies involving the human aspects in software engineering seek to relate psychological factors with exact sciences. Studies show that emotions such as (un) happiness in a software development environment are directly linked to software quality, affecting developer performance.Understanding happiness and unhappiness can be worked out in ways that improve work environment, productivity, and developer motivation. This paper aims to identifythe effects of (un) happiness on the performance of software developers operating in the state of Pernambuco. In this paper, we will analyze the effects and moderating fac-tors that influence the performance of developers when they are happy and un happy during the software development process. Based on a literature review and the opin-ion of those involved in software development, through a questionnaire, which was at-tended by 71 developers, the moderating factors capable of emotionally influencing theindividual leading to the improvement or worsening of their performance were raised.These include: negatively influencing mental and physical health and team motivation as a positive moderating factor.Although some companies have flexibility in many ways such as clothing, coffee breaks and leisure spaces, developer attention is often not explored individually. In this paper, we can conclude that factors such as Mental Health prove that care for the well-being of the individual is extremely important for the proper functioning of the development process.Item A Diagnoses Instrument for Software Engineers’ Soft Skills(2019) Bastos, Thiago Alves; Sampaio, Suzana Cândido de Barros; http://lattes.cnpq.br/0066131495297081; http://lattes.cnpq.br/9312633017399857The use of Agile Methodologies among the Software Development Projects have beingin creasing in recent years. These methodologies have a set of values and principles which are people-centered, increasing the importance of the people factors for the success of projects using Agile methodologies. However, these factors are not fully understood by practitioners who work within Agile teams. This reality created a gap between what the companies are expecting from their Software Engineers and whatthey really know, in terms of Soft Skills, especially in their first-time job. Therefore, basedon a Literature Review and on the opinion of the Software Engineers working withinAgile Teams in the Digital Port of Recife, this work developed the MVP of an instrument capable of making a self evaluation of the 8 most important Soft Skills for a Software Engineer working in an Agile environment. Raising awareness about the relevance ofthe Soft Skills for the career of a Software Engineer, highlighting what are the mostrelevant Soft Skills for them and also reducing the existent gap in the IT job market.Moreover, during this study it was created a Soft Skill Catalog, containing the synonyms and the definitions of these Soft Skills found in the Literature. Finally, it was possible to realize the relevance of the Soft Skills for the Software Engineers where Leader ship and Negotiation were the two less important and Communication was the most important and the developed instrument came out as an extremely important instrument, specially for the Software Engineers in the beginning of the career. More over, it was also possible to realize that there aren’t enough activities inside the companies to improve the Soft Skills of their Software Engineers and the existent activities are not aligned with their expectations.Item Políticas para desenvolvimento de software seguro em times ágeis(2019) Bezerra, Carlos Magnum Matias; Sampaio, Suzana Cândido de Barros; http://lattes.cnpq.br/0066131495297081; http://lattes.cnpq.br/9077153013471246The values and principles of agile methodology ain to aggregate value to the business in a quick manner, being this agility, one of the critics factors for the successof this approaches. This success is crucial to attend the constant rising demand forsoftware, generated by the necessity of digital transformation. Currently, another concern, also resulting of this necessity, has gained more visibility, the cyber secu-rity. A lot of companies that have migrated for the digital world did not have thedue caution with the present threats in this scenery. As consequence, many security problems have being espoused in this past few years, this problems, tent to resultin social and financial losses. Software being one of the computational assets with the biggest expulser to this threats, the search for cyber security tend to become ademand. In this scenery, emerge the necessity to include security practices to the everyday live of the agile team. With the intent to contribute to the resolution ofthis task, this paper has as his goal to: establish cyber security policies, aggregating practices destined to the inclusion of security attributes to software projects, being developed for agile teams. To achieve this, it was necessary to perform a exploratory research through a bibliographic survey, to obtain an initial understanding of the problem and of the main approaches used to solve it. From the bibliography that itwas found it was considered only the research that present practices that included cyber security activities on software projects. Based on predefined criteria, an initialfiltering of the surveyed practices was conducted. The resulting subset was evaluatedby an agile development team with security expertise. The result of this evaluation evidenced the 14 (fourteen) most relevant practices and the stages of the development process to which they belonged. From the selected practices, five (5) policieswere structured and organized, then evaluated by experts, through interviews, tojudge their benefits for safety and applicability in agile teams. From the result of this assessment, it was concluded that 3 (three) of the policies were sufficiently ap-plicable to agile teams and contribute to project safety. Already 2 (two) of them,despite the security benefits, still need adjustments to make the incorporation viablein the agile world.Item Engenharia de software e métodos ágeis como forma de Inclusão(2019) Silva, Anderson Mateus da; Sampaio, Suzana Cândido de Barros; http://lattes.cnpq.br/0066131495297081; http://lattes.cnpq.br/5385133978429474Agile Methodologies have brought newi nsightint o how to develop software by focusing on individuals and relationships, on people and not on the software developed. Agile Methods also value the list of teams that have diversity, but only professional diver-sity is considered, where teams with professionals with different skills and knowledge facilitate self-sufficiency and consequently self-performance. However, the concept of diversity goes beyond this perspective, it is necessary to think about social diversity,think about inclusion and more than just include, integrate people into the team, inte-grate them into the organization. The human aspects of software engineering, studiedover 40 years ago, relate how individuals can develop their behavioral skills with in the context of software building environments. Such aspects can be enhanced through ag-ile practices, however, such practices do not actually have the perspective of inclusion,especially when talking about people with disabilities, so it is up to the team to create their own adaptations when this need exists.In this context,the objective of this paper isto identify the main techniques present in the literature, confront them with the reality of specialists who work ormanage agilete ams,being those with disabilities or people who worked coordinating teams with people with disabilities, and understand the challengesthey face during the developed projects. Based on a literature review and the opinionof agile practitioners through interviews, a series of techniques and strategies havebeen raised to help promote inclusion in agile teams. These include the Daily Meeting,Pair Programming, Planning Meeting, Review Meeting, Retrospective, Effort Estimat-ing, Workshop, and Code Challenges. Despite the use of these techniques, reliance onexternal factors such as specific tools or knowledge of sign language and inattention to make the environment conducive for professionals to feel confident and empoweredare the main challenges faced by agile teams with people with disabilities. Finally, acatalog is also proposed to support inclusion initiatives in agile teams, containing themain techniques mentioned in the literature and by agile professionals.Item Uma abordagem para tradução de uma linguagem de programação de robôs para um modelo formal(2018) Pereira, Iverson Luís; Nogueira, Sidney de Carvalho; http://lattes.cnpq.br/9171224058305522; http://lattes.cnpq.br/1186672408246777There is an increasing interest in virtual robot programming environments for educational purposes in recent years. These environments are an alternative to the use of real robots, which have a high acquisition value. Automatic verification of robot programs is a demand of students and teachers that expect to have fast and automatic feed back about the correctness of robot programs.However,no free software provides an automatic verification of virtual robot programs. This work proposes an approach for the automatic verification of virtual robot programs authored in the educational language called ROBO. We propose a compiler that reads programs written in ROBO and translates its source code into a formal notation called CSP (Communicating Sequential Processes), which is the input to a model checking tool called FDR (FailuresDivergences Refinement). The compiler was implemented using the facilities of the Spoofax framework, which is used to define a parser for the ROBO language and a set of translation rules from ROBO to CSP. This work removes a limitation of our previous verification approach that does not perform the verification of ROBO programs containing variables and procedures. A significant contribution is the extension of the verification approach to allow the automatic analysis of ROBO programs with variables and procedures.The extension consists of the modification of the compiler Grammar by the inclusion of variables and procedures and the inclusion of translation rules that define the formal semantics for the elements added into the grammar.Moreover, the work proposes a tool that makes transparent the translation process from ROBO to CSP and the automatic verification using FDR.We validate the approach using the proposed tool to verify the behavior of a ROBO program with variables and procedures.