This scenario is like a "Answer without question".
If you will not fix a target , what planning you do for
achieving it.
Following could be the results for mentioned problem
statement:
- It is very difficult to make a software without
requirements.
- For any product or software firstly the gathering of
rquirements is very important phase and it is also
important to gather requirements in only starting
phase.
- Gathering requirements from client is our prime moto, So making
or writing a software without requirements is not
appreciated and does not make any sense.
- Missing requirements are very unhealthy for any project
and for any organisation.
- In my view we can not make any software without writing
requirements.
- Making sofware without requirement may cause loss of
huge money, poor software quality and wastage of time and
efforts.
- It will be very confusing and ambigous for
those who will use that software , if requirements are not
clearly mentioned.
So for delivering a good software totally depends on gathering
of requirements and make a SRS(Software requirement
specification) document.