Project Time Line/Expected date for design completion |
We need to know what you expect so we can create the team appropriate to meet those expectations |
Go Live Date |
Not only do we need to know the Go Live date, but also how firm it is and what the criteria is for pushing the date out |
Demo Session |
A walkthrough of the prototype or mockups will help us familiarize ourselves with the application and ensure a greater understanding |
Business Requirements |
If these exist, they will be a primary means for us to understand the system and create appropriate test plans and test cases |
Functional Requirements |
If these exist, they will be a primary means for us to understand the system and create appropriate test plans and test cases |
Architecture Documents |
This kind of in-depth documentation can help us delve deeper into the system and test it more thoroughly |
Sample Test Documentation |
If you have a preferred format for the Test Plan and Test Cases, we need that template or access to the system you want us to use. |
Defect Report Format |
If you’d like defects reported in a specific manner, we need that format or template, or access to the system you want us to use |
Field Dictionary Document |
Detailed field declaration and validation at both the application level and the associated database fields. This information generally includes the character limit, character type validation, etc for each field in the application. |