Java Reference
In-Depth Information
tool to provide access to all team members and other
interested parties. The class diagrams are also shows
relationships among classes. This aspect of the diagrams may
tend to evolve later in the design process, as lower level
classes are identified. The class diagrams will improve the
definition of the classes, which in turn may require changes to
the sequence diagrams and, when developed, the state
transition diagrams. These other diagrams will also have an
impact on the class diagrams.
Component Diagram - Logical Architecture
The component diagram is another view of the system, at a
higher level than the class diagram. In this view, you are
expected to demonstrate the ability to visualize the system at
a higher level and understand all of the critical parts in your
solution. If you have proposed a MDBs to solve a particularly
integration issue, here is where you need to depict in the
diagram. The component diagram represents the high-level
parts that make up the modeled application. This diagram is a
high-level depiction of the components and the relationships.
A
component
diagram
depicts
the
components'
refined
post-development or construction phase.
Component diagrams are physical versions of class diagrams.
A component diagram shows the relationships and
dependencies between software components, including Java
source code components, Java class components, and Java
deployable components JAR (Java Archive) files. Within the
deployment diagram, a software component may be
represented as a component type. With respect to Java EE
some components exist at compile time, some exist at archive
time, some exist at runtime and some exist at more than one
