This page demonstrates how to combine constants and variables LePUS3 to specify application frameworks
Application frameworks cannot be modelled in UML, only specific implementations thereof. But a framework is NOT an implementation: It is specific combination between existing, pre-fabricated class library and user-defined classes which must collaborate according to specific rules. In LePUS3 the problem is solved using constants vs. variables: Constants, modelled as filled shapes, represent the pre-fabricated class library whereas variables, modelled as empty shapes, represent the user-defined elements of the framework. To verify the framework using the TTP Toolkit, simply assign (create a mapping) each variable to an element of your implementation.
Consider for example the following chart, modelling the following set of rules described in the documentation of Enterprise JavaBeans:
|Enterprise JavaBeans (legend)|
Enterprise JavaBeans is an application framework designed to support the rapid development of distributed enterprise applications. Monson-Haefel  describe some of the principles underlying the design of EJB applications as follows:
These statements are modelled in the chart above.