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
Component-Based and Service-Oriented Software Engineering: Key Concepts and Principles
ABB AB, Corporate Research, Västerås, Sweden. (BESS)ORCID iD: 0000-0001-7153-3785
ABB AB, Corporate Research, Västerås, Sweden.ORCID iD: 0000-0002-6200-4125
2007 (English)In: EUROMICRO 2007 - Proceedings of the 33rd EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 200, 2007, Vol. Article number 4301060Conference paper, Published paper (Refereed)
Abstract [en]

Component-based software engineering (CBSE) and service-oriented software engineering (SOSE) are two of the most dominant engineering paradigms in current software community and industry. Although they have continued their development tracks in parallel and have different focus, both paradigms have similarities in many senses, which also have resulted in confusion in understanding and applying similar concepts or the same concepts designated differently. In this paper, we present a comparison analysis framework of CBSE and SOSE and analyze them from a variety of perspectives. We discuss as well the possibility of combining the strengths of the two paradigms to meet non-functional requirements.

The contribution of this paper is to clarify the characteristics of CBSE and SOSE, shorten the gap between them and bring the two worlds together so that researchers and practitioners become aware of essential issues of both paradigms, which may serve as inputs for further utilizing them in a reasonable and complementary way.

Place, publisher, year, edition, pages
2007. Vol. Article number 4301060
National Category
Computer Systems
Identifiers
URN: urn:nbn:se:mdh:diva-4435DOI: 10.1109/EUROMICRO.2007.25ISBN: 9780769529776 (print)OAI: oai:DiVA.org:mdh-4435DiVA, id: diva2:127325
Conference
33rd EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2007; Lubeck; Germany; 27 August 2007 through 31 August 2007
Projects
SOFARAvailable from: 2008-12-04 Created: 2008-12-04 Last updated: 2016-02-11Bibliographically 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 text

Authority records BETA

Pei Breivold, HongyuLarsson, Magnus

Search in DiVA

By author/editor
Pei Breivold, HongyuLarsson, Magnus
Computer Systems

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

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