Accession Number : ADA264668


Title :   Software is a Product...Not


Corporate Author : NAVAL COMMAND CONTROL AND OCEAN SURVEILLANCE CENTER RDT AND E DIV SAN DIEGO CA


Personal Author(s) : Shapiro, M D


Full Text : https://apps.dtic.mil/dtic/tr/fulltext/u2/a264668.pdf


Report Date : Sep 1992


Pagination or Media Count : 3


Abstract : Much of our planning for software uses the hardware product model. While we're not perfect, we do a fairly good job of managing hardware engineering for required time, quality, and money. But software more often than not is late, doesn't do what we want it to do, and costs too much. And that's a problem. We can't see a solution to our problem-perhaps because we have made the solution invisible by thinking about it in the wrong terms. I propose a vocabulary change. We will better understand the process if we consider software as a service, not a product. Let me expand on this statement. I do not believe we must do any of the software-building activities differently. Instead, from the perspective of scheduling, budgeting, and delivering software, we should use the service paradigm rather than the product paradigm. Scheduling, Budgeting


Descriptors :   *SOFTWARE ENGINEERING , *SYSTEMS APPROACH , *PLANNING PROGRAMMING BUDGETING , REPRINTS , JOBS , MODELS , PROBLEM SOLVING , TIME , MONEY , VOCABULARY , COSTS , QUALITY , ENGINEERING , SCHEDULING , PLANNING


Subject Categories : Computer Programming and Software


Distribution Statement : APPROVED FOR PUBLIC RELEASE