BETA TEST LICENSE

ISSUES CHECKLIST

The following is a checklist of issues to be considered in a Beta Test Software License and a Beta Testing relationship between a Developer and Customer.  The listing is not exhaustive but is intended to spot certain issues related to Beta projects.

I.                   GENERAL PURPOSE OF AGREEMENT

a.     A Beta Test Software Agreement is generally entered between a Developer and Customer who generally agrees to test and [Portions Omitted - included In fully Licensed Version]eloper to make corrections and further prepare the Software for release to the general market.

b.     Generally, the Customer will agree to accept more risk of errors in exchange for a reduced price.

c.     The Customer will generally agree to some process for communicating errors and problems with the Software to the Developer.

d.     These arrangements can provide significant benefits to Developers as they assist the Developer in perfecting its product prior to complete release of the product to the market.  This helps reduce longtime costs for product support and returns.

II.                NORMAL TOPICS COVERED IN AGREEMENT

a.     What Does the Developer Agree To Provide?

                                                             i.      [Portions Omitted - included In fully Licensed Version]

                                                          ii.      [Portions Omitted - included In fully Licensed Version]

                                                       iii.      [Portions Omitted - included In fully Licensed Version]

                                                        iv.      [Portions Omitted - included In fully Licensed Version]

                                                           v.      [Portions Omitted - included In fully Licensed Version]

                                                        vi.      [Portions Omitted - included In fully Licensed Version]

b.     What Does The Customer Agree To Provide?

                                                             i.      Information to the Developer

                                                          ii.      Certain designated testing time

                                                       iii.      Follow Beta testing procedures

                                                        iv.      Cooperation and assistance

c.     Beta Testing Plans and Procedures

                                                             i.      Developer defined [Portions Omitted - included In fully Licensed Version]

                                                          ii.      Assist developer in obtaining meaningful feedback

                                                       iii.      Timetables

                                                        iv.      Communication methodology

                                                           v.      Status conferences

                                                        vi.      Identify contact staff of both parties

                                                     vii.      Input forms

                                                  viii.      Method for correcting problems that may arising in testing process

                                                        ix.      Error identification and correction

                                                           x.      Record keeping requirements

d.     Customer Risk Acceptance

                                                             i.      Customer should acknowledge and agree to additional risk it is accepting

                                                          ii.      Hold harmless of Developer

                                                       iii.      State consideration for assumed risk – decrease in costs, additional hands on support, etc.

                                                        iv.      Include risk of loss for incidental and consequential damages, downtime, etc.

e.     Pricing

                                                             i.      What discount is given [Portions Omitted - included In fully Licensed Version]testing relationship

                                                          ii.      What items are discounted?

1.    License fee

2.    Support services

3.    Custom programming fees

4.    Training

                                                       iii.      What [Portions Omitted - included In fully Licensed Version] the period of discount?

1.    Perpetual

2.    Limited Term

                                                        iv.      How many copies, [Portions Omitted - included In fully Licensed Version] etc. are given the discount

                                                           v.      What pricing applies if customer defaults in its obligations?

f.      Customer endorsements and model center

                                                             i.      [Portions Omitted - included In fully Licensed Version]

                                                          ii.      Will customer serve as a model center for other potential customers?

                                                       iii.      Confidentiality in the event the testing goes badly or relationship sours?

                                                        iv.      What involvement will customer have in Developer’s marketing?

g.     Customer/Developer staffing

                                                             i.      [Portions Omitted - included In fully Licensed Version]

                                                          ii.      [Portions Omitted - included In fully Licensed Version]

                                                       iii.      [Portions Omitted - included In fully Licensed Version]