Kuan Fan

Ranch Hand
+ Follow
since Jan 25, 2002
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 Kuan Fan

Thanks Yong,

Excellent explanation and great point ...

I was convinced the price itinerary is really necessary. For the component duagram, I will follow Cade's style to show teh dependencies only.

Hi Lakshmanan,

I decided to make a very simple price itinerary sequence diagram, just calculate price by number of seats multiply the coach or first class unit price and save the result somewhere.
I have also the same question for the preconditions, I think we have to make our own choice

Hi Yong,

You got a great score..

two questions for you, appreciate for your answer:
1. Do you think the price itinerary use case is necessary? because we can read the unit price for coach and first class when we search the flights in the prepare itinerary use case( also the prepare itinerary use case requires to display the price ), so we can calculate the price just by the number of seat multiple by the unit price. this is why I think the price itinerary use is useless. In my price itinerary sequence diagram, I only simply calculate the price and set to segment.
2. In your component diagram, did you use the lollipop, socket or port for the components. In my component diagram, I use only dependencies between components. I don't show the provide interface(lollipop), required interface(socket) at all.

hope I can get your answer, thank you very much
Good Point.

But the change itinerary use case will redirect to the prepare use case after the segment is deleted. The steps in prepare itinerary will be repeated.

I spent a lot of time to think about it, but still not clear now. Any other ideas?

I think the price itinerary use case is not necessary. The reason is that: we can get the coach price and first class price for a flight in the prepare itinerary use case( this use case require to display the price for the flight), then after the customer selects the seat, we can get the price for each segment( because one segment matched one flight) by simple calculation, such "coach price * number of seats"

I have no idea I'm correct or wrong. Hope somebody can help.


I�m working on the component diagram. Just wondering what type of style we should use:
1. the style from Mark Cade�s study case, only have components and dependencies
2. the style from this link(see figure 5 and figure 7): http://www-128.ibm.com/developerworks/rational/library/dec04/bell/

I�m using the Mark Cade�s style. I have no idea which one is better. If we choose to use the second on, maybe make the diagram complex and cluttering. What�s your opinions?


I'm working with the part II and trying to understand the use case descriptions.
How do you understand all transaction with the customer and the system must be secured with SSL in the prepare itinerary use case.
It seems to be strange for me. I think transaction doesn't need to be secured with SSL when the client just searches the flights information. In my opinion the transaction needs to be secured with SSL only when the client tries to pay by credit card.
Maybe I'm wrong. Postings will be appreciated.
Perfect explaination for Stereotype and Constraint
I'm also preparing SCEA. I'm working in Canada now. I'd like to make friends here.

Hi All,

I'm new to SCEA. I'm planning to take the Part II next month( Part I not finished yet :-) ).

Does anybody know where can download the source code for the book EJB Design Patters on http://www.theserverside.com/books/wiley/EJBDesignPatterns/
The source code download link was broken. I think that book should be helpful for the Part II.

Preciated for any help...

Source xml file:
<BBB ooo="555" ppp="666">
<DDD>d1 </DDD>
<DDD>d2 </DDD>
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" version = "1.0" >
<xsl utput method = "xml" indent = "yes" />
<xsl:template match = "/" >
<QQQ >
<xsl:copy-of select = "AAA/BBB" />
So far there is no problem. But if I add the namespace to the root element like below:
<AAA xmlns="http://mupc/xml/namespaces/geo" >
<BBB ooo="555" ppp="666">
<DDD>d1 </DDD>
<DDD>d2 </DDD>
The output file is only:
Anyone can help? Thanks.
Here, I want to thanks all of the people who ever helped me!
My score is:
General Considerations(maximum = 58): 55
Documentation(maximum = 20): 20
GUI(maximum = 24): 18
Server(maximum = 53): 49
I lost some points on GUI design. I paid a lot attention to the server design, but I ignored the GUI design.
Now I'm a sun certified developer and sun certified web component developer. I get these two certificates include programmer in 3 months.
I have 3-year java and 5-year unix experience. I immigrated to Vancouver Canada at the end of last year. The job market is not good. So I think the certificates should be helpful. I start my job-hunting now. Could anybody tell me which website is good for Java developers?
thanks a again!
I jared it on Windows 2000 and tested on win2000. I think i should test it on unix.
thanks Mark, you are always so nice!
Sun told me my jar file was corrupt.
I don't know what's wrong with me. I send a jar file using "jar -cvf d:\scjda-740175566.jar d:\FBN".
Grade: F
Score: 0
Comment: Your submission zip or jar archive file as we received it was corrupt. Please submit it again. You will not be charged for this. If you have any questions, please send email, with a copy of this comment, to who2contact@central.sun.com Don't worry if your grade appears to be "fail". That is just a database side effect.
Could anyone tell me what should i do?
I don't think that lock-1 need to lock every record one by one.
I design three database status: LOCKED NORMAL LOCKING.
Just assign the status to Database. when there are any records are being locked, the lock-1 must wait. IF the database status is LOCKED or LOCKING, all the records lock action should be rejected.
hope helpful