Hypothesis for an engineering project that can't be tested due to time constraints Question: How can I formulate a hypothesis for an engineering project that I help to develop but probably won't have time to test?

Explanation: The project is to develop a system that will train clinicians to write a certain kind of research data. This type of data will be posted into a community where clinicians can discuss and collaborate on it. I am working on this project and it will be the basis for my master thesis. The value of this project for the company is to generate more of the research data and to thus to create a community that actively discusses its products. Thus, my hypothesis could be something like: The new system will help to generate more research data and support discussion about the company's products. However, I can't test this hypothesis because the marketing and acceptance of the system will take too long. Thus, probably when the hypothesis would be testable (i.e. the first people are using it) I must have already delivered my thesis. I can't think of a hypothesis that only includes the setup of such a system. 

Can anyone think of something or give me some hints on how I can come up with a hypothesis or handle this situation?
For your specific case:

You could create a basic version of the system in a short time and conduct a study with a small number of clinicians. Have one group of them use it, and one group not use it. Define metrics that capture user variables (ease of use, tangible benefits) and system variables (how much different features are used, how much it adds to any existing discussion on products etc.). Make small changes in the system to change these variables, and map the outputs. By doing this, you already have an alpha-test, which will help you pitch the system when it is actually developed.

For the general case:

Often it is not possible to test the actual system/design/product in a limited time-frame. A good solution is to identify different parts of the system/design/product, compare these with existing systems and isolate parts that are unique and/or critical improvements. Develop just these parts, and test them either physically or through some kind of simulation. If it is a simulation, do some validation testing to increase confidence. Document everything, and generate sensible statistics during testing. Honestly report all the positive outcomes, the flaws and methods to tackle the flaws.