- The modeling of the classes used in the
application needs to be seen in the same light as that of the
database. Without the correct control over what a class can and can
not do, how the class interacts with other classes, the development
soon gets out of control.
- To achieve a scalable structure that
will provide multiple deployment options over the customer base,
with the maximum reuse of code, requires a fairly complex package
and class structure, this would not be possible in the long term
without the capabilities of the high-end tool.
- In the design process visualization of
the structure is important in the development of a flexible
solution, without been able to see the complete and accurate
structure changes are prone to cause problems by closing avenues of
- The tool of choice is currently Rational
Rose. This allows for visual representation of the current
development process with the ability to generate the java skeleton
stubs for and classes and there methods. As Rational Rose is J2EE
aware the potentially complex interfaces for the EJB’s can be
modeled and generated from within the Rational Rose Environment
saving the developers of creating the interfaces manually.
- Often when generating code from a
modeling tool the original code is removed but with Rational Rose
the existing code is left unchanged.