Seleção de padrões para a arquitetura de software: uma abordagem baseada em procura de termos e sinônimos

• Ano de defesa: 2014
• Autor(a) principal: Azevedo, Rafael Pereira Martins
• Orientador(a): Braga, José Luis
• Banca de defesa: Olveira, Antônio de Pádua Albuquerque , Lisboa Filho, Jugurta , Leal, André Luiz de Castro
• Tipo de documento: Dissertação
• Tipo de acesso: Acesso aberto
• Idioma: por
• Instituição de defesa: Universidade Federal de Viçosa
• Programa de Pós-Graduação: Mestrado em Ciência da Computação
• Departamento: Metodologias e técnicas da Computação; Sistemas de Computação
• País: BR
• Palavras-chave em Português: Engenharia de software; Software - Desenvolvimento
• Palavras-chave em Inglês: Software engineering; Software - Development
• Área do conhecimento CNPq: CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO
• Link de acesso: http://locus.ufv.br/handle/123456789/2686

The transformation of requirements into software architecture is an activity that requires a high degree of competence, given that the decisions made in this process affect all subsequent cycles of the project. A well-designed software architecture maximizes the degree of compliance with the requirements of the system. The choice of compatible solutions for the problem is a key to the success of a software architecture. The reuse of solutions previously used successfully in similar problems reduces risk and increases the quality of the architecture. Architectural patterns follows this idea once they are used to document architectural solutions to recurring problems. The huge amount of patterns, the amount of information embodied into their description and the unfeasibility of a software developer to know all this information, or buy them in a short time are some of the motivations to develop techniques, methods and tools that assist in selection of the most appropriate pattern for each kind of system. Our objective is defining an approach to generate appropriated recommendations according to the requirements of a proposed system. These recommendations are based on the occurrence of key terms used to both describe software problems and describe patterns. The methodological steps for the construction of the approach includes defining what kind of information may be involved in software architecture decisions, constructing an initial set of key terms from the literature, defining how the search may be conducted in accordance with these descriptions of software patterns and evaluating the results obtained from the use of the approach. The results were analyzed using metrics and comparisons with recommendations in the literature and indicated satisfactory performance of the approach.