Modeling architectural dependencies to support software release planning

Robert L. Nord, Ipek Ozkaya, Nanette Brown, Raghvinder S. Sangwan

Research output: Chapter in Book/Report/Conference proceedingConference contribution

1 Scopus citations

Abstract

Organizations building products or systems that rely on software continue to demand increasingly rapid innovation and development processes that enable them to adjust products and systems to emerging needs. Release planning is a key activity in managing these processes. An essential aspect of release planning is balancing the development of new capabilities to address user needs against investment in system infrastructure and architecture to enable flexibility and maintainability. Providing quantifiable insight and visibility into both the delivered capabilities as well as the emerging quality of the software architecture is essential to product success. In this paper, we describe our use of dependency structure and domain mapping matrices to model architectural dependencies. These dependencies provide insight into the value of the capabilities being delivered over total effort to better guide the process of release planning.

Original languageEnglish (US)
Title of host publicationInvest on Visualization - Proceedings of the 13th International DSM Conference
Pages159-171
Number of pages13
StatePublished - 2011
Event13th International Dependency and Structure Modelling Conference, DSM'11 - Cambridge, MA, United States
Duration: Sep 14 2011Sep 15 2011

Publication series

NameInvest on Visualization - Proceedings of the 13th International DSM Conference

Other

Other13th International Dependency and Structure Modelling Conference, DSM'11
Country/TerritoryUnited States
CityCambridge, MA
Period9/14/119/15/11

All Science Journal Classification (ASJC) codes

  • Civil and Structural Engineering
  • Modeling and Simulation

Fingerprint

Dive into the research topics of 'Modeling architectural dependencies to support software release planning'. Together they form a unique fingerprint.

Cite this