Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!csn!uswat!gbeary From: gbeary@uswat.uswest.com (Greg Beary) Newsgroups: comp.software-eng Subject: design to cost Message-ID: <15038@uswat.UUCP> Date: 5 Feb 91 14:44:26 GMT Sender: news@uswat.UUCP Organization: US WEST Advanced Technologies, CO, USA Lines: 36 In the January '91 issue of IEEE's Software magazine, Barry Boehm has an interesting article on Risk Management. He makes very brief mention of a technique called "design to cost". If anyone is familiar with additional information on this technique/process/lifecycle I'd appreciate it. We're having some difficulties in that we are trying to apply "normal software business" lifecycles to in-house development. What happens is that a internal client has the concept for a product. They "pitch" the idea to a funding board. The funding board allocates $x to use to build the product. We now begin to gather detailed requirements, estimate the effort- $y, and architect the product. In no case has $x >= $y. What your are left with is a client that never has the dollars for the functinality they want and a development organization that always "comes up short" in the eyes of the client. I believe this is due to applying a build-to-suit lifecycle to what essentially is a build-to-cost situation. It's rather like hiring a taxi driver in California, telling them you want to go to New York, and oh by the way... I only have $100 to give you for gas. The driver can either refuse your offer, drive you as far as $100 goes, or hope that when they have you in god-knows-where Nebraska - you'll "find" some more money to get yourself out of there. Does anyone have a description of a Lifecycle or process that addresses this type of situation? The Spiral model is lots closer to this approach than the normal waterfall, but not really a total fit. Thanks, Greg Beary -- Greg Beary | (303)889-7935 US West Advanced Technology | gbeary@uswest.com 6200 S. Quebec St. | Englewood, CO 80111 |