The Java (EE) Enterprise Architect Certified Master Assignment requires to complete design solution for the given business problem.
Tip #1: Understand Project Requirements
Read the assignment very well and fully understand the scope of the problem to solve. Note non-functional requirements given in the business problem to choose best architecture solution.
Tip #2: Download good UML tool for your design
Choose UML tool that provides support for UML 2.0 and that allows you to export the diagrams as images easily.
Tip #3: Class diagram
Start building your class diagram based on the business domain model given in the assignment file. Do not modify the proposed domain model because doing so would alter the scope of the requirements.
You must consider adding classes for representing the presentation tier components, like JSP or JSF pages. Include utility packages and classes useful for your solution, like cache or logging.
Use stereotypes for clarifying the purpose and nature of the proposed classes. Example: ‘JSF Page’, ‘ManagedBean’, ‘Interface’, ‘JPA’, etc.
Tip #4: Sequence diagram
The sequence diagrams must add some classes to represent important Java EE framework classes, like the Entity Manager. Remember that the class diagram must contain all the classes included in the sequence diagrams. If you have carefully completed the class diagram, making sequence diagrams should be a simple and enjoyable work.
Refer these links for Sequence diagrams:
http://www.agilemodeling.com/artifacts/sequenceDiagram.htm
http://www.ibm.com/developerworks/rational/library/3101.html
Tip #5. Component diagram
The component diagram must arrange components by tiers, so that it is clear the components that belong to each application tier. Also remember that components should expose well defined interfaces, so use and include them into the diagram.
Also you can group component in subsystems in such a way components related to the same functional purpose are logically grouped.
Refer these links for component diagrams:
http://agilemodeling.com/artifacts/componentDiagram.htm
http://www.agilemodeling.com/style/componentDiagram.htm
http://www.uml-diagrams.org/component-diagrams.html
Tip #6. Deployment diagram
The deployment diagram should show the detail of hardware and software of your system, and the application components that run on those nodes. Before start building this diagram, you should think about your assignment restrictions like time and cost and about your assignmentNon-functional requirements like reliability, availability, scalability, security, performance; and considering all these aspects, propose a scheme that allows satisfying them in the best way.
Refer these links for Deployment diagrams:
http://www.agilemodeling.com/artifacts/deploymentDiagram.htm
http://aviadezra.blogspot.com/2009/09/uml-deployment-component-diagrams.html
http://www.uml-diagrams.org/deployment-diagrams-overview.html
http://www.uml-diagrams.org/deployment-diagrams-examples.html
Tip #7. Assumptions and decisions:
The assignment may be slightly vague and one need to make a lot of assumptions and that might affect your design decisions. Documenting your assumptions and decisions as you progress in solving the case. You can include justifying the choice of each of the framework, APIs, technologies and products you have used. Also in the architectural decisions you can justify why or why not use some kind of Java EE framework component, so that it is easier for the evaluator to understand the proposed design and architecture.
Tip #8. OCMJEA Master Essay Exam
Do not take much time after sending the assignment to present the essay. This exam will be very easy if you completed your assignment by your own.
Tip #9: General Tips
Before working on UML tools, finalise the architecture with papers. This saves lots of re-work on your UML diagrams. Analyse different design options for each layer’s client Tier, Business Tier and Data Tier.
Tip #10: Documentation Tips
Document details about following items and it it will be very useful for essay exam as well:
- Security management
- Transaction Management
- Session Management
- Communication to external Systems
- Info about how your architecture supports non-functional requirements.
