Person:

Maccormack, Alan

Loading...
Profile Picture

Email Address

AA Acceptance Date

Birth Date

Research Projects

Organizational Units

Job Title

Last Name

Maccormack

First Name

Alan

Name

Maccormack, Alan

Search Results

Now showing 1 - 2 of 2
  • Publication

    Exploring the Relationship between Architecture Coupling and Software Vulnerabilities: A Google Chrome Case

    (2017-03-21) Lagerström, Robert; Baldwin, Carliss; Maccormack, Alan; Sturtevant, Dan; Doolan, Lee

    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. Unfortunately, the effects of different types of coupling are somewhat hard to distinguish.

  • Publication

    Visualizing and Measuring Software Portfolio Architecture: A Power Utility Case

    (2015) Lagerström, Robert; Baldwin, Carliss; Maccormack, Alan

    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.