Notes

CER1000
The application CER1000 is used to manually enter the estimated rate for the reduction of sales revenues for a rayon. Customer uses this application only when no historic data is available or when they create a new rayon.

At the first look, you see it’s only a simple application that allow customer to manage a list of data. It also has some common business rules like unique composite key, right format for the rate field. It supports lookup and filter. And a most of these features have been supported by the base. So, what did I do with this application and what challenge I when implement it.

First, let talk about what I have done for this application. I have followed the guideline to implement 3 layer for this application: create data model, map data model with database, create business object and implement some business rule, create the usercontrol and bind data to it, integrate usercontrol to a form and finally configure application to work as a plugin with the plugin application. Certainly, I have also created unit test while I am implementing. And the first challenge occurs with me. The database has a lot of dead data and it makes the unit test fail because it can’t pass the validation of business rules. With the support of Mr.Toan, I have found that because of the incorrect foreign key described in specs, the loaded data is not right.