Sample specifications in LePUS3 and Class-Z:

Enterprise JavaBeans

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 [2001] describe some of the principles underlying the design of EJB applications as follows:

• Every bean [class] obtains an EJBContext object, which is a reference to the container [class]
• The home interface extends the ...javax.ejb.EJBHome interface
• A home [interface] may have many create() methods, … , each of which must have corresponding ejbCreate() and ejbPostCreate() methods in the bean class. The number and datatype of the arguments of each create() are left up to the bean developer, but the return type must be the remote interface datatype.
• When a create() method is invoked on the home interface, the container delegates the invocation to the corresponding ejbCreate() and ejbPostCreate() methods on the bean class.
• An implementation for the bean’s home interface (‘home implementation’) is generated by the container.
• Remote interfaces are subclassed from the javax.ejb.EJBObject interface. … For every remote interface there is an implementation class, a business object that actually implements the business methods defined in the remote interface. This is the bean class.

These statements are modelled in the chart above.