Josep Andreas

Ranch Hand
+ Follow
since Jan 09, 2005
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 Josep Andreas

Originally posted by Karen Young:
Thank you, Josep. Did you show attributes and methods in the classes or were they just class names? Thank you.
I thought about this a lot. Initially I added attributes and methods to the classes. But I did not like the look of the diagram this way (all classes having different sizes..) and I did not feel it added any value to the diagram (as the methods are also displayed in the sequence diagram..)
So, In the end I removed them all. So my advise will be, only add methods if you feel it will add additional value to your diagram..

Originally posted by william smith:
congratz, you got a high score,
I would like to ask you

Thanks... still walking around with a smile..

1. do u have changed BDM ? I mean in segment and flight do u
put other class ?

No, I did not change the BDOM. There are a lot of posts in this forum about
the relation between flight and segment. Even when you do change the BDOM, you will be able to get a high score. For me changing the BDOM was not necessary.

pls. explain this issue .. how u resolved it?
2. When customer searches flights after query do u display the
search result as a segment +itinerary to customer.

I don't think I understand the question exactly. When a customer searches a flight, a Flight is displayed. I think you cannot show an itinerary because the customer has not selected a Flight(s) yet..?

3. how many component do u had ? did u show 1 component diagram ?

There are a number of ways to draw a component diagram. I followed the logic in Cade's guide:
I had about 25 components; I showed Facades, Session Beans, External subsystems. For entity beans with BMP you should display only the DAOs, For CMP you should show the entity beans. I also showed the components in the web-tier (simple design!) and components on the Travel Agent client.

It will also be usefull to look at the component diagram here:

[ April 08, 2005: Message edited by: Josep Andreas ]
Thanks for the congratulations..

The number of classes depend on the level of detail you want to show.
I kept the class diagram very high level and did not show classes in the webtier. Also I did not show any transfer objects. I think you should end up with 15-25 classes (I had about 20 classes).

Take a look at thw following URL:
I think that when you apply this template to your own design, you should be able to answer most questions. The questions are NOT related to PART I.

[ April 07, 2005: Message edited by: Josep Andreas ]
Yes, just saw my score on certmanager:

The maximum number of points you could have received is 100, minimum to pass is 70. Class Diagram (44 maximum) ............................... 42 Component Diagram (44 maximum) ........................... 42 Sequence/Colloboration Diagrams (12 maximum) ............. 11

I could not have done it without the help of the ranchers (especially deepak, Dhiren and Ajith (who let me explore the boundaries of this forum a bit)). thanks!!
[ April 06, 2005: Message edited by: Josep Andreas ]
It all depends on when you persist the itinerary.
You will have to make a choice whether you want to persist unpaid Itineraries or not.
In the requirements, you will not find a clear answer.
Make an assumption and stick with it.
[ February 28, 2005: Message edited by: Josep Andreas ]
I am using this URL as a template for my design:

It's a little bit too long, but I think the various paragraphs are OK and I think this will be more or less what SUN might expect of the document.

Yong How,
your right (of course).
Only for this project the most important requirement is "J2EE". Doesn't this mean that at least to some extend you shoul get your hands dirty?

Could you be more specific?
Oops.. Don't forget to include the diagrams
I want to upload the assignment by the end of the weekend.
So I am also busy with the documentation.

In the requirements they only ask a list with assumptions.
So i think If you submit anything more you should keep it
short and clear.

So i don't think a explanation is required where you evaluate all
options that are available with all cons and pros and
then come to your conclusion. I do think this would be too much.

I think a design decision might look like this:
copied from petstore:
SFSB is used because
1. Thread safety
2. Lifecycle management
3. Client type Neutral
4. Scalable

I will do the following:
0. A list with links to all paragraphs
1. A list with assumptions
2. I list with design decisions. (e.g explain why you used SFSB)
3. Scope
4. Add some appendixes (could be: 1 definitions used; 2. List with JSPs + function; 3. List with Classes+function; 4. Patterns uses; 5. something about each element in QoS requirements)

I think this will make the document easy to navigate.
probably the grader will be most interested in:
- assumptions
- design decisions
- Qos
- Patterns Used

what do you think?
Am I missing something important?
Under "Association stereotypes"
the <<local>> stereotype is used when a class A is a local variable within a method of a class B. shouldn't this be a dependency?
Any thoughts? IMO only the <<delegate>> is a true association.
[ February 22, 2005: Message edited by: Josep Andreas ]
When you take part three, do you have to type the questions in a textbox,
(or textarea)? Might be difficult to layout the answers (eg use bulleted list).
Or do you get to use MSWord?
[ February 21, 2005: Message edited by: Josep Andreas ]
I've letting this rest for a while. still not sure.
What if you just want to delete a segment, without selecting a new one.
Could happen. maybe you decided to take train back or stay there ( ).

I really do think that deleting a segment and changing the price should be done in one transction..
(in the end price itin UC IS included in Change Itin UC....)

I think, this is not something that you can leave for detailed design or implementation. this has to do with logical flow of app.

[ February 20, 2005: Message edited by: Josep Andreas ]
Sounds reasonable.
The frontend could be called Frontend or webtier or something alike.
You could label an arrow back to the user with the JSP name.

I really would like to show the functions of servicelocator
and signon filter.
(for some reason, use of servicelocator is really stressed in Cade's Guide,
it is displayed in both component and sequence diagram).

I think I do the same as with component diagram: Put one Object in that I call
JSP and then label the arrow to customer with JSP name.

(I think the diagram then will fit on 1 landscape printed page; I really hate those diagrams that do not fit on 1 printed page )
[ February 20, 2005: Message edited by: Josep Andreas ]
Thinking of using an intercepting filter.
Example of how it is included in sequence diagram:

I am using application Controller and intercepting filter (for authentication).
How is this displayed for post processing in sequence diagram?
1. Application Controller dispatches to Intercepting filter
2. Intercept Filter then dispatches to JSP? (or calls alt flow)
(seems a little bit odd have a Intercepting filter dispatch to a JSP)
I think the answer is here:

When the request is post-processed. (because user has to logon to view result)
Is the result JSP (which is restricted) generated (and cached) before the user is redirected to the logon page.
Or is the JSP generated after the user has logged on?

In other words, is the (post processing) filter applied, before or after
the JSP has been generated.
If this is the Case the JSP is cached by the the Intercepting Filter
Sounds logical, Is this correct?

[ February 19, 2005: Message edited by: Josep Andreas ]