Java Reference
In-Depth Information
Summary
Remember a clear and easy-to-understand picture is worth a
thousand words. It is important to remember that the
diagrams/views provided represent one way of documenting
the java solution. As long as you follow the criteria outlined
in the earlier sections, feel free to provide your own UML
diagrams that showcase your unique solution to the assigned
business scenario. Specifically do the following:
• Emphasis should be on the business solution i.e. if your
class diagram is 80% frameworks and 20% business logic and
is a candidate for failure.
• Augment diagrams with English text, but ensure that your
diagrams hold water on their own. Make sure the views/
diagrams are legible.
• Common parts of an enterprise web application may not be
mentioned explicitly in the requirements like user
registration/login, administration. This should be addressed
by the solution.
• Engage with stakeholders and conduct workshop and
discussions if there is no clarity around certain aspects of the
requirements or what is expected to be delivered as part of the
solution.
• Make suitable assumption when required and document
these in the specifications so that that is available for all
parties.
