Skip to Main Content
HBS Home
  • About
  • Academic Programs
  • Alumni
  • Faculty & Research
  • Baker Library
  • Giving
  • Harvard Business Review
  • Initiatives
  • News
  • Recruit
  • Map / Directions
Working Knowledge
Business Research for Business Leaders
  • Browse All Articles
  • Popular Articles
  • Cold Call Podcast
  • Managing the Future of Work Podcast
  • About Us
  • Book
  • Leadership
  • Marketing
  • Finance
  • Management
  • Entrepreneurship
  • All Topics...
  • Topics
    • COVID-19
    • Entrepreneurship
    • Finance
    • Gender
    • Globalization
    • Leadership
    • Management
    • Negotiation
    • Social Enterprise
    • Strategy
  • Sections
    • Book
    • Podcasts
    • HBS Case
    • In Practice
    • Lessons from the Classroom
    • Op-Ed
    • Research & Ideas
    • Research Event
    • Sharpening Your Skills
    • What Do You Think?
    • Working Paper Summaries
  • Browse All
    Evolution Analysis of Large-Scale Software Systems Using Design Structure Matrices and Design Rule Theory
    14 Jun 2007Working Paper Summaries

    Evolution Analysis of Large-Scale Software Systems Using Design Structure Matrices and Design Rule Theory

    by Matthew J. LaMantia, Yuanfang Cai, Alan D. MacCormack and John Rusnak
    Designers have long recognized the value of modularity. But because design principles are informal, successful application depends on the designers' intuition and experience. Intuition and experience, however, do not prevent a company such as Microsoft from constantly grappling with unanticipated challenges and delays in bringing software to market. Clearly, designers need a formal theory and models of modularity and software evolution that capture the essence of important but informal design principles and offer ways to describe, predict, and resolve issues. This paper evaluates the applicability of model and theory to real-world, large-scale software designs by studying the evolution of two complex software platforms through the lens of design structure matrices (DSMs) and the design rule theory advanced by Kim Clark and Carliss Baldwin. Key concepts include:
    • Important software modularity principles have remained informal.
    • DSM models reveal a key characteristic of modular architectures: The design rules must be explicitly defined so that otherwise dependent modules can be decoupled. Each independent module can then be replaced with a better version.
    • DSM modeling and the design rule theory of Clark and Baldwin have the potential to formally account for how design rules create options in the form of independent modules and how they enable independent substitution.
    • DSM modeling and design rule theory are general enough to model decisions other than those encoded in source code.
    LinkedIn
    Email

    Author Abstract

    Designers often seek modular architectures to better accommodate expected changes and to enable parallel development. However, we lack a formal theory and model of modularity and software evolution, which can be used for description, prediction, and prescription. According to Baldwin and Clark's theory, modular architectures add value to system designs by creating options to improve the system by substituting or experimenting on individual modules. In this paper, we evaluate their theory by looking at the design evolution of two software product platforms through the modeling lens of design structure matrices (DSMs) and design rule theory. Our analysis shows that DSM models and options theory can explain how real-world modularization activities in one case allowed for different rates of evolution in different software modules and in another case conferred distinct strategic advantages on a firm (by permitting substitution of an at-risk software module without substantial change to the rest of the system). The experiment supports our hypothesis that these formal models and theory can account for important aspects of software design evolution in large-scale systems.

    Paper Information

    • Full Working Paper Text
    • Working Paper Publication Date: April 2007
    • HBS Working Paper Number: 07-081
    • Faculty Unit(s): Technology and Operations Management
      Trending
        • 17 Mar 2022
        • Research & Ideas

        Navigating Tradeoffs: How Purpose Becomes a Company's ‘Lighthouse in the Storm’

        • 13 Jun 2022
        • Research & Ideas

        Extroverts, Your Colleagues Wish You Would Just Shut Up and Listen

        • 30 Jun 2022
        • HBS Case

        Peloton Changed the Exercise Game. Can the Company Push Through the Pain?

        • 25 Jan 2022
        • Research & Ideas

        More Proof That Money Can Buy Happiness (or a Life with Less Stress)

        • 18 Apr 2022
        • HBS Case

        Dick’s Sporting Goods Followed Its Conscience on Guns—and It Paid Off

    Alan D. MacCormack
    Alan D. MacCormack
    MBA Class of 1949 Adjunct Professor of Business Administration
    Contact
    Send an email
    → More Articles
    Find Related Articles
    • Infrastructure
    • Video Game
    • Web Services

    Sign up for our weekly newsletter

    Interested in improving your business? Learn about fresh research and ideas from Harvard Business School faculty.
    ǁ
    Campus Map
    Harvard Business School Working Knowledge
    Baker Library | Bloomberg Center
    Soldiers Field
    Boston, MA 02163
    Email: Editor-in-Chief
    →Map & Directions
    →More Contact Information
    • Make a Gift
    • Site Map
    • Jobs
    • Harvard University
    • Trademarks
    • Policies
    • Accessibility
    • Digital Accessibility
    Copyright © President & Fellows of Harvard College