SCHOOL OF ENGINEERING, COMPUTING AND IT
In Collaboration with Stamford College
Module Title: Distributed System
Research Topic: Topic: Travel Agents management system (TAMS)
Student Name: Izeuma Isaac Ede
Module Code: CN3057
UEL Id: u0855510
Stamford Id: 1118079
Module leader: THINAGARAN PERUMAL
Date of Exam: Dec, 2011
Intake: Fed 2009
Table of Content
Chapter1. Introduction
Chapter2. Technical review
Technical Architecture Design
Technology Requirement
* Server:
* Development tool:
* Databases:
* Communication protocol:
* Network component:
* Middleware:
Chapter3. Proposed System Design and Methodology
Background
Overview:
Used case diagram for TAMS
An initial use case diagram of TAMS
Requirements Analysis
Book Trip Use Case Diagram
Complete Used Case Diagram
Sequence Diagram
Research Methodology
Chapter4. Evaluation and Discussion
How RPC works:
Chapter5. Conclusions
Chapter6. References
The Essay on Chapter 5 Case Study 1
1. What do you think some possible drawbacks from recruiting from social network site might be? Some possible drawbacks from recruiting from social network site may be that it opens up the possibility for hackers to commit fraud and launch spam and virus attacks. It also can increases the risk of people falling prey to online scams that seem genuine, resulting in data or identity theft. 2. What ...
Travel Agents Management System (TAMS)
Chapter1. Introduction
Currently, Tourism is one of the most important and energetic segments in the current world. It has contributed around 13% of the world economic and it has added two of each felt hen of it work positions in the near feature, 108 million tourist will travel around the world and the will be million’s of dollar’s spill in the economic growth world wild. In México the tourism sector contributes with over 7% of the nation PIB and it also contributes with more than 9% in direct and indirect work position (conse jo de Promocion turistica,2006).
Realizing the important of tourism industry, travelling schedule and information carries a lot of weight in achieving the goal of tourism.
To aid the industry, I proposed a travel agency management system (TAMS).TAMS is an online integrated travel agency booking and management tool. TAMS will be designed to assist the client, and also the travel agents in managing the administrative and accounting functions of the agency more efficiently and effectively so that the agent can focus on sales, and satisfaction of his client. Also TAMS make it easy for inside, outside or independent agents to quickly access the system from anywhere, at anytime. It also keep you inform in real-time, making sure that reports are generated and your agents are properly managed and controlled.
Chapter2. Technical review
Technical Architecture Design
Currently, client/server traveling agents architectures are focus make on information system. A massive migration from host-centric to network-centric system is underway in every major public and private business.
Client/server traveling agent’s technology is capable of quickly delivering new and better service and value to customer and to the business. Its standard of enabling integration in different system components is built on open systems. Also it far more user friendly making the end user (Client/Agent) have controls will let them do their analysis and reporting without the intervention of information system.
A successful introduction of new systems and technology requires a thorough understanding of what exist today. There is a key factor that will enable you to understand the existing architectures. This key factor of the architecture design is technology requirement.
The Term Paper on Web Server System User Interface
Project 5: Good Neighbors Campaign Project Description: Develop a database to keep track of 20 data points for each of USC's 10, 000 employees for the past 10 years (and years to come). This database would need to have the ability to generate reports based on various queries in order to answer questions about donation trends among the University employees. Team Members: David Stark David Jena ...
Technical Architecture Design
Component | Product | Configuration(including version) | standard | Software installed |
Database server | HP 9000 | 64MB RAM;200 GIGHD NT;Number of process or TBD clustered with business server. | yes | X-open SQL Sybase system11 with replication server gateway IBM MQ series. |
Admin. Server | HP 9000 | 64MB RAM;200 GIGHD NT;Multi-processor. Development machine will have 2 processors. Production machine clustered with data server. | yes | Enter a IBM MQ series compeller PVCS EnCana, multi-Tier 4GL |
Agents | Acer | Pentium, 75 -100Mhz 24MB RAM, 1 GIG HD Win95, card reader attached and HP printer | no | Enter a RPC power builder SQL anywhere using TCP/IP |
Client-Check-inCheck-out | Web browser application | | no | |
Network | EthernetInternet | | yes | T,TCP, IP |
Middleware | EthernetInternet | RPC | yes | Client to Bus Rules server |
Technology Requirement
The competitive and technology nature of travel agent market has changed the way travel agencies operate. However, to meet changing in business the technical architecture will define all components require by the technical infrastructure. In accomplishing this, the system adaptive range translates the balance between being driven by a return on investment and being driven by adaptability.
The following is an explanation of the components may be included in the technology requirements: these include servers, development tool, databases, communication protocols, network components and middleware.
* Server:
When dealing with server with server the most important thing is choosing server that is standardize on vendors, versions of operating systems, model and software configuration. Generally speaking, disk space shouldn’t be a big issue with web servers.
* Development tool:
This is to standardize on a small set of tools like two-tier client development tool (object-oriented tools and cross platform) mult-tier tools, internet/intranet and server development tool; for each type of platform.
The Essay on Operating System Server Client Network
Functions of an Operating System Operating Systems is a computer program that controls the operation of the hardware of a computer and the execution of programs. The primary functions of an operating system include: 1) Managing and controlling the hardware of the computer, e. g. , drivers 2) Interfacing between hardware and software, i. e. how programs and applications use hardware - keyboard, ...
* Databases:
Is understanding the business requirement to accelerate decision making is the key to choose a database technology.
* Communication protocol:
This is dealing with systematic planning, implementing and monitoring of all channels of communication protocols.
* Network component:
It consists of two important parts which are the items that are to be connected and the equipment that connect them. E.g. the following are hardware that are members of the networks (connects the computers and peripherals).
* Network switch
* Computer networking network router
* Broadband modem
* Network hub
* Router/Switch
* Nic card
* Middleware:
It connects software components of a distributed application or software that functions as a translation layer.
SQL
Fegure1.
UNIX Windows Server App
DCS
DB2
Tuxedo
Oracle
Remote CORBA Objects
Application Server
Web Server
Server side/Processing
Web Browser
Client PC
Messaging Transport
Application/Software/Middleware
Briefly on this section of this report, let do a little more on summarizing, but still lend perspective to the many activities, past and present, which contribute to making middleware technology an area of exciting current development, along with considerable opportunity and unsolved challenging problems. We have provided references to other sources to obtain additional information about ongoing activities in this area. We have also provided a more detailed discussion and organization for a collection of activities that we believe represent the most promising future directions for middleware. Downstream, the goals of these activities are to:
1. Reliably and repeatable construct and compose network-centric systems that can meet and adapt to more diverse, changing requirements/environments.
2. Enable the affordable construction and composition of the large numbers of these systems that society will demand each precisely tailored to specific domain.
The Term Paper on Disintermediation and Reintermediation of the Travel Agents
1. INTRODUCTION Nowadays, the travel distribution channel is very complex and characterized by the presence of many different kind of intermediaries which operate in a very competitive market. Since the beginning of the travel industry, intermediaries have always played an important role for the development of tourism products and services. Indeed, intermediaries have the ability to organize and ...
To accomplish these goals, we must overcome not only the technical challenges, but also the educational and transitional challenges, and eventually master and simplify the immense complexity associated with these environments, as we integrate n ever growing number of hardware and software components together via DOC middleware.
Chapter3. Proposed System Design and Methodology
Background:
In this proposal, TAMS has been picture in the design and development of travel agents management system. These include the technical architecture design and technology requirements. Also this paper will briefly present a wide survey of critical issues in the design and implementation of distributed system in travel agents management system using RPC mechanism. The following section should describe some steps of message exchange and communication in TAMS distributed system using RPC communication mechanism.
Overview:
Remote Procedure Call (RPC) is a protocol that program used to request a service from a program located in another computer in a given network without having an understanding of the network details. Requesting for a program is a “client” and service providing program is the “server”. Base on my topic travel agent management system (TAMS), I will be using remote procedure call (RPC) to determine the steps of message exchange and communication. And they are as follow;
1. Client procedure calls client stub in normal way; this procedure calls the client stub in the TAMS travel website or link and try to locate the server normally.
2. Client stub build message, calls local Os; this is when stub abstracts procedure calls between processes on the operating system of the stub server.
3. Client’s Os give message to remote Os; it involves passing message sent form the client machine to the server machine.
4. Remote Os send message to server stub; in this case the TAMS server Os hand the message to server stub which will be sent to the client.
5. Server stub unpacks parameters, calls server; this is called the server-side stub, and it involve in receiving form the client-server stub which unpack the marshaled parameters, also it performs the procedure on the server.
The Term Paper on Peer To Peer Network Server Security Client
Peer-to-Peer Networking vs. Network Domains Difference Between network can be based on either a peer-to-peer level or server-based, also referred to as domain-based. To distinguish the difference, a peer-to-peer network, also known as a work group, is a network in which a group of computers are connected together to share resources, such as files, applications, or peripherals. The computers in a ...
6. Server does work, return result to the stub; this is when the server gives permission to the travel or user on the TAMS travel agent website.
Figure2.
Database
Destination User login
Admin
Travel schedule
Used Case Diagram for TAMS
Before we go into detail, let look at some points of finding a proper used case diagram for travel agency management system.
Firstly, the main aim of this project is to provide a flexible and reliable environment for travelers that wants to travel to see the sight scenes, shopping or for business meeting etc.
The company (TAMS) wants to offer to people the ability to book complete vocation packages and for agents to be able to focus more on the important modules in the system.
An initial use case diagram of TAMS
Figur3.
Book Trip
Cancel Trip
Customer Agent
Note: the following will be the requirement for TAMS.
* Initial requirement description
* Entering the requirements analysis phase
Requirements Analysis (As a TAMS agency you need to answer these questions):
* What features do we need?
We should be able to create a customized trip for our customers.
* What does this involve?
Through an interaction between customers, travel agents, and architects (designer and developer)
* Customers want?
The key member of this group is the customer, so customizing a trip is the most important.
Now that we know what our system must be able to do, we start thinking of a complete case diagram for both participant (customers and agents) and the most important thing is TAMS (Booking a trip and canceling a trip) as since in figure 4 below. According to Jeffrey .O, the third strategy involves the developing agent asking the customer question about their needs and formatting the answers into requirements for inclusion in top-level specification, to the analysis this process should be part of every requirements analysis activity in distributed system.
Book Trip Use Case Diagram
Book/Cancel Trip
Extension point: Trip extras needed?
Figure4.
The Essay on The Composition of the Business of Travel Agent
The Composition of the Business of Travel Agent and Tour Operator or how They are comprised. First, what is Business travel? Business travel is stated as the practice of people traveling for purposes related to their work. It is on the rise especially with foreign business markets opening up. Then now, Travel agents are professionals who provide assistance with organizing and booking travel. At ...
Book/Cancel Hotel
Client Agent
Book/Cancel Flight
Reserve/Cancel Trip Extras
Figure5: Complete Used Case Diagram
Sequence Diagram
It testing should handle a simple travel booking and expect a positive processing to the end. The test case neither simulates business errors nor technical problems. Next picture shows the use case as a sequence diagram.
The travel agency puts a travel booking request towards the system. The travel booking contains two separate flights. The flight requests are published to the airlines (SmartAirline and RoyalAirline).
Both airlines confirm the flight bookings with a positive answer. The consolidated travel booking response is then sent back to the travel agency.
Figure6: Sequence Diagram
Pseudo code
Input (I-Customer_status) Agent
Select (I-Customer_status)
Case(TravelBookingRequest)
Case(TravelBookingReponse)
End Select
Procedure Booking
Begin
Read I-member_no, I-telephone_no from Agent
Select * From Customer Where Customer_No = I-Customer_No or Telephone_Number = I-Telephone_No
Read (all attributes of customer) from Agent [Note: user changes Travel Info the input form] which contains the retrieved data.]
Update Schedule
End
Procedure New
Begin
Read (all attributes of customer except Customer_No) from Agent)
Read I-Customer_No from Scanner [Note: the customer number is scanned from a blank member card]
Insert Into Customer Values (from flightr and car input)
End
End
Research Methodology
In the previous sections much has been emphasize on technical review of the model of travel agent management systems. The following section in this paper will be discussing on the methodology used for this study.
As reviewed form sources like journals white papers and books in other to pile up information in this project, I indentified some awareness problem of choosing the right mechanism in this case “RPC” in distributed system.
Chapter4. Evaluation and Discussion
In achieving the goal of this project, we must first understand the problem of indentifying and choosing the right mechanism, as well the research objective in the study. I have decided to evaluate the distributed system by implementing remote communication using RPC mechanism in the selected distributed system application. The architecture design research was preferred as a high methodology to be followed in the cause of study, which take us to our current state of tackling and overcoming the awareness problem of choosing the right communication mechanism.
The project aimed to be a proof of concept application that will demonstrate TAMS distributed system is useful and easy to use. We will discuss issues regarding the choosing of the right mechanism RPC.
Construction a distributed client-server based applications, RPC is a powerful technique. When calling procedure, the called procedure need not exist in the same address space. With a network connecting them, the two systems may be on the same system or they may be on a different system on a network connecting them. We will be disusing the details of the interface with the network of distributed applications by using RPC. Which allows the application to use variety of transports and physical and logical elements of the data communication and application by the transport independence of RPC isolated the application, but first let go briefly on how it work;
How RPC works:
An RPC is dry to a function call. Caller waits for a response to returned from the remote procedure and the calling arguments are passed to remote procedure when an RPC is made in functional call. During the flow of activity Figure 1 shows an RPC call between two networked system .To send the request to server and wait the client make a procedure call. Until either a reply is received, or it times out the thread is blocked from processing. The server calls to send something fixed that performs the requested service, and sends the reply to the client when the request arrives .The client program continues, after the RPC is completed. Network applications are specially supported by RPC.
A second limitation was encountered in the listener mechanism. In order for the TAMS to be able to notify the client of changes, the server must be aware of the client’s address. In the WLAN environment, this problem can be solved by notifying the server that the devices address changed, updating the callback information. This solution would introduce the problem of notifying the moment the event has occurred, but we consider it is a more reliable solution and it is not dependent on the clients frequently changing address but machine scheduling.
Chapter5. Conclusions
In this report we discussed how TAMS is designed to assist the client, and also the travel agents in managing the administrative and accounting functions of the agency more efficiently and effectively distributed system. Two important areas were identified in the management system; one is a massive migration from host-centric to network-centric system which is underway in every major public and private business and the other is the key factor of the architecture design in technology requirement. A description of the components are to be included in the technology requirements which include Servers, Development tool, Databases, Communication protocols, Network components and Middleware distributed operating system.
Success with early, Complex distributed application requirements and simpler architecture provided by bundling existing network systems, operating systems, and programming languages led to more ambitious efforts and expansion of the a wide survey of critical issues in the design and implementation of distributed system in travel agents management system using RPC mechanism, The result has been a deeper understanding of the large and growing issues and potential solutions in the space between the steps of message exchange and communication in TAMS distributed system using RPC communication mechanism. There are significant limitations with regards to building these more complex systems today. For example, applications have increasingly more stringent requirements.
Chapter6. References
Grady, Jeffrey O. “System requirement Analsis” Elsevier Inc, 2006.
Temponi, C., Yen J, Tiao W.A., “House of quality: A fussy logic-based requirements analysis”, European Journal of Operational Research, Vol.114, pp. 340, 1999.
