sankha subhra das

Greenhorn
+ Follow
since Jun 24, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by sankha subhra das

Try Jude (its free) or trial version of Sparx Enterprise Architect.
Chen,
the requirement does NOT mention anything about the new Transmaster design and hence leaves it open ended...You as an architect are free to assume anything as long as properly documented...The exam also does not constrain u w.r.t budget and/or time. Yes, SOAP might provide ONE implementation of the Transmaster service as web service. Given the abundance of framworks/patterns, u can defer the implementation of the provider till run time even, which might as well be "SOAP-LESS" invocation. One such framework thats kinda steady and supports the latest AXIS version is the WSIF framework allowing dynamic invocation as well....

These are just some of the tools to ease your migration to the web services environment easy...Document what u'd likta use in this airline specific case and explain the reason for ur choice.

Sun wouldn't penalize u for using state-of-the-art technology if you find a compelling reason to do so and feel would best satisfy the client's needs. To be frank, except for the network latency factor, i'd likta see the Transmaster component evolve as a web service. And with frameworks like WSIF, the session management as well as the use of RMI-IIOP istead of xml marshalling/demarshalling during the web services call would adequately increase the response time and hence its acceptibilty...

Hope that helps.

Sankha Subhra Das
Steven,
To my understanding, both paid and unpaid itineraries needs to be persisted...."How long" and "to what extent" is ur call....for the exam persisting paid itineraries will suffice.Imagine u running a travel agency with 20 agents and an online customer

website. Bulk of ur transactions happen via travel agents. u would definitely want to know how much sale a particular agent(in seats/class/dollar value terms) made this season...this is ur primary business and hence makes sense to persist paid itineraries. It would also help resolving discrepancies, if any.

For intelligence/reporting format, sometimes unpaid itineraries are needed...u would like to track customers vis-a-vis their itineraries and indentify a preference pattern for later marketing activies (newsletters and/or promotions).

where to store is again ur choice....could be db or flat file or an archive db...since the exam restricts ur choice of hardware choice, u might only want to persist the paid itineraries. But whatever u do, u need to mention it explicity in the assumption section. Hope that helps

Thanks
Sankha Das
Tony,
whether to model them as data members of flight class or as independent classes is ur call...

As Theodore said, "Remember, there are no 'right' or 'wrong' answers if you can defend and explain why you made one choice over another."

Thanks
Sankha Das
Steven,
am not sure if I understand the question correctly...xml-rpc is a request-based http-post protocol. Request and response, both are in xml format...

xml Stream of object basically ALWAYS returns the data in xml format which in ur case is invariably true for xml-rpc based request...It basically xml-izes ur object WHATEVER the request format.

Hope that helps

Thanks
Sankha Das
Jose,
if u look at the service to worker pattern a view can have 1::* relation with helper classes via dispatcher/controller.

u can implement ur helpers either as commands(I would prefer this) or as delegates....and then u can implement two beans and/or tags in the same jsp...nothing in the jsp specs stops u from doing so.

Hope that helps

Thanks
Sankha Das
Jo,
I assume by facade ur referring to SLSB facade. Yes, if its a PRIMARY flow in the business ur designing the system for, you need to depict all the components. Whether u depict all those in a single diagram or as separately references is up2 you.
For alternate/additional flows, you can explain in the documentation section and link it to ur primary flow diagram(fig x). Still better if u mention a little about the design patterns ur using in ur architecture early on in the documentation section.
All dependent objects that acts as first/second class objects with a direct dependency on the bean SHOULD be depicted.The finer details of what constitutes an entity bean is known to the examiners and can be avoided. At any point to avoid duplication and redundancy, you can depict the primary flow with all components and explain the rest in the documentation section.

Thanks
Sankha Das
yamini
BDM refers to business domain model. Domain models describe
business processes. These processes are documented as a sequence of
actions that provide observable value to a business actor.

For a good understanding of BDM's, refer to the following link :

http://www-128.ibm.com/developerworks/rational/library/content/RationalEdge/mar01/IntroductiontoBusinessModelingUsingtheUMLMar01.pdf

Thanks
Sankha
Anirudha,
i'll try to make this simple...

Mediator :

(i) jndi works as mediator between clients that needs services and agents that publish resources/services. jndi is facilitating this by limiting
direct interaction between these two parties, so they are not very tightly coupled to each other.
(ii) Logging of a message for audit purpose is a common mediation pattern. This Mediation entails Objects to log the incoming message to a file/database table for future retrieval or audit.

Memmento :

(1) Say u got a house in new orleans but u reside in clarksburg, wv. the house is new/refurnished so u take a photograph (Memento) of the place such that it can be restored later(or for ur insurance company to pay for flood damages), if needed. You retain the photos and hand them to the local insurance agent to pay for the damage. Note that you procured and stored the Memento, but never had to look at or use its contents.

Thanks
Sankha Subhra Das
Bharat,
precisely thats where u need to wear ur "architectural" cap and make a judicious choice. Yes travel agents will be the core of the business, hence the system should be fast/available to agents at all times.
You mentioned,
"If I use HTTP session (servlet) for both Web client and travel agent swing application, then how does the peformance differ?"
Take note first that http session can be used with web components only and NOT swing components. Now for the typical customer, you have a choice of using httpsession or SSB.There's plenty of articles on the internet discussing/comparing the two. As an architect, u need to think if httpsession will suffice for the amount of data to be stored in session. Also remember httpsession works best for storing small amounts of data like user navigation, preferences etc. I have used httpsession for my customer interface and provided justification for the same.
yes ur right when ur say that the use of SFSB will suffice both the actors' needs. Do u see any other choice than using swing components to talk to EJB's directly ? u might have ur own session management handling (like sending data back and forth between requests) or store it as a cache in agent's system. now u hafta figure out the performance impact between client side caching vis-a-vis server side caching thru SFSB's. again u hafta get back and see if the hardware provided will allow u this at the client without the need for extra caching servers. as a general rule, performance wise its faster for swing components to access business tier directly and web clients to use httpsession over SFSB's for most business processes.
As I said before, there is nothing wrong or right as far as architecture is concerned, it all depends on what assumptions u make and how best u fulfil the requirements given the hardware constraints.

Thanks
Sankha Subhra Das
Mikeh,
the answer is "it depends". Yes, its perfectly ok to follow Cade's strategy and create few ( 2-3 component diagrams).
Normally for each unique flow, there would be 1-2 VO's involved. You may not write the entire details of each VO just a mention would be sufficient.
Yes, its best to put non-functional "good-to-have" features like SSL in ur assumption section.
Yes, those 4 use cases are the ones u'll be graded on. If you feel additional use cases will support ur understanding and/or architecture, go ahead and depict it. But as for component diagram is concerned, they all will follow standard typical artifacts for each unique flow( ie view, controller, helper, validator etc).I depicted additional use cases if any in sequence diagrams to depict pre/post conditions w.r.t other use cases and left the component diagram from getting cluttered.
Yes, alternate processes are important and best represented in sequence diagram and/or in the assumption section.

Hope this helps.

Thanks
Sankha Subhra Das
I reckon if ur a busy project manager or a typical jack-of-all-projects architect designing and/or simultaneously working on a bunch of stuffs, it makes some sense to get some RATJ(rapid architecture training on J2EE...not an industry standard term....lol).

However, if ur into J2EE for a while, a formal training will add on to ur already pressing time requirement preparing for the scea.

Thanks
Sankha Subhra Das
Chao,
Sun's architecture guide by Cade and the book by Barbara provides an example architecture. Along with that, posts from other ranchers and yahoo groups about individual experiences should suffice.

Thanks
Sankha Subhra Das
Jo,
yes there is nothing that disallows part 3 before part 2. I've done it as well with a week gap between the two.

Thanks
Sankha Subhra Das