This document outlines a project plan for a tourism mobile application. It includes sections on the workplan and results, stakeholders, benefits and risks, architecture, scenarios, and proof of concept. The workplan lays out the project phases from idea through programming and deployment. Stakeholders are identified based on their influence and interest. Risks are analyzed in areas of schedule, scope, and resources. The architecture section describes key values, deployment, and a use case. A proof of concept demonstration and documentation is proposed.

1. Giacomo Giorgianni
Hesam Alipoor
Ghazaleh
Shoajee
1.Project Workplan &
Results
2. Stakeholders
3. Benefits & Risks
4.Architecture
5.Scenarios
6.Proof of concept

2. Workplan:
Project
Use-Cases
Workplan
Fulfill
Identificatio
Resear
Concept
n
ch
Architectur
Definiton
Core Modules
e Design
High
Testing
level
Phase
Idea
IDEA
PREPARATION DESIGN
Identificatio
n:
Stakeholder
s
-Risk
Analysis
Providing
Demo
(HOPEFULLY!)
Fulfill
Database
PROGRAMMING POPULATION
Interaction
User Interface
Identificati
on
Deployment

3. Stakeholders:
I
N
F
L
U
E
N
C
E
• Travel
Companies
• Travel
Companies
• Main
Tourist
Authority
• Attractions’
(ENIT,…)
Manager
• Tourist
Service
Provider
• Local
Tourist
Authority
• Tourist
Information
Provider (Tourist
Center…)
I N T E R E S T
• Visitor
• s
Tourist
s
• Local
Shops

4. Risks Analysis:
SCHEDUL
E RISKS
SCOPE RISKS
- Application not
Supported (Fragmentation)
-Errors in estimation
of phase division
- Geolocation
Estimation Error
- Closeness of
attractions
- Single Point of Failure
(Geolocation)
- Big
- Internet
CompetitorsAvailability
Dependence
- Lack of Programming
- Lack of Funds
Skills
From investors
- Lack of interest
form Users or Sellers
- Lack of
- Dependencies
between phases
RESOURC
E RISKS
Information and
Material
High risk
Medium Risk
Low

5. Key Values:
• Innovation
• More-Way Business:
• User Side: Save Moneys!
• Seller Side: Get more customers!
• Enjoy the city and discover it
• Treasure hunt – like involvement
 FUN!
• Reduce Planning Time
• No fear of missing attraction
• Users involvement
in improvement
• No registration needed

6. Deployment:

7. Use Case 2:
App Navigation

8. Proof of concept:
• Software Live Demonstration of:
 List of attraction in the city
 Attraction Page Navigation
 Geolocation Service (Hopefully)
• PowerPoint presentation including:
 More specific design Details
• Word Documentation with
Development details

9. Thank you