Arquitetura evolutiva e design emergente

• Autor(a) principal: Santaguida, Michael
• Data de Publicação: 2010
• Tipo de documento: Trabalho de conclusão de curso
• Idioma: por
• Título da fonte: Biblioteca Digital de Teses e Dissertações da PUC_SP
• Texto Completo: https://repositorio.pucsp.br/jspui/handle/handle/36678
• topic: CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO::METODOLOGIA E TECNICAS DA COMPUTACAO::ENGENHARIA DE SOFTWARE

The development of a software system architecture that is flexible to changes, at first, might seem like a complicated task. The reason is because decisions related to architecture are amongst the most crucial in a system software project, where a change of non-functional requirements during the project can generate large impacts. The purpose of this monograph is to show that you can develop an evolutionary architecture, able to meet the changes that arise during the project, by developing a design quality that makes the impact of change minimal. This monograph is divided as follows: In chapter 1, System Architecture will be addressed by showing what it is and its evolution from traditional to evolutionary architecture. In chapter 2, a better explanation of what an emerging design is with some examples will be given. In chapter 3, the following code qualities will be explained; encapsulation, cohesion, coupling, redundancy, readability and testability. Its importance to the system code will also be explained along with some examples. In chapter 4, some principles of software design and how it improves its quality will be shown along with some examples. In chapter 5, design patterns will be analyzed in terms of what they are, its benefits and how to implement them together along with some examples. In chapter 6, the techniques for Test-Driven Development will be shown along with a step-by-step explanation of how to use it and its benefits for an emergent design. To finalize, in chapter 7, the techniques of refactoring, which allows changes to the code with quality problems to a good quality code without affecting the external behavior system, will be shown and explained