The problems of designing large software systems were studied through interviewing personnel from 17 large projects. A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software… (More)
The capability maturity model (CMM), developed to present sets of recommended practices in a number of key process areas that have been shown to enhance software-development and maintenance capability, is discussed. The CMM was designed to help developers select process-improvement strategies by determining their current process maturity and identifying the… (More)
• Business process reengineering-the redesign of an organization's business processes to make them more efficient. • Coordination technology-an aid to managing dependencies among the agents within a business process, and provides automated support for the most routinized component processes. * Process-driven software development environments-an automated… (More)
ore than half the cost of the development of complex computer-based information systems (IS) is attributable to decisions made in the upstream portion of the software development process; namely, requirements specification and design . There is growing recognition that research on how teams actually go about making requirement deter-minations and design… (More)
The iedas and findigs in tiis document shouid not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. 'L-z , ay it-sademarks in this document is not intended in any way to infringe on the rights of the trademark holder.
Software development processes are usually modeled by manifestations of the software artifact at given stages in its evolution and the nature of the transformations being applied to it during these stages. Thus, the software process is purported to begin with a stage called something like requirements development, or in some cases with the even the earlier… (More)
The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and " No Warranty " statements are included… (More)
This article characterizes technical debt across 700 business applications, comprising 357 MLOC. These applications were analyzed against more than 1,200 rules of good architectural and coding practice. The authors present a formula with adjustable parameters for estimating the principal of technical debt from structural quality data.