Models in OptimalJ
To develop an OptimalJ application, you use the following models (and submodels):
Domain model—captures functionality in platform-independent models. The domain model defines the business without any specific application detail and consists of:
Class model—specifies the system classes and is graphically represented using class diagrams.
Service model—captures behavioral information.
Application model—describes functionality in the following design models, which are independent of specific code, but are based on a certain technology or application framework, and therefore are PSMs. The application model consists of:
DBMS model—the persistency model
EJB model—the business logic model
Web model—the presentation model
In OptimalJ, the design models are generated from the domain model.
Integration model—provides interfaces to legacy and external applications.
Connector model—the integration model is subdivided into connector model packages in which you can import and define CICS/COBOL programs/copybooks, CORBA IDLs, and Web services WSDL. It can also be used to define a Web service provided by the application.
Code model—provides an implementation of the system described by the models. The code model contains the source code (Java language).