Andy Chow

+ Follow
since Nov 20, 2003
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 Andy Chow

I used the book with ISBN: 0130449164.
That got me through part 1 and they have an example solution for part 2.
I will say if you have worked with J2EE before using this one is good enough. Only ~200 pages VS the 1000 pages for the other book

Originally posted by Will Stevens:
I think we could agree there are a limited amount of SCEA studyguides out there, compared to SCJP studyguides. I knew this book (below) has had mixed reviews/ratings but bought it anyway, due to lack of alternative studyguides.
Has anyone used this book, and if so, what are your honest impressions of it for the SCEA exam?
ISBN: 0072226870

Thank you very much for your reply. I am glad that there are other people who feel the same way. It is no problem to make my design to support multiple clients. It kind of does that already, but do you need to include classes of the Fat client in the class diagram? (ex. like swing components)
Thanks for your help,
I am sorry about crossing the line. Hopefully I didn't cross it too much.
I haven't submit the assignment yet ... I am just wondering what will happen if I did.
So let me rephase the question a bit. Do I need to include the design for the GUI application in the Class diagram?

Originally posted by Rufus BugleWeed:
They don't tell you why you failed, so how would you know?
You are posting ideas about your proposed design, ethically you are over the line.
[ November 20, 2003: Message edited by: Rufus BugleWeed ]

I apologize if this is assignment specific, but this is a important question to me.
It was mentioned in the exam that your achitecture will be graded on how well it supports both web clients and application clients.
I just do not agree that we need an application client. If I submit my assignment with the assumption that no application client is needed, will i get a fail?
I would suggest you give a detailed assumption and explaination of your approach. As Andrew said SUN is not trying to test your understanding of the industry. As long as you make your assumption and solve the problem with the correct architecture decision then you are ok.
Conceptually, uses is also an association. I think the Date object do have an association with the lendable object, but depends on the level of details you want to show on your class diagram, most of the time they are left out.
In the case of reverse engineering the pet store ... in the implementation you would definitely found much less association (as in object creation and aggregation sense) because of performance and partical design and implementation reasons. As in your example, DueDate will just be an attribute to the lendable object in the actual implementation.
As for the books ... the author will want to illustrates the concepts and that is why they kind of take the highest details possible.
This is only my 2cents

Originally posted by noel angel:
Hi Ravi,
If you have a class that merly uses the services of another class you do not show it in an association or on a class diagram. for example:
I take a book out of the library on a date. The lendable object is associated with a specific date object called the due date which is a member of the lendable object. I may also use the Date class to obtain the string representation of the date to use for a report given nightly to the librarian which shows the books taken out that day. This is not an association only a uses relationship which we do not need to show on a class diagram. There is no semi-permanent relationship between the Date class and the report class. There is between the lendable and the due date!
There are many classes that fit into the non-associated just used category. I reversed engineered Sun's Pet store example and was very surprised how many non associated classes there are. All of the exception classes for example are used when needed not associated. Many of the factory classes are associated only to the DAO they create not the rest of the class diagram, so once they create their representative DAO's they out of stuff until they are needed again. They are associated to those DAO's however.