The other aspect is the feasibility. You must look to the functional and performance requirements, that means: the feasibility when we defind certain functional specifications, are they feasible? Now, at a definition stage, is fine, but when we are implementing at a later stage, we will see that it is not feasible. I think this is what we are to, when we are talking of needs analyses, or the requirements analyses, we should be able to check up here itself. The other is performance requirements. The sort of the performance that you are expecting from the system. Can we really get it? With a given hardware and software with the user environment can we have that. This is what is to be assessed, so that our system will be conforming to the specifications at a later stage. Then also it is very important to look at the user responsibilities. The user responsibilities, maintainability and reliability. Let us try to look at what happens in a practical situation. We believe that we can get certain data from the user systems and we try to provide this. If a lot of effort is required to collect the data and put the data probably the data will not be the data that comes into. The third aspect is manpower availability. The quality of the manpower that is available to do a certain job. And finally of course the feasibility is sort of relating to the cost of the need.

---