Re: Application Development

}>>>>>>>>> Perry's response to Malcolm Weallans <<<<<<<<<< My $0.02 on this is to provide the detailed schema docs at a cost and with a disclaimer as to modifications and how they affect the baseline software. We currently don't do this, primarily because our services organization does most of the custom modifications required at client sites. If it was up to me, I would have our entire schema in a CASE Tool like System Architect, and then charge the client a fee to distribute the data dictionary. After all, it is a tremendous value-add to have your entire schema well documented so that someone can easily integrate other packages, or extend the current one without sucking up time from the development staff to explain the schema and table relationships. } From: onlinedbc@cix.compulink.co.uk ("Malcolm Weallans") } Subject: Re: Application Development } Date: Mon, 18 Mar 1996 21:31:44 GMT } To: informix-list@rmy.emory.edu } } This message is extremely relevant to an issue I am involved in } at this time. } } > Hello } > } > } > My company is planning to contract the development of a major } > application. I would appreciate receiving e-mail from software } > contractors with regards to the following issues concerning custom } > applications: } > } > 1. What is a reasonable warrenty period for the delivered } > application? } > } > 2. If major bugs are encountered after the warrenty period, who } > typically pays? The contractor or client? } > } > 3. What is a good method for "signing off" the completion of the } > package. What are the major points of agreement and } > obligations the vendor and the client must agree to? } > } > 4. What percentage of the total package cost is a reasonable price } > to pay for extended warranty? } > } > 5. What other critical points if any should we be examining? } > } > 6. Are there any good references on this subject? } > } > Thanks } > } > Jim Collier } > Winnipeg, Manitoba } > Canada } > } > } My major piece of advice is that the client should ensure that } the developer provide them with a well-documented schema of the } database. Recently I have been training personnel from VARs, } consultants, and clients. They all have a different } interpretation of what database documentation the developer } should provide. The developers do not want to provide any } database documentation as they say that it would encourage the } client to alter data through SQL, abd the clients want the } documentation as they want to write their own queries and } reports. } } I would like to see this issue discussed more fully through } this group so that we can arrive at a documented standard } provision. } } Malcolm Weallans } Online Database Consultancy } Phone 01628-72154 } Fax 01628-37463 } CIX - onlinedbc } -perryd (Guru) ==================================================================== = Perry Dillard - Chief Architect Direct Dial: (206)517-6430 = = FourGen Software, Inc. FAX: (206)522-0054 = = FourGen Building Tech. Support: (800)444-3398 = = 115 NE 100th Street Sales: (800)333-4436 = = Seattle, W.A. 98125-8098 = = = = e-mail: perryd@fourgen.com Web Site http://www.fourgen.com = = = = Home Page: http://www.geocities.com/SiliconValley/3198 = ====================================================================