Assumption

1. Fig1: User entry table.

2. Fig2: Table Generated by the system.
Test case
Functionall requirements
Fig1: User entry table.
1. Test that none of the cells contains a zero value, i.e there wont be any prod
uct with zero value. if this is expected as part of offers then there should be
warning given in the user interface.
2. System should not allow user to enter negitive values. as there wont be a pro
duct with negitive value.
3. System should not accpets any character apart from positive decimal numbers.
4. If user leaves a cell blank the cell should get grayed out automatically.
5. Test that the system calculates the total of the columens correctly.
6. System should warn the user if Row or column titles is empty.
Fig2: Table Generated by the system.
1. Test that whole number values entered in fig1 is equalent to 1.5 times in fig
2, in corresponding cells (fig1 Vale Ex: 10, 15, 33) Equalent (fig 2 values Ex:1
5, 22.5,49.5)
2. Test that the single decmial value entered in fig1 is equalent to 1.5 times i
n fig 2, in corresponding cells (Vale Ex: 10.2, 15.3, 20.7) Equalent (fig 2 valu
es Ex:15.3, 22.95,31.05)
3. Test that the double decmial value entered in fig1 is equalent to 1.5 times i
n fig 2, in corresponding cells(Vale Ex: 10.25, 15.03, 20.99) Equalent (fig 2 va
lues Ex:15.37, 22.54,31.48)
4. Test that the shaded cells in fig1 is represented as shaded in corresponding
cells in fig2.
5. Test that the total value in fig2 is equalent to 1.5 times value in fig1 in t
he corresponding cell.
Usebility:
1. System should allow the user to add new columens and rows.
2. System should allow the user to delete selected columens and rows.
3. Conversin rate should be displayed to the user in a saperate field. costumar
may be interested in this value.
Non Funcitonal requrements
1. If user tries to delete a row or a colum, system should pupup a warning messa
ge to make sure this is not accidentel deletion.
2. System diagnostec check utility should be provided, so that user can report p
roblem with more useful informaiton to the developer.
3. Applicaiton should have a self recovery capabulity, when application crashes
or hangs.
4. All the data fields should be saved automatically when user closes the applic
ation.
Error COnditions
1. User friendly error message should be reported when user tries to enter negit
ive value in fig1.
2. User friendly error message should be reported when user tries to enter chara
cter value in fig1.
3. User friendly error message should be reported when user tries to enter zero
value in fig1.
4. If the netwrok is down, applicaiton should detect and report to user with us
er freiendly message.
int fig1[5][4] = {
{10, 12, 14, 45} , /* initializers for row indexed by 0 */
{20, 15, 24, } , /* initializers for row indexed by 1 */
{22, 60, , } ,
{28, , , } , /* initializers for row indexed by 2 */
{80,87,38 ,45 } ,
};
int fig2[5][4] = {
{15, 18, 21, 67.5 } , /* initializers for row indexed by 0 */
{30, 22.5,36, } , /* initializers for row indexed by 1 */
{33, 90, , } ,
{42, , , } , /* initializers for row indexed by 2 */
{120,130.5,57 ,67.5 }
};
for ( i = 0; i < 5; i++ )
{
for ( j = 0; j < 4; j++ )
{
if (fig1[i][j] != (fig2[i][j] * 1.5) )
{
printf("!Error the data dosent match.fig1[%d][%d] != fig2[%d][%d] ",
i,j,i,j);
}
}
}