Software development under bounded rationality and opportunism

Erbas, Cengiz; Erbas, Bahar Çelikkol

doi:10.1109/sdg.2009.5071331

Cited by 7 publications

(13 citation statements)

References 7 publications

(9 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Coordination and administrative loads of bottom-up construction place it at a disadvantage at k=0, but the cost differences between D(k) and C(k) narrow as asset specificity rises and reverse as the need for cooperative adaptation exceeds a threshold k>k2. Topdown decomposition can be viewed as hybrid mode of development, as incentive intensity and administrative control take on intermediate values (Erbas and Erbas, 2009). The proposed approach may serve as a foundation for a unified theory in software engineering.…”

Section: Software Development Methodsmentioning

confidence: 99%

See 1 more Smart Citation

On a theory of software engineering a proposal based on transaction cost economics

Erbas

2013

2013 2nd SEMAT Workshop on a General Theory of Software Engineering (GTSE)

Self Cite

View full text Add to dashboard Cite

This article leverages the findings of the transaction cost economics field, and proposes a simple theory and associated vocabulary to serve as a foundation for a unified theory of software engineering. It characterizes software engineering as a set of transactions organized under three governance structures. The theory explains the strengths and weaknesses of these governance structures in relation to asset specificity. It takes into account the recursive nature of the notions in software engineering, and applies uniformly to various contexts at different levels of granularity. The theory not only provides an explanatory framework for some of the propositions given in the software engineering literature, but also reveals the boundaries of their applicability.

show abstract

Section: Software Development Methodsmentioning

confidence: 99%

“…Components are implemented one at a time and the system is re-factored when required. This approach expects the parties to be open to cooperative adaptation; but it is unable to control costs as well as the top-down governance structure (Erbas and Erbas, 2009). …”

Section: Governance Structures In Software Engineeringmentioning

confidence: 99%

On a theory of software engineering a proposal based on transaction cost economics

Erbas

2013

2013 2nd SEMAT Workshop on a General Theory of Software Engineering (GTSE)

Self Cite

View full text Add to dashboard Cite

show abstract

“…Our approach, in this paper, relies on leveraging transaction-cost economics (TCE) to identify building blocks for a theory of software engineering [11][12][13]. TCE studies the organization of business transactions between a supplier and a client.…”

Section: Related Workmentioning

confidence: 99%

Modules and transactions: Building blocks for a theory of software engineering

Erbas

2015

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

This article leverages the findings of the transaction cost economics field, and proposes a simple theory and associated vocabulary to serve as a foundation for a unified theory of software engineering. The theory characterizes software engineering as a set of transactions organized under a spectrum of three governance structures (top-down, bottom-up and reuse), and explains the strengths and weaknesses of these governance structures in relation to asset specificity and uncertainty. It takes into account the recursive nature of the notions in software engineering, and applies uniformly to various contexts at different levels of granularity. It sheds light both on the technical and on the human aspects of software engineering through a unified explanatory framework, without requiring a need to assemble different approaches to address each. The theory not only explains some of the propositions given in the software engineering literature but also reveals the boundaries of their applicability.

show abstract

“…Several approaches for software development governance were suggested, e.g. based on incremental commitment model [7], using decision rights automation [8], linking long-term business with release planning [9], and using the transaction cost approach [17]. Quite a few articles explore software development governance in agile development [9,10,11,12,13,14], yet they do not focus on large-scale hardware-dependent contexts.…”

Section: Background and Related Workmentioning

confidence: 99%

Evaluating the Governance Model of Hardware-Dependent Software Ecosystems – A Case Study of the Axis Ecosystem

Wnuk

Manikas

Runeson

et al. 2014

Software Business. Towards Continuous Value Delivery

View full text Add to dashboard Cite

Ecosystem governance becomes gradually more relevant for a set of companies or actors characterized by symbiotic relations evolved on the top of a technological platform, i.e. a software ecosystem. In this study, we focus on the governance of a hardware-dependent software ecosystem. More specifically, we evaluate the governance model applied by Axis, a network video and surveillance camera producer, that is the platform owner and orchestrator of the Application Development Partner (ADP) software ecosystem. We conduct an exploratory case study collecting data from observations and interviews and apply the governance model for prevention and improvement of the software ecosystem health proposed by Jansen and Cusumano. Our results reveal that although the governance actions do not address the majority of their governance model, the ADP ecosystem is considered a growing ecosystem providing opportunities for its actors. This can be explained by the fact that Axis, as the orchestrator and the platform owner, does not address the productivity and robustness of the ecosystem adequately, but has a network of vendors and resellers to support it and some of the governance activities (e.g. communication) are achieved by non-formal means. The current governance model does not take into consideration.

show abstract

Software development under bounded rationality and opportunism

Cited by 7 publications

References 7 publications

On a theory of software engineering a proposal based on transaction cost economics

On a theory of software engineering a proposal based on transaction cost economics

Modules and transactions: Building blocks for a theory of software engineering

Evaluating the Governance Model of Hardware-Dependent Software Ecosystems – A Case Study of the Axis Ecosystem

Contact Info

Product

Resources

About