Beruflich Dokumente
Kultur Dokumente
SYSTEM
Plan your holiday as you go
PROJECT IDEA:
APPLICATION ARCHITECTURE:
USE CASES:
X is on a vacation at Los Angeles. He takes a look at his schedule for the day
on the SmarTraveller application on his mobile phone and sees that he has a
visit to the museum planned in the morning and a trip to San Diego Zoo
planned for the evening. The helpful weather forecast feature for each item in
the itinerary shows that it is slightly cloudy in the morning and is expected to
rain in the evening. X decides to change the order of the schedule so that the
visit to the Zoo will be done in the morning when it is cool but dry and the
museum tour will be in the evening. He switches back to the itinerary day
view and changes the items to the new order.
BUSINESS MODEL:
1.1 Objectives
SmarTraveller is a small business that is aiming big. The three main
objectives are listed as follows:
1.2 Mission
In such a fast changing world, where people do not have time to “Stop and
Stare”, holidaying becomes an important aspect of life, especially when it
acts as a stress buster. Recreation is essential. SmarTraveller strives to be
the best choice for clients by helping to ease their holiday planning burden,
ensuring a worry-free and hassle-free vacation at a reasonable price.
Being in sync with the current market needs, combining technology and
trends and providing customers reliable service is the daily mission of the
SmarTraveller group.
2. SERVICES
The breakdown of the market for holiday planning falls in a wide, very diverse
grouping. Individuals as well as organizations demand the services we
provide. The market segments have been broken down into Individuals, their
family and friends and age groups.
Our largest clients will be normal everyday life human beings who wish
for a break and need to plan everything from scratch. The sheer
volume of such people is what makes this section of people to be
driving our profits. These people also will have set vacation times in a
year allowing us to focus more in their behavioral predictions and
tailoring the services we provide to them.
2. Age Groups
• Under 24: Persons under the age of twenty-four (24) using a holiday
planner will be least in number. We hope to tap the early college
graduates who have begun their professional careers but have not yet
started their families. The revenues generated will range from
moderate to high, depending on the destination and volume of
students using it.
• Ages 25-55: The persons that fall into this age group are employed,
middle to upper-middle class families. The reason they choose holiday
planners is they are too busy to do it themselves. Therefore,
Smar”T”raveller will be on hand for questions, contact will be moderate
in length but occur regularly so as not to disturb the daily life of the
families. These will generate moderate revenues, with a few
generating low and high revenues.
• Ages 56 and above: Persons over the age of 55 have reached the
turning point of life. These events will generate moderate to high
revenues depending upon the income level of the family. Their age will
give them the freedom to stay on vacation longer they will have none
or least commitment towards work and other income earning duties.
Though they might have the time to plan an entire vacation most of
them would not do so as it would be too much of a hassle. They would
prefer following an automated guide and enjoying the vacation. This
will be our critical market section.
Our target markets are middle to upper middle class families, individuals,
couples or small organizations. We choose them as they are the ones which
would have the resources financially but little time to plan all the events.
Families need recreation and employed individuals may be overburdened
with work. Thus they generally ignore this aspect of life.
Thus SmarTraveller allows them to spend enjoyable time with friends and
family without getting their hands dirty in all the planning involved.
Cost Model:
The cost model involves cost relating to setting up the business unit ,
running costs and also the profits and the fee charged by us for
providing the services. According to certain figures , the statistics
would be as follows :
EXPENSES INCURRED :
Cost for collaboration and association with Trip Planner sites: $50,000
Development and Software Support : $40000 per person annually with a rough estimate of 4 - 8
people
PROFITS INCURRED :
REVENUE GENERATION:
4.0 Competition
Our application is mainly a live real time guide to a trip which is not offered
by web based trip planning companies.
Although local tourism companies do offer a real time guide, but their
schedules are rigid and also their trip is not tailored for an individual or a
family. It is meant for the majority and all may not have the same taste. Our
application is based on every individual or family making it personalized.
For people who wish to plan their own trip this would not be useful. But
we are right in assuming that the volume of such people will be very
small which would not impact our business.
MOCKUPS:
1) After the welcome screen, the user sees the itinerary he had
planned with holiday planner websites like kayak, makemytrip
etc.
• During the travel, when the user clicks on Day 1 of the itinerary,
it navigates to the plan for the first day. When MAP is clicked, it
shows the location of the current coordinates.
• When the user clicks on the next feature Tourist Attraction, apart
from the normal itinerary being shown, the system will suggest
other places ( For eg. A zoo in Los Angeles might be near some
location visited in the current itinerary).
TECHNICAL ARCHITECTURE – CLIENT SERVER ARCHITECTURE
SCREENSHOTS:
Welcome Screen:
LEARNING :
• Considering the fact that Android has an updated SDK 0.9, it takes a while
to get acclimatized to it and begin using it. There is limited help available on
the website and not enough literature, reference or tutorial available that
assists you in covering every facet of developing android applications.
Though basic tutorials do exist, they are few in number and contain very little
help for detailed design.
• All codes point to the older versions of the SDK and a lot has changed ever
since the updated SDK. It takes time to figure out the equivalent function and
get it working. Thus, a bit of trial and error is needed with the fear that after
implementing relevant functions, it may not work.
• The Google documentation for getting this running is accurate and must be
followed.
• Forums (anddev.org) may be of help as users face similar problems, but it
needs a thorough search which may sometimes lead to a wrong suggestion.
Again, one’s patience may be tested here.
ROADBLOCKS:
• Since we extracted lots of data from Yahoo API, Yelp API etc., we found
that implementing everything in the phone would make it
tremendously slow. Hence we decided to use a Client Server
Architecture and performed all our operations on the server and with
MySQL as the server database. Though this helped us make the
application on the phone extremely light, it was hard getting the initial
server-database-android interaction to get working
• Yet another major issue we faced was in getting the client-server
communication. We started with a HTTP connection, to perform HTTP
Post but later found that many headers required for HTTP connection
are not available in the recent SDK. Hence we found an alternative for
it and performed URL connection. Due to very less availability of
tutorials or documentation regarding this, we had difficulty figuring out
its proper usage.
FUTURE PLANS:
• To notify customers about flight delays or any other hazards caused which
could cause a potential damage.
• To prepare a master itinerary that could be shared with the family
members who could discuss about the same
• To include more dynamic feature
• API’s used
o Yelp
o Yahoo
o Google
• Other Resources
o Initial Itinerary from travel web sites