Visualizing and Measuring Software Portfolio Architecture: A Power Utility Case

Robert  Lagerström; Carliss Y. Baldwin; Alan   MacCormack

Article | Journal of Modern Project Management

Visualizing and Measuring Software Portfolio Architecture: A Power Utility Case

by Robert Lagerström, Carliss Y. Baldwin and Alan MacCormack

Abstract

In this paper, we test a Design Structure Matrix (DSM) based method for visualizing and measuring software portfolio architectures. Our data is drawn from a power utility company, comprising 192 software applications with 614 dependencies between them. We show that the architecture of this system can be classified as a “core-periphery” system, meaning it contains a single large dominant cluster of interconnected components (the “Core”) representing 40% of the system. The system has a propagation cost of 44% and architecture flow through of 93%. This case and these findings add another piece of the puzzle suggesting that the method could be effective in uncovering the hidden structure in software portfolio architectures.

Keywords: Software; Infrastructure; Utilities Industry;

Format: Print

Purchase

Citation:

Lagerström, Robert, Carliss Y. Baldwin, and Alan MacCormack. "Visualizing and Measuring Software Portfolio Architecture: A Power Utility Case." Special Issue on DSM Conference 2014. Journal of Modern Project Management 3, no. 2 (September–December 2015): 114–121.

Other Article | Academy of Management Annual Meeting Proceedings | 2017

Designing an Agile Software Portfolio Architecture: The Impact of Coupling on Performance

Alan MacCormack and Robert Lagerstrom

The modern industrial corporation encompasses a myriad of different software applications, each of which must work in concert to deliver functionality to end-users. However, the increasingly complex and dynamic nature of competition in today’s product-markets dictates that this software portfolio be continually evolved and adapted, in order to meet new business challenges. This ability – to rapidly update, improve, remove, replace, and reimagine the software applications that underpin a firm’s competitive position – is at the heart of what has been called IT agility. Unfortunately, little work has examined the antecedents of IT agility, with respect to the choices a firm makes when designing its “Software Portfolio Architecture.”
We address this gap in the literature by exploring the relationship between software portfolio architecture and IT agility at the level of the individual applications in the architecture. In particular, we draw from modular systems theory to develop and test a series of hypotheses about how different types of coupling impact three specific dimensions of agility: the ability to update, remove and replace software applications in the firm’s portfolio. We test our hypotheses with data from a financial services firm, encompassing over 1,000 software applications and 3,000 dependencies between them. We capture data at two points in time, allowing us to identify changes in the software portfolio, and hence to develop robust measures of IT agility.

Keywords: Software; Design; Organizational Change and Adaptation; Performance Effectiveness;

Citation:

MacCormack, Alan, and Robert Lagerstrom. "Designing an Agile Software Portfolio Architecture: The Impact of Coupling on Performance." Academy of Management Annual Meeting Proceedings (2017). (doi:10.5465/AMBPP.2017.297, ISSN 2151-6561.) View Details

Cite View Details Find at Harvard Register to Read

Employing software metrics, such as size and complexity, for predicting defects has been given a lot of attention over the years and proven very useful. However, the few studies looking at software architecture and vulnerabilities are limited in scope and findings. We explore the relationship between software vulnerabilities and component metrics (like code churn and cyclomatic complexity), as well as architecture coupling metrics (direct, indirect, and cyclic coupling). Our case is based on the Google Chromium project, an open source project that has not been studied for this topic yet. Our findings show a strong relationship between vulnerabilities and both component level metrics and architecture coupling metrics. 68% of the files associated with a vulnerability are cyclically coupled, compared to 43% of the non-vulnerable files. Our best regression model is a combination of low commenting, high code churn, high direct fan-out within the main cyclic group, and high direct fan-in outside of the main cyclic group.

Faculty & Research

Visualizing and Measuring Software Portfolio Architecture: A Power Utility Case

Abstract

Citation:

About the Authors

More from these Authors