The main HINT I took from Alain Hunsung's POST about two meanings for flights. I think that is the core of the design.
do u like to tell us the two meaning of the flights in detail?
How many component diagrams did you have?
I'm planning to deliver 2, do you believe this can be a problem?
How many components did you have? Did you map all your classes (business (entity beans?) and service classes) to components
1. While it is understandable that the Oracle database in the 'Frequent Flyer' system can be accessed by the Business Entities and DAO(s) of the new application, but how do u propose to reuse CGI & perl scripts?
2. Let's assume that we create links from the new j2ee application, to the pages of the 'Frequent Flyer' system. That would mean that the HttpSession established in the j2ee web-app, be carried over to the 'Frequent Flyer' web-app. This can be achieved by session replication techniques. However, the big qs is: if a Customer, after visiting the pages of the 'Frequent Flyer' web-app, wishes to return to the j2e web-app?
To do this, we need to introduce links/buttons in the 'Frequent Flyer' web-app, which point to the j2ee web-app. But, as per requirements, the 'Frequent Flyer' system cannot be re-written!
Considering these issues, I am proposing that ONLY THE DATABASE from the 'Frequent Flyer' system will be reused, and NOT THE WEB COMPONENTS
The quote is from http://www.webopedia.com/TERM/S/screen_scraper.html
Software that allows a PC to intercept character-based data from a mainframe -- often presented in a green screen -- and present it in an easier to understand graphical user interface (GUI ). Newer screen scrapers present the information in HTML, so it can be accessed with a browser. Leading makers include Mozart (www.mozart.com), Flashpoint, Inc. (www.flashpt.com) and Intelligent Environments (www.screensurfer.com).
Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.
Originally posted by Dhiren Joshi:
When I meant screen scraper I didnt mean the literal meaning for a main frame screen scraper.
The techonology u wwill need to use would be the same but u wuold scrape through a web page so the term screen scraper. (It would be a HTML parsing of sorts)
Is it required to show the thick client design in the assignment. If we can show the design of the middle tier and how it can cater to any type of client won't it be sufficient.
I read in on the posts that someone didn't show the thick client tier in their assignment. Any suggestions
Originally posted by Dhiren Joshi:
Thick client. R u referrring to the Swing. Yes from my experience, U need to show that at least in the component diagram and explain security u would use for it .
U dont need to show for sequence diagram any flow particularly to the client but again your sequence diagrams need to be good enough in case that flow needs to be supported for thick client.
Thats the technique I used and u would need to add a few assumptions design detail for the client so that the grader would understand your design.
[ May 08, 2005: Message edited by: Dhiren Joshi ]
Container managed against application managed.
The problem is if I just say container managed I am sure it wont be sufficient. What level of details we need to furnish
For the use cases' sequence diagrams, what do u think if I just use "Client" to represent both type of client (i.e. Swing and Web)?
I find that many ranchers design a web framework for the web client. I wonder whether the framework for spring client is also needed.
People are talking about 1,2,3 components diagrams. I have one question, when we seperate component diagrams. i mean one component diagrams consists many component then why we need 2 component diagram.
Whip out those weird instruments of science and probe away! I think it's a tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton