Daniel --

Hope the meeting went ok yesterday. See comments below.

>Thanks dor the response.
>
>> However, if you do want to do some comparison between different types of
>> analysis documents, Software Requirements: Analysis and Specification by Alan > Davis, Prentice Hall, is a good resource.
>Does this book covers documenting a system after implementation? We discovered yesterday what we suspected all along: the vendor's core system used a code-as-you-go methodology and did not arise from a DDD. The vendor tried to fo the least amount of work to meet the RFP in order to get paid. Most of their represnsatives seemed shocked that we will not put their DDD on a shelf never to be read again.

Well, the whole idea of analysis is to guide design and development in whatever method of development style -- from waterfall to xTreme.

Certainly one loses the benefits of analysis guiding development when a DDD is done after the fact. It's like building a building and then doing the architectural drawings.

Their approach certainly doesn't seem an industry practice.

Davis' book is a good resource for defining the purpose and content of large analysis/design documents. It would help address issues like this upfront.

>
>> Not knowing anything further about the situation, I may be stepping out on a
>> limb. But, from your description, it sounds like the DDD should be an
>> internal document developed by the software vendor for the purposes of its
>> own customization.
>Yes. However, we would be sastified with an exact description of the functionality if we were not also purchasing the source code.

>
>> It is hard for me to imagine charging a potential client for that document
>> (if that did happen).
>THe RFP includes a large payment for this piece (the contract is worth several million dollars). Our goal was to encourage vendors to provide good documentation.

Didn't realize this was a custom/semi-custom project -- I thought it was a commercially developed app which you were considering purchasing.
>
>> I could consider an analysis charge for meeting business requirements,
>> but in many circumstances that either be included as part of the sales
>> process or determined on your own. A competitive process for acquring a
>> product can often put a potential vendor in the "proper state of mind."
>> Of course, that also will depend on what you want in a quote -- it's harder
>> to get a fixed price quote than time and materials that way.
>The vendor won bids from three different states. They bid twice their usual price in Virginia because of the additional customizations (25% more than any other state) and documenation. Therefore, we assumed that the remaining 75% prenium was the cost of producing the extra documentation and for $1.4 M, we assumed we would receive excellent documenation...

I think your relying on the RFP is the best bet, because the agreement on the analysis seems a bit fuzzy. For a custom/semi-custom project, the analysis should address the RFP that the state has provided. Instead, the company is trying to pass this off more like a commercial product which is modified. I don't think that cuts it.

>
>> In any case, if you feel you don't have enough information to proceed, I
>> suspect you don't.
>Thanks for the vote of confidence!
>
>Daniel


Jay