Help coderanch get a
new server
by contributing to the fundraiser

Tomas Cirip

+ Follow
since Mar 17, 2004
Merit badge: grant badges
For More
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Tomas Cirip

My solutions consisted of
1) main HTML document
2) one class diagram
3) 4 sequence diagrams - one for each use case
4) component diagram
5) deployment diagram

1) Contained my architectural choices, decisions, assumptions and verbal description of some of the diagrams
2) I had one class diagram with approximately 20 classes; technology independent
3) technology independent - using a lot of stereotypes - view, controller, entity etc. later on stated how views, controller are implemented for the java client and for web client
4) grouped components by tiers not by subsystems
5) provided deployment diagram even though it wasn't required - not a lot of work anyway

My major problem wasn't really solution and how to do it (technology wise). I have enough experience with J2EE and also think that my knowledge is on decent level. I had major problem in realizing how much details to provide in my solution and also the format. I was mostly concerned about component diagram as I can see now - there was a reason to be concerned. I am not sure if it was the content or the format of the component diagram that evaluator didn't like (that's where I lost all my 11 points).

I have to admit preparing for the certification made me think more about how other people can read my design and how to prepare it so it is easy for them to read it, especially when you don't know your audience.
Hi everybody,

I just passed part II/III and would like to share it with the community.

Class Diagram (44 maximum) .......................... 44
Component Diagram (44 maximum) ...................... 33 Sequence/Colloboration Diagrams (12 maximum) ........ 12

I would like to thanks all of you for very productive discussions. I found forum very usefull not just for the certification purposes. Thanks again and good luck to all those still working on SCEA.


Originally posted by Ramon Gill:
Some people have used notes in the class diagrams to say what are entity beans, session beans, etc.



What's the difference from using stereotypes or calling it XYZBean then? I think there should be no sign of J2EE technology at all? Anybody? What is your opinion/experience?
Hi all,

Is Class Diagram supposed to be technology independent? If yes then I just list Entities, SessionFacade classes etc. I don't specify what is Session EJB, what is Entity EJB etc. I can show J2EE components in Component Diagram. Correct?

Hi all,
let's say I have following domain model:
Deparment ------* Employee
I want to design Deparment as Entity EJB and Employee as Session EJB/DAO for some reason. How do I model it in the class diagram? I have two options:
<<entity EJB>> <<session bean>>
DeparmentBean EmployeeManagerBean
| |
| |
Department --------* Employee

<<session bean>>
<<entity EJB>> V
DepartmentBean ---------* Employee
My questions are:
A) what is the right way to model according to domain model and my design 1 or 2?
B) I don't understand one thing: If I show class Employee in the class diagrams like that, does that mean that there will be class called Employee in system? Does it matter if I use EmployeeVO in sequence diagrams? Do I have to call it EmployeeVO in the class diagram already?
C) If option 2 is the right one, how do I detect that DepartmentBean actually represents Department domain class? Let's say I want to keep good practice of calling EJB XxxBean. For simplicity I did not list all EJB classes. Is domain class just abstract business entity.
I was readin JSR 26 but it doesn't have answers to my questions. Thanks for the response.
Hopefully my textual UML diagrams show well if not, please copy message to notepad or wordpad with for example 'Courier New' font. Thanks
do I need to show alternative flow(s) in the sequence diagrams?
20 years ago
Thanks. I didn't think of this option. I'll let you know if I find something else. Can you enter stereotypes in newer versions of Rational Rose?
Does anybody know if it is possible to show stereotypes in Rational Rose 2002.05.00 in sequence diagram? If not what is other alternative to show what is JSP and what servlet in the same version of Rose? Thanks

Originally posted by Priya Patel:
I did not show *ANY* J2EE extension classes.

What do you mean by 'J2EE extension classes'? Mark Cade is shows Stateless Session beans in the class diagram, isn't that 'technology dependent'?
Hi all,
My sequence diagram is growing rapidly and I understand that it can be pretty difficult for marker to review. Is there a rule that there MUST be one sequence diagram for one use case? If not is there a way to horizontally split diagram? Can I simply create let's say 3 sequence diagrams for one use case and somehow indicate order? If yes, can somebody point me to example or explain how to do it? Thanks

Originally posted by Ajith Kallambella:
A domain model is normally technology agnostic. Technology here includes both implementation platform such as J2EE and analysis methodology such as OO.
After the business analysts finalize the domain model, you bring in the technology experts to decompose the model by applying a specific methodology. In case of a typical OO analysis phase you do things such as identifying generalization/specializations, separating processes from participants, defining contracts( interfaces ), identify conceptual divisions in order to define types and so on.
Once this is done, you apply platform specific(J2EE) principles and identify implementation details/constraints - things such as what gets modelled as entity beans( and why ), what can be just a POJO etc.

So to answer your original question( finally ), you should ensure that, during the steps detailed above, you do not contradict any relationships specified in the original domain model. This is an absolute must. Avoid diluting the clarity of any relationship and don't redefine the cardinality.

Thank you Ajith,
do you by any chance have some book or website that you would recommend on this topic? I just have a problem how much I can change and how much just to put into assumptions. I know assignment is simplified just enough to test our ability to build good systems. But still I want to build something that is close to real world system. Assignment is very good lesson for me. I don't have a problem with any part, I am very familiar with J2EE. I just have problem with BDM which I should start with first of all. After that, I think it is piece of cake. Thank you for your response.
I know that business domain model is not supposed to be changed. From what I am reading some of you have changed it. How do I know which change (changing multiplicity, adding new business entities/classes, merging them etc) are still ok and not in conflict with original model? Is there some good article or page where I can find what kind of changes are still acceptable and not breaking original domain model?
Hi all,
I have few questions about Part 2. I have problem with how many and which objects/components to list in the diagrams etc. I just don't want to overdo it but on the other side I want to provide enough information for the 'marker' to understand my design. I know that a lot of the questions were probably answered before. I would like to ask those of you that already passed Part 2 following questions:
1) How many classes did you include in the class diagram and how many class diagrams did you provide?
2) How many components did you list in the component diagram?
3) Did you have to split large sequence diagrams into two?
From what I've heard it is enough if class diagram contains just EJBs(if there are any), Value Objects, DAOs, ServiceLocator etc. Do I have to list also HTMLAction, FrontController and other WAF classes? I still want to include WAF in the sequence diagrams.
If somebody considers above questions going too far, I apologize. Thanks for all inputs.