Gerald,

Thanks so much for your suggestions. You also raise some interesting questions related to framework functionality, which certainly has a function point value to it even if reused on multiple projects.

>I think that the difference is only in how your weight each of this points.
>If you remove the code from the buttons to put it in another place (BO or SP), you have to 'lighten' the button and add points for the BO. Or you can ignore the BO and let all the weight on the button, in the end you will 'win' more points if more than one button call the same BO method. You have to add point for the BO itself even if you dont add points for the methods of the BO.
>
>Views are not only implem. decisions, if not used, you have to do a select in a method or something else. So you have to add points for them too (EQ or table). The same thing for SP, they are EQ, they just dont sit in the app.
>
>BTW, do you have already some classes ready to use?
>Do you charge 'points' for these classes or a flat rate?
>If you use a framework, do you take points for each method and object in the framework?
>
>You have already a good start as you said.
>At this point, its more an 'art' then a method.
>Go with your feeling (and a good buffer) and it should be ok :)
>
>Just my 2 cents (CDN)