Bina Sarmah

• Oct 13th, 2011

 

Since it's rarely possible to test every possible aspect of an application, evrisk analysis is appropriate to most software development project.

The checklist should include answers to the following questions:

1.Which functionality is most important to the project's intended purpose?
2.Which functionality is most visible to the user?
3.Which functionality has the largest safety impact?
4.Which functionality has the largest financial impact on users?
5.Which aspects of the application are most important to the customer?
6.Which aspects of the application can be tested early in the development cycle?
7.Which parts of the code are most complex and thus most subject to errors?
8.Which parts of the application were developed in rush or panic mode?
9.Which aspects of similar/related previous projects caused problems?
10.Which aspects of similar/related previous projects had large maintenance expenses?