real time software always have high risk. You can anlyse risk on the bases of business requirment specification. If a minor change may cause of big problem and some time we wish to produce project having some bugs but in these type of project it is strictly not accepteble
Risk analysis is always done as a part of test plan activity. Where folowing points are taken in account like.. 1. which are thefuntionilities are more critical hitting directly customers stocks data etc.. 2. which are the functionilities has more complex coding. 3. which are the functionilities developed in tight schedule..Developer opnion counts here 4. which are the functionility has previously has more changing request and modification. 5.which are the functionility has more maintanence issues in past with same aplication. Maintanence people experience counts here.. 6. which are thefuntionility is seems to be more complex in terms of testers openion. 7.which are the area has no clear requirements. 8. test team experience alsocounts where such applications fails. 9. Entire project development and testing participate in risk analysis. so on... Based on such risk analysis judgement is taken
