Problem

Within the context of J2EE, you would like to use EJB components to take advantage of the services offered by this technology, drawing on the accumulated experience of high level J2EE architects.

Process

• Analysis:
  - defining the business model's classes
  - retrieving existing CORBA components, reverse engineering existing applications in order to obtain a complete UML analysis
• Design:
  - determining those classes likely to be EJBs
  - annotating the analysis model using specific UML extensions (EjbEntity, EjbSession, ...)
  - defining particular properties (entity primary keys, database access modes, ...)
  - applying an automated design pattern used to deduce those elements which are useful and necessary to the EJB framework (interface, construction operations, ...)
• Coding and testing:
  - Automatic generation of Java code
  - adding and testing parts of the code specific to the business
• Deployment:
  - determining relevant configurations
  - optimising the application by using all the application server's properties

Benefits

• Learning good practises in a real context
• No "reinventing the wheel" , avoidance of common design errors
• A more rapid return on investment