Java Reference
In-Depth Information
the technology landscape and how these will be addressed by
your solution. Be strategic and objective in your assessment
of risk. Low-level risks should be avoided and high-level,
systemic risks that would be nightmare scenarios should be
included in this section. E.g In an online auctioning
application, a security limitation in any form would be a
major risk than worrying about if the application could run in
multiple browsers. The mitigation and hopefully complete
removal will be the focus of this section.
Class Diagram - from Domain Model to Class Diagrams
One has to ensure that all the objects detailed in the domain
model are present in the class diagram. Select and commit to
a method or framework that describes how you plan to build
the solution at the web/presentation, business logic,
persistence, and integration tiers. There are some important
points to note on the class diagram, as follows:
• The level of details in the class diagram will include the
entities, important manager EJBs and few other classes
representing important architectural concepts (a cache, an
interceptor, a DAO for accessing an external tool etc. which
needs to be addressed by the solution)
• The domain model will map to classes nearly directly, only
on a few occasions modifications and extensions will be
required e.g. introducing a base class.
• Annotations will be used to show how specific items in the
domain model are mapped onto JEE components specifically,
session beans and Entity classes. The class diagram will
