Introducing an architectural conformance process in continuous integration

Registro completo de metadados
MetadadosDescriçãoIdioma
Autor(es): dc.creatorPinto, Arthur F.-
Autor(es): dc.creatorTerra, Ricardo-
Autor(es): dc.creatorGuerra, Eduardo-
Autor(es): dc.creatorSabbas, Fernanda São-
Data de aceite: dc.date.accessioned2026-02-09T11:09:57Z-
Data de disponibilização: dc.date.available2026-02-09T11:09:57Z-
Data de envio: dc.date.issued2019-04-25-
Data de envio: dc.date.issued2019-04-25-
Data de envio: dc.date.issued2017-
Fonte completa do material: dc.identifierhttps://repositorio.ufla.br/handle/1/56621878-
Fonte completa do material: dc.identifierhttp://www.jucs.org/jucs_23_8/introducing_an_architectural_conformance-
Fonte: dc.identifier.urihttp://educapes.capes.gov.br/handle/capes/1135134-
Descrição: dc.descriptionAs software evolves, developers usually introduce deviations from the planned architecture, due to unawareness, conflicting requirements, technical difficulties, deadlines, etc. This occurs in systems with an explicit division of responsibility between groups of classes, such as modules and layers. Although there are architectural conformance tools to identify architectural violations, these tools are underused and detected violations are rarely corrected. To address these shortcomings, this article introduces an architectural conformance process into continuous integration. Thus, the conformance process is triggered by every code integration and, when no violations are detected, the code is integrated into the repository. The implemented tool, called ArchCI, supports the proposed solution using DCL (Dependency Constraint Language) as underlying conformance technique and Jenkins as the Continuous Integration server. We also evaluated the applicability of our proposed solution in a real-world Java project where we incrementally introduced 44 constraints through six releases. As the result, our process was able to detect 42 violations, which have always been fixed before the ensuing release.-
Idioma: dc.languageen-
Publicador: dc.publisherJournal of Universal Computer Science-
Direitos: dc.rightsrestrictAccess-
???dc.source???: dc.sourceJournal of Universal Computer Science-
Palavras-chave: dc.subjectSoftware architecture erosion-
Palavras-chave: dc.subjectArchitectural conformance-
Palavras-chave: dc.subjectContinuous integration-
Palavras-chave: dc.subjectErosão de arquitetura de software-
Palavras-chave: dc.subjectConformidade arquitetônica-
Palavras-chave: dc.subjectIntegração contínua-
Título: dc.titleIntroducing an architectural conformance process in continuous integration-
Tipo de arquivo: dc.typeArtigo-
Aparece nas coleções:Repositório Institucional da Universidade Federal de Lavras (RIUFLA)

Não existem arquivos associados a este item.