21
SOFTWARE BETA TESTING NINE KEY CONSIDERATIONS Prepared By: Ony Okoro

Software Beta Testing

Embed Size (px)

Citation preview

Page 1: Software Beta Testing

SOFTWARE BETA TESTING

NINE KEY CONSIDERATIONS

Prepared By: Ony Okoro

Page 2: Software Beta Testing

A beta test is the final stage of testing a software prototype before it is ready for launch.

WHAT IS A BETA TEST?

Page 3: Software Beta Testing

CONSIDERATION #1:WHAT ARE THE RISKS TO CONDUCTING A BETA TEST?

Page 4: Software Beta Testing

Disclosure of your trade secrets.

Third party rights to your prototype.

Damage to a third party as a result of the beta test.

MANAGE YOUR COMPANY’S RISK AND PROTECT YOUR COMPANY’S INTELLECTUAL

Page 5: Software Beta Testing

CONSIDERATION #2: WHO OWNS YOUR PROTOTYPE?

Page 6: Software Beta Testing

Will evaluators have rights to improvements?

Who will own the data resulting from the evaluation?

How can you prevent evaluators from reverse engineering or modifying your prototype?

PROTECT YOUR COMPANY’S INTELLECTUAL PROPERTY CONTRACTUALLY

Page 7: Software Beta Testing

CONSIDERATION #3:WHAT IS THE SCOPE OF THE EVALUATION?

Page 8: Software Beta Testing

What constitutes proper use of the prototype?

Will the evaluator have rights to use the prototype for commercial purposes?

LIMITING THE SCOPE OF THE EVALUATION MAY OFFER GREATER PROTECTION FOR YOUR COMPANY

Page 9: Software Beta Testing

CONSIDERATION #4:WHO SHOULD EVALUATE YOUR PROTOTYPE?

Page 10: Software Beta Testing

What role should evaluators have in the market?◦ Direct Customers◦ Indirect Customers ◦ Competitors◦ Academics

EVALUATORS SHOULD BE DIVERSE CONSIDER AVOIDING COMPETITORS

Page 11: Software Beta Testing

CONSIDERATION #5:WHAT CONFIDENTIALITY OBLIGATIONS SHOULD EVALUATORS HAVE?

Page 12: Software Beta Testing

How long will confidentiality obligations last?

Under what circumstances will confidentiality obligations no longer apply?

How limited should access to the prototype be?

STRONG CONFIDENTIALITY AGREEMENTS OFFER GREATER PROTECTION FOR YOUR COMPANY’S TRADE SECRETS

Page 13: Software Beta Testing

CONSIDERATION #6:WHO SHOULD HAVE ACCESS TO THE PROTOTYPE?

Page 14: Software Beta Testing

Will the evaluation take place at a single site or at multiple sites?

Will affiliates of the evaluator have access to the prototype?

Will consultants/contractors/agents have access to the prototype?

LIMITED ACCESS TO THE PROTOTYPE OFFERS GREATER PROTECTION FOR YOUR COMPANY’S

TRADE SECRETS

Page 15: Software Beta Testing

CONSIDERATION #7:WHAT CAN EVALUATORS SAY ABOUT YOUR PROTOTYPE?

Page 16: Software Beta Testing

Will evaluators have any rights to include data in publications? ◦ If so, what type of data can be included?◦ How will the publications be reviewed?

Will evaluators have any rights to mention their involvement in the beta test?

Will evaluators have any rights to publicly comment about the prototype?

BALANCE BETWEEN THE INTERNAL NEEDS OF THE EVALUATOR AND

YOUR COMPANY’S COMMERCIAL NEEDS IS IMPORTANT

Page 17: Software Beta Testing

CONSIDERATION #8:WHO IS RESPONSIBLE FOR BUGS AND ERRORS ?

Page 18: Software Beta Testing

Will the prototype be provided “AS IS”?

Is it appropriate to limit your company’s liability? ◦ If so, what is the scope of the limitation?

LIMITED LIABILITY ENABLES YOUR COMPANY TO MANAGE RISK AND OFFERS GREATER PROTECTION FOR YOUR

COMPANY

Page 19: Software Beta Testing

CONSIDERATION #9:WHAT HAPPENS WHEN THINGS GO WRONG?

Page 20: Software Beta Testing

Will the evaluator have any obligation to protect your company from their use of the prototype?

Will you be able to act quickly if your trade secrets are disclosed?

How will disputes be handled? ◦ Negotiation/Mediation/Arbitration/Litigation

Who should bear the costs of breaches, errors and mistakes?

CONSIDER AVOIDING RISK FOR ACTIVITIES OVER WHICH YOUR COMPANY HAS NO AUTHORITY OR CONTROL

Page 21: Software Beta Testing

For more information contact: Ony Okoro at [email protected]

FOR MORE INFORMATION: