Some tips and tricks from my experience and a few blogs that helped me through this journey.
I used StarUML 5.2, this version was not completely UML2. However, my assigment mentioned that my solution should be UML complaint. It did not specifically ask for UML 2, so I went ahead with StarUML 5.2 and since I passed, I don't think it harmed.
Class Diagram:
I had crammed in a lot of information in the assigment. Towards the end, my class diagram looked more like an information overload. I did not want to split it as I did not want to risk failure, so
I created 2 images .
In image 1 , I hid all the attributes and operations, left the dependencies and class level annotations intact. I removed most of teh comments too. I called it the overview diagram.
This diagram had a prominent note requesting the examiner to look at the Main Class diagram for operations and other details. That way I thought, the examiner can easily see classes and their relationships without getting bogged down by attribute and operation details.
In the main class diagram I crammed as much information as possible.
Deployment diagram:
I had two deployment diagrams.
The first one gave a high level view with firewalls, all clusters, datacenters etc.I showed all servers, and all nodes. This diagram did not give details of the ears/wars and jars.
The second one was called Type level deployment, it detailed how the jars, wars and ears were deployed. I only showed one AS node in the type level diagram, and put a note stating that. I showed external systems on both.
Assumptions:
I had made a lot of assumptions.
I did not want to aggravate the examiner by making her go through paragraphs of assumptions.
So I highlighted the important part of the assumption in bold, and then explained it in detail
in regular font. That way the examiner can get an idea by merely skimming through and then delve
into detail if she feels the need.
Risks:
I had in total 7 risks, I ordered them by degree of importance, thus the 3 major ones were first.
Going through Java ranch and reading experiences of others helped me refine my diagrams.
I started preparing for Part III while still working on my assignment. Trying to answer the list
of possible Part III questions helped me catch and correct some flaws or shortcomings in my design.
Blogs that helped me.
http://reddymails.blogspot.com/2011/07/well-assignment-i-got-was-designing-big.html
http://scea5-passingpart2and3.blogspot.com/
http://java.dzone.com/articles/my-path-scea-5
http://www.selikoff.net/2010/11/17/jeanne%E2%80%99s-sceaocmjca-5-part-23-experiences/
Hope this helps, have fun.
I used StarUML 5.2, this version was not completely UML2. However, my assigment mentioned that my solution should be UML complaint. It did not specifically ask for UML 2, so I went ahead with StarUML 5.2 and since I passed, I don't think it harmed.
Some Tips:
Class Diagram:
I had crammed in a lot of information in the assigment. Towards the end, my class diagram looked more like an information overload. I did not want to split it as I did not want to risk failure, so
I created 2 images .
In image 1 , I hid all the attributes and operations, left the dependencies and class level annotations intact. I removed most of teh comments too. I called it the overview diagram.
This diagram had a prominent note requesting the examiner to look at the Main Class diagram for operations and other details. That way I thought, the examiner can easily see classes and their relationships without getting bogged down by attribute and operation details.
In the main class diagram I crammed as much information as possible.
Deployment diagram:
I had two deployment diagrams.
The first one gave a high level view with firewalls, all clusters, datacenters etc.I showed all servers, and all nodes. This diagram did not give details of the ears/wars and jars.
The second one was called Type level deployment, it detailed how the jars, wars and ears were deployed. I only showed one AS node in the type level diagram, and put a note stating that. I showed external systems on both.
Assumptions:
I had made a lot of assumptions.
I did not want to aggravate the examiner by making her go through paragraphs of assumptions.
So I highlighted the important part of the assumption in bold, and then explained it in detail
in regular font. That way the examiner can get an idea by merely skimming through and then delve
into detail if she feels the need.
Risks:
I had in total 7 risks, I ordered them by degree of importance, thus the 3 major ones were first.
Going through Java ranch and reading experiences of others helped me refine my diagrams.
I started preparing for Part III while still working on my assignment. Trying to answer the list
of possible Part III questions helped me catch and correct some flaws or shortcomings in my design.
Blogs that helped me.
http://reddymails.blogspot.com/2011/07/well-assignment-i-got-was-designing-big.html
http://scea5-passingpart2and3.blogspot.com/
http://java.dzone.com/articles/my-path-scea-5
http://www.selikoff.net/2010/11/17/jeanne%E2%80%99s-sceaocmjca-5-part-23-experiences/
Hope this helps, have fun.
