Java Reference
In-Depth Information
Tackling Business Problem
The analyst's team will come up with a brief introduction to
the customer background and the needs for a Java EE
application. They will include a structured description of the
main requirements, a domain model, use case diagrams and
NFRs and you are expected to deliver the solution for the
Java
application
using
the
Java
EE
technologies
and
framework.
The business problem captured or discussed during
workshops might be vague and may specify very high-level
description of the main use cases and thus there will be many
open questions or areas where further deep dive should be
planned. The requirements may be incomplete namely the use
case diagrams, and miss information necessary for the design.
Therefore you have to fill the missing parts for yourself and
replace the missing information with assumptions, perhaps
adding the unclear element to the list of risks. This is best
done through workshops, interview and discussion with
various stakeholders from business and technology
departments. Once the proper levels of details are available
and you have the solution in your mind, it isn't too difficult to
draw the views for the solution using a suitable Visual editor.
One can leverage tools like MS Visio for the diagrams as they
are very intuitive and more than solves the purpose.
The key part of the solution itself the various diagrams or the
views are the key outputs delivered by the architects. As an
architect you have to decide which components or interfaces
the system should have their integration into the eco-system
