Guaranteed Development: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
<blockquote> | <blockquote> | ||
There are two aspects to what I have traditionally called the Commodity Software policy. One is a warrant for correction of defects at no additional cost in perpetuity and is the original simple sense which is still operative once your application goes into maintenance. | There are two aspects to what I have traditionally called the Commodity Software policy. One is a warrant for correction of defects at no additional cost in perpetuity and is the original simple sense which is still operative once your application goes into maintenance. | ||
Prior to that:<br><br> | Prior to that:<br><br> | ||
<ul> | <ul> | ||
Revision as of 01:45, 13 April 2007
DRAFT
"What do you mean by 'Guaranteed Development'?"
There are two aspects to what I have traditionally called the Commodity Software policy. One is a warrant for correction of defects at no additional cost in perpetuity and is the original simple sense which is still operative once your application goes into maintenance. Prior to that:
- When I identify a specific vertical market opportunity, I prepare an app using the most likely selection from the Common Platform Bases. In doing so independently I have advanced labor at no cost to the class of agents who would operate in that real world vertical market. ...
- When a generic application is so purchased, it diverges from the common public abstract application upon which it is based. ...
- In this way we eliminate, or reduce to it's practical minimum, your risks in application development, the bugaboo of automation.
