mdh.sePublications
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
Using Dependency Model to Support Software Architecture Evolution
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0001-7153-3785
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-5278-755X
Mälardalen University, School of Innovation, Design and Engineering.
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-0921-0878
2008 (English)In: Automated Software Engineering - Workshops, 2008. ASE Workshops 2008. 23rd IEEE/ACM International Conference on, 2008, p. 82-91Conference paper, Published paper (Refereed)
Abstract [en]

Evolution of software systems is characterized by inevitable changes of software and increasing software complexity, which in turn may lead to huge maintenance and development costs.  For long-lived systems, there is a need to address and maintain evolvability (i.e. a system’s ability to easily accommodate changes) during the entire lifecycle. As designing software for ease of extension and contraction depends on how well the software structure is organized, this paper explores the relationships between evolvability, modularity and inter-module dependency. Through a case study of an industrial power control and protection system, we describe our work in managing its software architecture evolution, guided by the dependency analysis at the architectural level.  The paper includes also the main analysis results, our experiences and reflections during the dependency analysis process in the case study.

Place, publisher, year, edition, pages
2008. p. 82-91
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:mdh:diva-4437DOI: 10.1109/ASEW.2008.4686324ISI: 000266630600021Scopus ID: 2-s2.0-58049190615ISBN: 978-1-4244-2776-5 (print)OAI: oai:DiVA.org:mdh-4437DiVA, id: diva2:127329
Conference
Aramis 2008 - 1st International Workshop on Automated engineeRing of Autonomous and runtiMe evolvIng Systems In conjunction with ASE2008 the 23rd IEEE/ACM International Conference on Automated Software Engineering; L'Aquila; Italy; 16 September 2008 through 16 September 2008
Available from: 2008-12-04 Created: 2008-12-04 Last updated: 2018-08-21Bibliographically approved
In thesis
1. Software Architecture Evolution and Software Evolvability
Open this publication in new window or tab >>Software Architecture Evolution and Software Evolvability
2009 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

Software is characterized by inevitable changes and increasing complexity, which in turn may lead to huge costs unless rigorously taking into account change accommodations. This is in particular true for long-lived systems. For such systems, there is a need to address evolvability explicitly during the entire lifecycle, carry out software evolution efficiently and reliably, and prolong the productive lifetime of the software systems.

In this thesis, we study evolution of software architecture and investigate ways to support this evolution.           The central theme of the thesis is how to analyze software evolvability, i.e. a system’s ability to easily accommodate changes. We focus on several particular aspects: (i) what software characteristics are necessary to constitute an evolvable software system; (ii) how to assess evolvability in a systematic manner; (iii) what impacts need to be considered given a certain change stimulus that results in potential requirements the software architecture needs to adapt to, e.g. ever-changing business requirements and advances of technology.

To improve the capability in being able to on forehand understand and analyze systematically the impact of a change stimulus, we introduce a software evolvability model, in which subcharacteristics of software evolvability and corresponding measuring attributes are identified. In addition, a further study of one particular measuring attribute, i.e. modularity, is performed through a dependency analysis case study.

We introduce a method for analyzing software evolvability at the architecture level. This is to ensure that the implications of the potential improvement strategies and evolution path of the software architecture are analyzed with respect to the evolvability subcharacteristics. This method is proposed and piloted in an industrial setting.

The fact that change stimuli come from both technical and business perspectives spawns two aspects that we also look into in this research, i.e. to respectively investigate the impacts of technology-type and business-type of change stimuli.

Place, publisher, year, edition, pages
Västerås: Mälardalen University, 2009
Series
Mälardalen University Press Licentiate Theses, ISSN 1651-9256 ; 97
National Category
Computer Engineering
Research subject
Computer Science
Identifiers
urn:nbn:se:mdh:diva-4540 (URN)978-91-86135-15-7 (ISBN)
Presentation
2009-01-26, Gamma, Västerås, 14:15 (English)
Opponent
Supervisors
Available from: 2009-01-09 Created: 2008-12-17 Last updated: 2018-01-13Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records BETA

Pei Breivold, HongyuCrnkovic, IvicaLarsson, Stig

Search in DiVA

By author/editor
Pei Breivold, HongyuCrnkovic, IvicaLand, RikardLarsson, Stig
By organisation
School of Innovation, Design and Engineering
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 67 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