Introduction
As a J2EE architect, you are required to organize various J2EE components into groups and determine how those components will interact. To a large extent, this is object-oriented analysis and design (OOAD) with an eye towards the technology that will be used to implement the components. All of this analysis is conducted within the context of various project goals and nonfunctional requirements as we identified in the previous chapters.
As an architect, you must control the coupling between components and packages, and whenever possible, capitalize on the use of component associations. This requires you to work with the project team and communicate architectural ideas clearly. This entails the use of visual modeling using object-oriented ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access