Web clients and application client

[Andy Chow]

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?
Thanks,
Andy

[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 ]

[Andy Chow]

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?
Thanks,
Andy

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 ]

[Levent Gurses]

Andy,
You are bringing a good point about the assignment. Sun wants us to design the application in order to demonstrate ability to support multiple client types. I would certainly agree with you, that in your judgement, you might think that a fat client is not necessary. If you justify your opinion with a solid argument, I do not see any reason why Sun should reject it. But there is also the requirements document, that the FBN wants to have a fat client. Also, you do not have the analyst to discuss the issue with. So, in a way it makes sense to play it safe and design for fat client, and in the meantime take the opportunity to think and learn about J2EE applications that serve to multiple client types. I had the same dilemma, but at the end it turned out that just adding the fat client transfomed my design into a more stable and sophisticated one. I hade more fun too.
Hope that helps, and wish you the best in the assignment.

[Andy Chow]

Levent,
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,
Andy

[Andrew Monkhouse]

Hi Andy,
Like Sam Joe's question the other day, I think this is an acceptable topic, although it is also close to the line.
[side note]I am going through the opposite argument at work at present: one of the other people wants to only have a web enabled J2EE application, and I am pushing to have that plus a fat J2SE stand alone application [/side note]
I think you could get into trouble if you decide that the client's requirement is not required. As Levent said, you cannot discuss this with the analyst or with the client. They may have some reason for wanting the fat client that they just haven't mentioned.
One of the measurables that I have seen mentioned, for both this and the SCJD assignment, is the ability to follow the instructions, even if you don't agree with them. In giving us the certification, Sun are, in effect, telling potential employers that we are architects. They don't really want to be saying that someone is a good architect if they ignored some of the requirements.
End result: my feeling is that you should support the fat clients.
Regards, Andrew

[Rufus BugleWeed]

If you followed this forum for a long time somebody passed with just a web client. :roll:

[Nishant Anshul]

Hi Andy,
i agree with andrew. it's likely u will get thru w/o fat client but it's prudent to include that case also. It emphasizes ur flexibility to consider such scenarios also where u r not comfortable....just to honor ur customer (sun in this case) with rgds,