I am putting together a support agreement with another software company. I
am going to maintain their application for their customers (I have been
doing work on the application as a contractor). There are no written
specifications for the application so I figured the source code could be the
specification. If there are any requests for reports or forms not included
in the source code, they would be considered enhancements and not be
included in the maintenance agreement.
Here is the language I used in the agreement:
"""Absence of Written Specifications
Often times work is performed where there is no documentation or written
specifications and authorizations to do the work are verbal. In the event
there is no written specification both parties will agree upon a release
version of the application as a benchmark of features and functionality.
The source code of the agreed upon version will be considered the written
specification for the project. All reports, forms and processes included in
the application's source code will be included in the scope of this
Agreement and be considered "agreed upon" by both parties."""
Any ideas on this approach?
By the way, I use Whil's "The Software Developer's Guide" when putting
together agreements, but he doesn't cover what happens when you enter into
an agreement where there are no written specs.
Jeff
Jeff Johnson
[EMAIL PROTECTED]
623-582-0323
Fax 623-869-0675
--- StripMime Report -- processed MIME parts ---
multipart/signed
multipart/alternative
text/plain (text body -- kept)
text/html
application/x-pkcs7-signature
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
