The architectural design of software systems is not a trivial task, requiring sometimes large experience and knowledge accumulated for years. Reference architectures have been increasingly adopted as a means to support such task, also contributing to the standardization and evolution of these systems. Although considerable time and effort are devoted to design these architectures, an outdated description is still found in several of them and, as a consequence, resulting in their non-continuation. This article presents guidelines to evolve the description of reference architectures, considering different types of stakeholders and required tasks. To complement our statement that the guidelines are correct by construction as they were grounded in widely known international standard ISO/IEC/IEEE 42010 and literature, we also briefly present a qualitative analysis comparing the guidelines with an ad hoc way (commonly occurred in reference architectures). We believe solutions like these guidelines are necessary and could further contribute to the sustainability and longevity of reference architectures.
翻译:软件系统的建筑设计并非一项微不足道的任务,有时需要大量的经验和多年积累的知识,参考结构日益成为支持这种任务的手段,同时也有助于这些系统的标准化和演变,虽然在设计这些结构方面投入了大量的时间和精力,但其中一些结构仍然有过时的描述,因而导致这些结构不再延续。本条款提出了制定参考结构说明的指导方针,同时考虑到不同类型的利益攸关方和所需任务。为了补充我们的说法,即这些指南在建筑上是正确的,因为它们以广为人知的国际标准ISO/IEC/IEEE 42010和文献为基础,我们还简要地提出了一份定性分析,将准则与临时方式进行比较(通常在参考结构中出现)。我们认为,类似这些指导方针的解决办法是必要的,可以进一步促进参考结构的可持续性和寿命。