2008
DOI: 10.1016/j.cor.2007.01.011
|View full text |Cite
|
Sign up to set email alerts
|

An optimization framework for “build-or-buy” decisions in software architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
30
0

Year Published

2009
2009
2021
2021

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 74 publications
(32 citation statements)
references
References 21 publications
2
30
0
Order By: Relevance
“…They also state that each product variant has its specific considerations regarding appropriate requirements, risks and costs. Cortellessa et al, present a framework supporting the choice between selection of commercial component software and development in-house (Cortellessa et al, 2008). Daneshgar et al have examined, in relation to the 'make or buy' decision on the basis of 10 existing decision criteria, additional criteria that affect small and medium businesses (Daneshgar et al, 2013).…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…They also state that each product variant has its specific considerations regarding appropriate requirements, risks and costs. Cortellessa et al, present a framework supporting the choice between selection of commercial component software and development in-house (Cortellessa et al, 2008). Daneshgar et al have examined, in relation to the 'make or buy' decision on the basis of 10 existing decision criteria, additional criteria that affect small and medium businesses (Daneshgar et al, 2013).…”
Section: Related Workmentioning
confidence: 99%
“…Component-based software development is often used to deal with this challenge but the selection of appropriate software components then becomes an important decision (Jha et al, 2014). A component can be defined as a coherent package of software that can be independently developed and delivered as a unit, and that offers interfaces by which it can be connected, unchanged, with other components to compose a larger system (D 'Souza and Wills, 1997 Choosing between these options is not obvious (Cortellessa et al, 2008). However, we were unable to find a good overview of criteria that could be used for such a decision.…”
Section: Introductionmentioning
confidence: 99%
“…In the following discussion of make-or-buy literature, we focus on normative make-or-buy approaches for IT services (e.g., components, modules) or especially web services, as the sell option we consider in this paper is only relevant for IT/web services that are tradable on a market. For instance, Cortellessa et al [21] investigate whether a firm should buy commercial offthe-shelf components or develop them in-house. They incorporate costs as well as quality attributes in a non-linear cost-quality optimization model and also consider the architecture of the intended software system.…”
Section: Make-or-buy Decision-makingmentioning
confidence: 99%
“…The actual decision-making is often done using optimization approaches [7], [8], in particular when the trade-off is between two properties such as cost and reliability [9].…”
Section: Related Workmentioning
confidence: 99%
“…Assuming for the sake of the argument that the estimates problem is solved (which it most certainly is not), this means that each alternative software product -each option on the decision maker's table -can be characterized by an 8-dimensional vector. Also assuming that the properties can all be measured and mapped onto a scale of, say, 0-10, the problem becomes one of selecting between alternatives of the form A = (10, 10, 2, 10, 10, 5, 8, 1), B = (4,9,8,10,7,0,8,9), C = (7,8,7,4,7,2,7,0). This is a complex problem.…”
Section: Introductionmentioning
confidence: 99%