A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit <a rel="external noopener" href="http://www.diva-portal.org/smash/get/diva2:838171/FULLTEXT01.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
Software Development and Professional Practice
The challenge in software development is to develop software with the right quality levels. The main problem is not to know if a project is technically feasible concerning functionality, but if a solution exists that meet the software quality requirements. It is therefore desired to get an early indication of the qualities of the resulting software. Software architecture is concerned with what modules are used to compose a system and how these modules are related to each other, i.e. the<span class="external-identifiers"> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1007/978-1-4302-3802-7_5">doi:10.1007/978-1-4302-3802-7_5</a> <a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/h7qttve4dffljoumaqwglyurlu">fatcat:h7qttve4dffljoumaqwglyurlu</a> </span>
more »... e of system. The software architecture of a system sets the boundaries for these qualities. Hence, to design the software architecture to meet the quality requirements is to reduce the risks of not achieving the required quality levels. In this thesis we present the experiences from a software architecture design project with two industry partners. Based on these we propose a method for reengineering architectures and exemplify by an applying the method on a real world example. The method is based on architecture transformations and software quality evaluation of the architecture. Further, we present a method for predicting software maintenance effort from the software architecture, for use in the design and reengineering method. The method uses change scenario profiles to describe future changes to the system and architecture impact analysis provide knowledge of the modification volume required for the realization of each scenario. The results from a quasi experiment supports that groups consisting of prepared members create better scenario profiles. Also, the results suggest that there is a large room for variation between scenario profiles created by individual persons.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20170812141520/http://www.diva-portal.org/smash/get/diva2:838171/FULLTEXT01.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext"> <button class="ui simple right pointing dropdown compact black labeled icon button serp-button"> <i class="icon ia-icon"></i> Web Archive [PDF] <div class="menu fulltext-thumbnail"> <img src="https://blobs.fatcat.wiki/thumbnail/pdf/ef/14/ef1416fae8aeab68a8dd0cca0b14126735c665d3.180px.jpg" alt="fulltext thumbnail" loading="lazy"> </div> </button> </a> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1007/978-1-4302-3802-7_5"> <button class="ui left aligned compact blue labeled icon button serp-button"> <i class="external alternate icon"></i> Publisher / doi.org </button> </a>