Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • 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)Licentiate thesis, comprehensive summary (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 architec-ture 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 architec-ture 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
Karlskrona: University of Karlskrona , 1999. , 146 p.
Series
Blekinge Tekniska Högskola Forskningsrapport, ISSN 1103-1581
Keyword [en]
Software architecture, design
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-00133Local ID: oai:bth.se:forskinfo8569FE80FD5CFBCCC12568A3002CAC1BISBN: HK-R-RES--99/10 OAI: oai:DiVA.org:bth-00133DiVA: diva2:837789
Note
A full text version of this licentiate is available as Research Report 10/99Available from: 2012-09-18 Created: 2000-03-15 Last updated: 2015-06-30Bibliographically approved

Open Access in DiVA

No full text

Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

Total: 51 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • 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