Documenting software architecture rationale is essential to reuse and evaluate architectures, and several modeling and documentation guidelines have been proposed in the literature.
However, in practice creating and updating these documents rarely is a primary activity in most software projects, and rationale remains hidden in casual and semi-structured records, such as e-mails, meeting notes, wikis, and specialized documents.
The software element explains the rationale behind autonomous car initiatives by software corporations, but it also highlights the need for common international frameworks, first to test such vehicles and then to make them available for public use.
In (Bratthall et al. 2000), the authors present a controlled experiment which evaluates the impact of the use of design rationale documentation on software evolution.
Here, we document the survey's outcomes, review functionalities of available genome browser software platforms and offer our rationale for choosing the GBrowse software suite for MaizeGDB.
The paper reports the software architectural design, implementation tools and rationale for their selection, test and validation.
The rationale for why FDA-cleared software should be used for creation of the STL file is two-fold.
Rather than describing the structure of software systems, architectural decisions capture the design rationale and – often reusable – architectural knowledge.
The aim is to provide a rationale for homology computation in electromagnetic modeling software.
This is a simple and unobtrusive software tool that allows engineering designers to record their rationale as the design proceeds.
