Evolving strategies for software architecture and reuse
(2007) In Software Process: Improvement and Practice 12(3). p.295-309- Abstract
- To achieve their business objectives, software developing companies employ different technical and managerial strategies concerning architecture and reuse. These strategies include component-based development, software platforms, product lines and highly configurable code bases. Frameworks for describing these strategies have recently emerged, presenting them in orders of increasing maturity, with researchers declaring specific architectural strategies to be more mature than others. Such frameworks can be useful in helping a company realize a particular architectural strategy but they do not provide guidelines concerning which architectural strategies are appropriate for companies in particular situations.
Different companies... (More) - To achieve their business objectives, software developing companies employ different technical and managerial strategies concerning architecture and reuse. These strategies include component-based development, software platforms, product lines and highly configurable code bases. Frameworks for describing these strategies have recently emerged, presenting them in orders of increasing maturity, with researchers declaring specific architectural strategies to be more mature than others. Such frameworks can be useful in helping a company realize a particular architectural strategy but they do not provide guidelines concerning which architectural strategies are appropriate for companies in particular situations.
Different companies have different needs - the business context and business goals of a company will determine which architectural strategy is most suitable for that company. There is no universally most mature strategy. In this article, we have studied architectural situations in thirteen companies in order to determine why and how these companies have moved between architectural strategies and how these relate to reuse and business goals and conditions. We present a framework for describing these and provide guidelines for companies about how to traverse the maze of architectural evolution. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/769401
- author
- Nedstam, Josef LU and Staples, M
- organization
- publishing date
- 2007
- type
- Contribution to journal
- publication status
- published
- subject
- keywords
- empirical software engineering, software architecture, architectural evolution, strategic reuse
- in
- Software Process: Improvement and Practice
- volume
- 12
- issue
- 3
- pages
- 295 - 309
- publisher
- John Wiley & Sons Inc.
- external identifiers
-
- scopus:34250747415
- ISSN
- 1077-4866
- DOI
- 10.1002/spip.327
- language
- English
- LU publication?
- yes
- id
- 984aa884-54ec-48f1-83ee-9d403f49781b (old id 769401)
- date added to LUP
- 2016-04-04 09:09:41
- date last changed
- 2022-01-29 08:33:38
@article{984aa884-54ec-48f1-83ee-9d403f49781b,
abstract = {{To achieve their business objectives, software developing companies employ different technical and managerial strategies concerning architecture and reuse. These strategies include component-based development, software platforms, product lines and highly configurable code bases. Frameworks for describing these strategies have recently emerged, presenting them in orders of increasing maturity, with researchers declaring specific architectural strategies to be more mature than others. Such frameworks can be useful in helping a company realize a particular architectural strategy but they do not provide guidelines concerning which architectural strategies are appropriate for companies in particular situations. <br/><br>
Different companies have different needs - the business context and business goals of a company will determine which architectural strategy is most suitable for that company. There is no universally most mature strategy. In this article, we have studied architectural situations in thirteen companies in order to determine why and how these companies have moved between architectural strategies and how these relate to reuse and business goals and conditions. We present a framework for describing these and provide guidelines for companies about how to traverse the maze of architectural evolution.}},
author = {{Nedstam, Josef and Staples, M}},
issn = {{1077-4866}},
keywords = {{empirical software engineering; software architecture; architectural evolution; strategic reuse}},
language = {{eng}},
number = {{3}},
pages = {{295--309}},
publisher = {{John Wiley & Sons Inc.}},
series = {{Software Process: Improvement and Practice}},
title = {{Evolving strategies for software architecture and reuse}},
url = {{http://dx.doi.org/10.1002/spip.327}},
doi = {{10.1002/spip.327}},
volume = {{12}},
year = {{2007}},
}