Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Design and Evaluation of Software Architecture
Responsible organisation
1999 (English)Report (Other academic)
Abstract [en]

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 structure 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 knowl-edge of the modification volume required for the realization of each sce-nario. 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.

Place, publisher, year, edition, pages
1999.
Series
Blekinge Tekniska Högskola Forskningsrapport, ISSN 1103-1581 ; 10
Keywords [en]
software architecture
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-00125Local ID: oai:bth.se:forskinfo3A18DED3A4A0876DC12568A3002CABFCOAI: oai:DiVA.org:bth-00125DiVA, id: diva2:838171
Note
This thesis is submitted to the Research Board at University of Karlskrona/Ronneby, in partial fulfillment of the requirements for the degree of Licentiate of Engineering.Available from: 2012-09-18 Created: 2000-03-15 Last updated: 2018-01-11Bibliographically approved

Open Access in DiVA

fulltext(477 kB)15019 downloads
File information
File name FULLTEXT01.pdfFile size 477 kBChecksum SHA-512
697554cb4b10f8958b96db308b1b9204c06b21bc7e92143308855b8bea3d10a2aa3ddaa80ff22bd4ab50d388171cc9a06ea819c6e0caece0c61d60646b65a340
Type fulltextMimetype application/pdf

Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 15023 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 616 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf