Search |
||
"Why the little fish eat the big fish". - MotivationPosted by malcolmdavis on May 5, 2004 at 6:36 AM PDT
With the right incentive, the unattainable can be attained Proper requirements generate proper results Under further investigation, it was determined that the problem with the military avionics revolved around the issue of requirements. The military requirements went into how the system should be constructed, by stating specific components in the design. On the other hand, commercial requirements focused on the consequences of failure. If equipment failed during flight, the vendors are required to reimburse airlines for any cost attributable to the failure. For instance, the additional fuel cost as a result of a missed landing opportunity. In both cases, it was the customer's requirement model that eventually determined the quality and cost of the product. Service for fee or ASP What happens if someone would to walk into a corporate IT and offer to do the project for free? Everything would be provided including hardware, software, and support. There would also be a guarantee of quality of service. Instead of a 'flat fee' or 'fee for service', the customer would pay based on usage. In the ASP model everybody wins; the customer pays less up front, the vendor receives a constant revenue stream. Since the ASP focus is on quality, cost and time to market, the manner in which software is developed is drastically different. This is why small commercial companies can run circles around large clunky IT shops. [Little fish eating the big fish]. Personal drive Final thoughts I want to thank Terry James for sharing his philosophy on the subject matter. I have spent many years in both the commercial and IT world; Terry helped me understand why the mindsets are so different. Thanks TJ. »
Comments
Comments are listed in date ascending order (oldest first)
|
||
|
|