3. Description
• Our backbone is based on the already existing
system of phone-tracking-system
• Our goal is to develop an enhancement of that
idea in order to create a traffic report
4. • Every 60 seconds app-users are sending its own GPS-
location to a central server.
• In order to identify bad traffic-conditions our server is
using the informations about the driving activities and
the movementspeed to compare current movingspeed,
with regular traffic-conditions.
• Our system mark streets with traffic jams in red on
Google Maps and calculates how many minutes you
loose if you use them, no matter if you are driving by
car, by bike, or if you are using public transportation.
6. Target audience
• Firstly, students and teacher of our schools
will be targeted
• Later, we will also target other people in order
to improve the relieblility of our system
8. Location
• At the begin our traffic report will start up in
Munich, Zaragoza and Zebugg, but if our idea
is successful we would expand to other cities
10. Cost analysis
• Start-up costs: 1000€-4000€ für Server
• Fixed costs: see start-up costs
• Break-Even-Point: 1000€= 10x x=100
(in order to reach the profit zone we have to
get 100 users who bought our app for 10€)
12. SWOT-analysis
• Strengths: -does not exist in this way
-backbone already exists
• Weaknesses: - hard to realize
-expensive start-up costs
• Oppurtunities: -could be a trend
• Threats: -no experience in programming
-high costs
14. Local competitions
• Google Maps traffic report:
Shows you where traffic jams are, but not how
much more time it would take if you drive this
road.
• Traffic report in the radio:
Tells you where traffic jams are, but you can‘t
see the traffic jam in a map.
