In the spec it states that the travel agents would like to replace "the 3270 terminal" now does that mean the application must be built using a graphical user interface? Many thanks for any advice/comments etc. Cheers David [ September 09, 2002: Message edited by: David Raid ] [ September 10, 2002: Message edited by: David Raid ]
I don't think you're missing anything. I think you show insight, maybe even saying too much. I believe the travel agents are on an intranet, No? [ September 09, 2002: Message edited by: Rufus Bugleweed ]
"3270" terminals based apps are generally refering to monolithic cobol/mainframe applications. These applications are based on screens; the user need to know the name/id of the screen that they want to use - there is no concept of hypertext or links that makes these screens really cumbersome to use and the learning curve for such systems/apps is very steep. Moving away from 3270 means more than just moving to a GUI application. Obviously that is one big reason. Can I have a friendly user interface without using GUI - yes checkout the banking applications written in DBase/Clipper
Yes i agree on all the points on the terminals. They go hand in hand with the IMS system that is currently used. You see the requirments is for a "Java Application" for the travel agents but can a browser be counted as a sort of java application? allbeit a java aplication by proxy i.e displaying the info from the server. probably not but IMO a fat client would need more diagrams. 'Most' people seem to think that the four suffice. These things are sent to trouble me.
I think what i am trying to figure out is how much of the client plays in the final design. Is it good enough to have a client on the diagrams pass over its requests and no more? Are we really just designing the app server tier?