|
Q: What are the steps in the Ready for IBM Rational software validation process?
A: The process is documented and accessible when you are a member of PartnerWorld. You download the requirements, identify your solution, apply for validation, and then proceed through the validation session.
Q: Do I have to change my solution to obtain Ready for IBM Rational software validation?
A: To pass the Ready for IBM Rational software requirements you may need to make modifications, but this is not the goal; well-designed software (for example, software developed according to the Eclipse guidelines) should pass the Ready for IBM Rational software requirements with no or only minor changes.
Q: Do I have to share my code with anyone as part of the Ready for IBM Rational software validation process?
A: There is never a need to share the source for your solution during or after the Ready for IBM Rational software validation process. You are required to demonstrate that your source does not use internal (non-API) interfaces to Eclipse, but this step does not require that you share your source.
Q: How much time and effort is required to obtain Ready for IBM Rational software validation?
A: The effort required can depend on the size and complexity of your solution, but it is not a fixed ratio. You have to assess and test your solution's compliance with respect to the requirements and then document your findings using a pretest report that is included in the validation package. Once the pretest report is complete, you have to participate in the Ready for IBM Rational software validation session. The process starts when your solution is ready (functionally complete). The elapsed time can range from two to four weeks; the work effort depends on your solution but should be on the order of a few days.
Q: How do I apply for Ready for IBM Rational software validation?
A: Simply follow the steps outlined in the Ready for IBM Rational software validation process; using the Global Solutions Directory you will create a listing for your solution and nominate it for validation. You will then submit your Ready for IBM Rational software validation pretest report. After receiving your completed pretest report and application we will contact you to schedule a validation session.
Q: Once I have submitted my pretest report for Ready for IBM Rational software validation, how long is it before the actual validation session is scheduled?
A: The scheduling process depends on the availability of both your team and our team. We make every effort to schedule the Ready for IBM Rational software validation session at the earliest possible time that is convenient for both teams. Scheduling an event within one week, assuming there are no problems with the pretest report, is the goal.
Q: Who participates in the Ready for IBM Rational software validation session?
A: The session includes as many members of your team as you desire; they may be technical representatives, management representatives, or both.
The Ready for IBM Rational software validation team representatives vary based on the type and complexity of the solution to be validated.
Q: What happens before and during the actual Ready for IBM Rational software validation session?
A: Prior to the validation session, we review the Ready for IBM Rational software pretest report for completeness and accuracy. We let you know if your pretest report is incomplete. Once your pretest report is complete, we will work with you to schedule your validation session. During the session, your team will introduce your software and perform solution-specific actions to demonstrate compliance with the Ready for IBM Rational software validation requirements. Typically you will start with your software installed and configured to support demonstration of its function. When you are extending an Eclipse-based IBM Rational Software Delivery Platform practitioner product you will perform an uninstall and reinstall as part of the validation process to demonstrate how you satisfied the installation requirements.
Q: How are the results of the Ready for IBM Rational software validation session documented?
A: The pretest report is used to document the validation session. It is annotated to indicate what has been tested and the status ("pass" for applicable requirements that you complied with, "open" for those where compliance was not adequately demonstrated and an issue remained and "OK" for those requirements that were "N/A"). Any unresolved requirements (marked "open") are noted and the actions required to resolve them are also documented. This revised pretest report is sent back to you at the end of the session. Usually, you can show resolution through screen captures. Occasionally, a short follow-up validation session may be required.
Q: How am I notified of the success (or failure) of my Ready for IBM Rational software validation?
A: The validation status of your application is usually known at the end of the validation session. Occasionally a follow-up validation session or other communication is required to resolve any open items before the process is complete. The program manager sends official notification of a successful validation by e-mail.
Q: After a successful validation, how do I obtain the Ready for IBM Rational software mark?
A: After you have successfully completed validation and your Authorized Profile Administrator has signed the required trademark license supplement, you may download the Ready for IBM Rational software mark.
Q: What changes would require that my solution undergo the full Ready for IBM Rational software validation process again?
A: Full revalidation is required for new versions of a solution, or new releases of the solution which contain significant changes to the Rational product integration.
Q: What is the Ready for IBM Rational software delta revalidation process and how does it differ from the full Ready for IBM Rational software validation?
A: The delta revalidation process is used when only minor changes to the solution have taken place; it entails the submission of appropriate pretest documentation and a review by the Ready for IBM Rational software validation team. In some cases it may be possible to avoid a formal Ready for IBM Rational software validation session.
Q: What changes would require that I submit my solution for an Ready for IBM Rational software delta revalidation?
A: A Ready for IBM Rational software delta validation may be used if revalidating a product to a new version of Ready for IBM Rational software if only minor changes have been made in the solution, primarily for compliance to the new Ready for IBM Rational software version. A Ready for IBM Rational software delta validation may also be used when revalidating minor changes in the solution to the same version of Ready for IBM Rational software.
Back to top
| 
