“IT IS BETTER TO SEE SOMETHING ONCE THAN TO HEAR ABOUT

IT A THOUSAND TIMES.”

LET’S EXPLORE PAKISTAN

A Project - A vision to promote the tourism industry in Pakistan

By

Hurmain Javaid (BSEF19M004)

Nimra Haq (BSEF19M010)
Iqra Sarwar (BSEF19M012)

Submitted To

Professor Amna Mirza

 VISION
“OUR VISION IS TO HELP PEOPLE DECIDE THE NICEST POSSIBLE
DESTINATION IN PAKISTAN FOR THEIR PERFECT HOLIDAY”

Explaining our vision:

 It is to PROMOTE THE TOURISM INDUSTRY IN PAKISTAN; give people the
visionary explanation of why Pakistan tops the list of WORLD’S BEST TRAVEL
DESTINATIONS and ranked as one of the 10 COOLEST PLACES TO GO.
 Our vision is to help people choose the best travel destination (in accordance with
their interests and budgets), to better satisfy them with the options they
consider.
 Our vision is to provide people with an easily accessible application by everyone (like
Amazon and Daraz) by better creating an easy and essentially needed interaction
between the tourism service providers and the tourists through our application.
 Our ultimate vision is to assist the economy of Pakistan by bridging the gap
between demand and supply in the Pakistan tourism industry.
 Our application will be unique and have a larger marker value because no competitor
exists till the time.
MAJOR REQUIRMENTS
Functional
Let’s Xplore Pakistan is a software application. At first, a home page is presented to the
user where a brief introduction to the vision of software is presented. User can select to
sign up or login from the home page. User can also proceed to explore the application
without login or sign up. In this case, they can get to know about tourism spots, relevant
services provided, view aesthetic pictures and videos in gallery, and read the posts shared
by other users.

User can sign up or login to the application. While signing up users must specify
themselves as service providers or tourists.

If a user sign up as tourist, he/she can view and post pictures and videos in gallery, can
share and read blog posts, explore the services provided at various tourist spots, avail
these services, pay online for them, and book them ahead of time. Users can contact
service providers, they are provided facilities to send text messages, make voice and video
call, schedule meeting and send emails within the application. They don’t need to use third
party applications for above mentioned operations. Users can also cancel or modify any
bookings and payment they made. They can rate the reliability and quality of the services
of a specific service provider.
If a user sign up as service provider, he must sign a contract to work with our application.
After sign up he/she can offer different services. To add a service, different categories
are provided. User first select a specific category and then provide all the required
information to add service successfully. User have the capability to contact tourists, send
auto-generated emails, and offer special discounts to particular tourists. They can also
utilize gallery and blog post features.

Application contains a hierarchy of the UI. All the services are categorized by the
tourism spots they belong to. All the services related to a specific spot are further
categorized based on their nature. For example hotels and restaurants are hospitality
services. All the extra information about each spot and service is listed under know-how
section. Know-how section of a spot may contain road maps, details of petrol pumps and toll
plazas on the way. And know-how section of a hotel may contain information about the
number of rooms and availability of rooms in that hotel.

SUPPLEMENTARY SPECIFICATIONS
Usability
Application must be user friendly, and have an aesthetic look and feel.

Color choice must be user friendly to special users too. Like color blind users.

Screen reader facility must be provided to aid users who are blind.

Application must support different languages recognized globally to facilitate all type of
users and serve across the globe.

Proper documentation and 24/7 active help must be provided to all users at the comfort of
their couch.

Simple, elegant and consistent software design must be used in the application following a
rule “What you see is what you get.”

It must be easy to navigate, customize and accessible.

Application must have a good enough speed and throughput.

Reliability
Application must be reliable and respond in time.

Users account must be authenticated while logging in.

Users must be able to recover or reset their password after proper authentication.
User must be able to recover their account in case of failure and back up their data.

Service providers provided information must be verified and reliable. All the information
must be verified before posting and sharing in gallery and blog posts.

There must be policy to avoid scams in domain rules which all the tourists and service
providers must abide by.

Good error handling is essential part of reliability. All possible errors must be handled
properly.

There must be systematic way to handle the failure of the system on which our application
depend.

Performance
Application response time, recovery time and throughput must be optimal.

Application memory consumption and RAM utilization must be limited and optimized. It
must consume the system resources efficiently.

Application must be able to work with unstable connection and less memory and other
resources.

Application speed must be efficient enough to boost the user experience. It should not lag
behind or become unresponsive.

Application must be implemented with efficient algorithms to facilitate fast searches and
large data volume handling.

Supportability
Application must be able to accommodate all the changes that may occur in future and
adapt with the need of hour.

Application must handle the growing demand and traffic with the passage of time.

Application must me maintainable product, all standard and best practices must be
followed while production.

Application must be configurable, user must be able to easily personalize and modify
application features according to their choice.

Application must supports internationalization, worldwide users must be capable to

configure it according to their own culture and language.

Application must be easily installable in all environment. I.e. desktop, iOS and android
Other Requirements (+)
Implementation

Application is programmed in android development kotlin programming language and use

java as secondary support if required.

Application must support all the operating systems including windows, Linux, android and
iOS etc.

Application use cloud based Microsoft Azure database for storing and managing
information.

Application must not consume valuable resources of the system inefficiently.

Hardware interfaces

Application must support a touch screen and screen reader facility.

Application size must not exceed 50 megabytes for mobile devices.

Application must be useable without interact but user can interact with other only via
network.

Software interfaces

Application uses following different API to facilitate online payments and communication.

 Online payment verification system

 Audio calling API
 Video calling API
 Online Meet API
 Emailing API
 User authentication system
 Weather forecast API
 Google Map API
FEATURE LIST
As we are making an application, that can be accessed by the users and the service
providers. So, we will discuss the features for all the interactors:
1. View homepage
2. View gallery photos and videos
3. Read blogposts
4. Explore different roles of users, i.e. service providers and tourists
5. Sign up as tourist
 6. Signup as Service Provider
7. Login
FOR Tourists: (user in this section refers to tourists)
The application does:
1. Provide a List of all worth-seeing spots in a proper view on opening the application.
A proper hierarchy of the UI is maintained.
2. Facilitate the ease of contacting the Travel agencies by providing proper
information (phone numbers, emails or any other communication sites) of the
agencies explicitly.
3. Application also provide the support for different modes of communication like
audio, video calling, text messaging and online meetings.
4. Each page of the spots’ information contains:
o Aesthetic Images of that place.
o List of Restaurants, Hotels, guides, travel agents and all other service
providers with their detailed information and pictures and charges.
o List of Facilities that these service providers provide.
5. Provide ease of deciding the best place according to the user's budget by providing
a “SORT-BY PRICE” feature.
6. Provide ease of deciding the best place according to the user's interests by
providing a “SORT-BY MOSTLY VISITED PLACES” feature.
7. Online Booking
8. Online payment
9. Provide Ease of Writing reviews/blogs on specific places (REVIEW feature and
blogposts)
10. A “MAP” feature like google maps to see the secure and quick ways to reach
somewhere.
11. Contain a list of Transports/Airlines and their drivers/pilots with their proper
information and reviews of people to help people decide more easily.
12. Contain weather and climate information of each place.
13. Contain all the information about types of entertainments that a spot offers.
14. Contain information about distances between different spots (so if anybody wants
to travel more and more places, he/she can decide easily keeping in view their time).
15. Contain information about the different agents of the agencies and their past data
and history of the past tours done by the travel agencies.
16. Display information about Petrol pumps and Toll Plazas on the way.
17. Screen reader support for blind users.
18. User can report if any service provider is scam.
19. User can share his/her own content about tourism in gallery photos and videos.
20. User can request rate the application and leave a review.
21. User can change the language. Different world wide recognized languages are
supported to maintain internationalization of the application.
22. Content displayed to the users is monitored to be updated and authentic.
FOR Service Providers:
The application does:
1. Provide facility to service providers like Travel agencies and hotels’ owners to add,
update, delete and edit their information and services on application.
2. Provide facility to Hotel owners to add their rooms’ and food’s specification and
charges and their contact details.
3. Allow Travel agencies to add their travel packages and charges and contact details.
4. Facilitate People to upload pictures/Videos to the GALLERY by “Add pictures”
feature.
5. Facilitate the service providers to check the list of people who want to travel.
6. Facilitate the Hotel managers to add information about neighborhood areas and
their views to increase their plus points.
7. Allow Hotel management to thoroughly update the availability or non-availability of
rooms so that no kind of inconvenience occurs for the travelers.
8. In a similar way, as does the hotel management is facilitated. All service providers
can add the desired services with relevant information at their own ease.
9. UI customization is provided to service providers. They can add different section
they want and skip they don’t like.
10. Service providers can offer special discounts to specific users if they want.

Both tourists and service providers can customize UI. They can change theme, look
and feel, and color scheme of the UI.

DOMAIN RULES

ID RULE CHANGEABILITY SOURCE

In case of not being Pakistan
If you are a foreigner and travelling registered with the Meteorological
to Pakistan you : Global Disaster Department
Alert and
 Should secure your passport
in a safe, waterproof place
Coordination https://www.s
 Must register with the System, you can martraveller.g
RULE Global Disaster Alert and contact your ov.au/destinat
1 associated travel
Coordination System to ions/asia/paki
receive alerts on major agency or other stan
disasters service providers to
 Must follow the advice of receive disaster
authorities. alerts.
 A little bit of editing
Pictures/Videos of places should not like Adding frames
RULE2 be fake at all, no filters allowed can be allowed, but
still filters are highly
unacceptable.
https://travel.s
tate.gov/conte
nt/travel/en/tr
Vary travel routes and timing,
RULE3 aveladvisories/
especially for routine trips.
traveladvisorie
s/pakistan-
travel-
advisory.html
https://travel.s
You must be aware of your tate.gov/conte
surroundings, especially around You can also contact nt/travel/en/tr
RULE4 public markets, restaurants, your associated travel aveladvisories/
government and military agents traveladvisorie
institutions. s/pakistan-
travel-
advisory.html
https://wwwnc.
Everyone above 12 should get fully cdc.gov/travel/
RULE5 vaccinated for COVID-19 before destinations/tr
travelling. aveler/none/pa
kistan
COVID-19
If you do, don’t forget
that it might start https://www.za
RULE6 You should Avoid travelling to drizzling at any time. meen.com/blog
northern areas in Monsoon. So, always keep an /hidden-
umbrella or a raincoat tourist-
in reach. destinations-
pakistan.html
https://www.za
RULE7 Don’t climb or try trekking Until you meen.com/blog
are an expert. /hidden-
tourist-
destinations-
pakistan.html
Don’t violate the general rules of
RULE8 any area (like if taking pictures is
 not allowed, don’t do that)

RULE9 Avoid unethical activities like

smoking in public places specially
When an application or registration
RULE of hotels to the app is received, The
10 controller should make enquiries and http://www.pha
only register those hotels fulfilling .org.pk/Docs/P
the criteria of the reasonable akistan%20Hot
standards of health, hygiene and els%20and%20
comfort. Restaurants%2
0Rules1977.pdf
The Controller, for the Record of http://www.pha
RULE registration and licenses for hotels .org.pk/Docs/P
11 and Restaurants: shall maintain akistan%20Hot
registers for hotels and els%20and%20
restaurants, containing particulars Restaurants%2
of their registration and licenses. 0Rules1977.pdf
In case of non-availability of rooms
RULE in hotels after someone has booked
12 that room, he must be informed
before-hand.
RULE The rooms in hotels must be cleaned
13 and well-maintained
RULE Places should be kept clean, no kind NO CHANGE
14 of wrapper, plastic and any other ACCEPTABLE.
garbage should be thrown in any
area

RISK ANALYSIS
SECURITY

Our system will deal with personal user data such as Name, ID card number,
address, nationality, bank account details, transactions details etc. The system
must ensure the ongoing safe and secure use of private data while minimizing
exposure risk. Our system must be secure enough to protect that data from any
unauthorized source/user. Also system must be ready to deal with unwanted
cyberattacks.

RELIABLITY
The system must be designed in such a way that in case of crash, it must be
recovered as soon as possible else it would cause great discomfort for the users.
The wait and uncertainly will cost us the confidence of our users.

MAINTENANCE

During maintenance of our system, the users must not be affected. It would cause
distress and users would want to move to alternatives. We need to address this
risk as well.

MARKET COMPETITON

When a software has a monopoly, everyone would be, kind of, forced to use that
one. But once it has competitors, users would have options. Then the software will
need to have something to attract users. As the competitors increase, it becomes
more and more difficult. In the inception phase, we need to address this factor.
Our software gives services for tour management as well as has features of a
social media application, such as posting and sharing blog, videos, pictures etc. This
distinguishes our product from that of our competitors.

Also we need to be up-dated with the changing technology and changing

requirement to remain in the competition and have a market value. Else we have
example of NOKIA! :’)

FEASIBILITY ANALYSIS
Organization
 We have a sufficient commitment to this project (including management, testers,
QA, and other external but involved parties) team.
 This is the largest project we have ever attempted.
 We will follow a blend of Scrum and XP as unified process modeling. That is a well-
defined process for software engineering. To capture and manage requirements, we
plan to have a public survey.

Funding/Financial
 We have the funding in place to complete project.
 We have allocated funds for training and mentoring.
  There are no budget limitations such that the system must be delivered at a fixed
cost or be subject to cancellation.
 We have accurate cost estimates.

People
 Enough people are available.
 We have appropriate skills and experience.
 We have worked together before.
 We believe the project can succeed.
 We have user representatives available for reviews.
 We have domain experts available for assistance.

Time
 The schedule is realistic.
 Functionality can be scope-managed to meet schedules.
 Delivery date is of intermediated criticality. We have a bit flexibility for it and can
manage our project well.
 We have the time to "do it right". We have proper time and everything scheduled
well. So, we can do a proper design and analysis. There is no need for rush to code.

Business Risks To top of page

 We have a proper plan for a situation if a competitor reaches the market first. We
have planned a very user-friendly interface, flexible contract, help & support,
customizations for the end users that our application have a greater business value
and in the short span of time no one can replace our application.
 We believe that our project funding can’t be jeopardized. Because we are
developing an application that cops up vast interests of the government and
intended to be a public service application. So, in any critical situation we can rely
on funding.
 The projected value of the system is greater than the projected cost. This project
costs a specific amount of time and money but our project have market value and
importance that can assist and effect the economy of our country.

Technical Risks To top of page

Scope risks
  An application that meets the requirements mentioned above in the document and
can assist to reduce the demand and supply gap in Pakistan is our measure of
success.
 Our initial requirements are fairly stable and well understood. Moreover we are
following a unified agile modeling process in which we will continually polish our
requirements on the basis of feedback and analysis.
 The project scope is firm to some extent, it can expand but for the time being it is
limited to be utilized all internationally but cover only one industry, tourism
industry of a country, Pakistan.
 The project development time scales are not rigid. They are short but flexible.

Technological risks

 We have planned to use kotlin, which is currently, one of the most popular the
language for android development.
 The transaction volumes in the requirements are reasonable. If the application
turns out to be successful the transaction volume may increase drastic
 We have transaction rate credible estimates, which are quite optimistic?
 The data volumes for application are reasonable. They can be held on currently
available systems.
 We have some unusual and challenging technical requirements that require the
project team to tackle problems with which they are unfamiliar. These include the
development of the auto monitoring system of information and content according to
the standard criteria and rules.
 Success is dependent on few relatively new products like monitoring system, but it
uses most of the existing services or technologies, existing proven hardware,
software, and techniques like audio video calling APIs and scrum, etc.
 There are external dependencies on interfaces to other systems, including audio,
video calling APIs, online meet APIs and auto email. Most of the required interfaces
already exists.
 There are some availability and security requirements which are extremely
inflexible. System must not be unavailable or unresponsive for a bit larger span of
time. i.e. few hours. System security is highly inflexible. It must be very rigid and
reliable.
 There may be users of the system that are inexperienced with the type of system
being developed. But a help & support feature can cop up with this problem.
 There is a minor chance of increased risk due to the size or complexity of the
application that may occur due to the increasing requirements.
  There is an important requirement for national language support. Also, some famous
languages must be supported by application to facilitate internationalization of
application.
 This system is possible to design, implement, and run. Unlike Some systems which
are just too huge or complex to ever work properly, it can operate smoothly.

External dependency risk

 This project don’t depend on any other in development project.

 The success is totally dependent on off the shelf products and externally-
developed components are not the major part of the application to play role in its
success.
 Success is not much dependent on the successful integration of development tools
(design tools, compilers, and so on), but have a smaller dependency on
implementation technologies (operating systems, databases, third party APIS, and
so on).

ACTORS, GOALS AND USE CASES

Actors
 Primary
o Tourist primary actor
o Service provider primary actor
o Support & Help staff primary actor
o Admins & moderators primary actor
 Secondary
o Online payment verification system secondary actor
o Audio calling API secondary actor
o Video calling API secondary actor
o Online Meet API secondary actor
o Emailing API secondary actor
o User authentication system secondary actor
 OFFSTAGE
o Government tax agency offstage actor
o National Command and Operation Center (NCOC) offstage actor
o National Tourism Coordination Board (NTCB) offstage actor
o Pakistan Tourism Development Corporation (PTDC) offstage actor
Goals
All users can view home page, view gallery and blogposts without login or signup.

Users can sign up for service provider or tourist category. Service provider’s signup a
contract while signing up.

Users can ask for help any time. A documentation and 24/7 online support is provided to
users.

Service providers can add their services, modify them, offer special discounts to
particular users, and communicate with users via audio, video calls, emails and online
meeting. They can schedule meetings ahead of time.

Service providers can send auto generated emails to users. They can share photos and
videos in gallery and post in blogposts section.

Tourists can sign up and login to the system to avail different service. They can explore
the services provided, book them, rate them, leave a feedback, cancel the booking, pay
online, and communicate with the service providers at comfort of their couch.

Tourists can view pictures and videos, read blog posts and share their own content too.

Admins and moderators provide online help and supports to all sort of users. They validate
and monitor the pictures, videos and all sort of content shared on the application.

Users can reset and recover their passwords and their accounts in case of any failure.

Users can personalize appearance, customize look and feel, and change the language
according to their own ease.

Screen reader facility is provided for blind users and color theme is used keeping in view
the ease of color blind users too.

Third party APIs are used to provide services like audio and video calling, scheduling and
organizing online meetings, send auto generated emails and online payment authorizations.

Know-how section must contain all worth mentioning information about a particular spot or
service. It must be maintained well and updated regularly.

USE CASES
Black box use cases:

 UC1 : Explore application without login, signup

 UC2 : Signup & Login to the application
 UC3 : Manage pictures, videos or blogposts
  UC4 : Manage services
 UC5 : Manage online payments
 UC6 : Manage bookings
 UC7 : Manage tourists and service providers’ communication and interactions
 UC8 : Manage and facilitate searches
 UC9 : Manage home page
 UC10 : Manage help & support
 UC11 : Manage content monitoring and control
 UC12 : Manage UI and customization
 UC13 : Manage service provider contracts
 UC14 : Manage know-how sections
 UC15 : Manage hierarchy of the application UI

Fully dressed format of 10-20% use cases

Choosing use cases with high risk, market value and architectural significance.

 UC2: Sign up & login to the application

 UC3: Manage pictures, videos and blogposts
 UC4: Manage services

Use Case UC2: Sign up & login to the application

Scope: “Let’s Xplore Pakistan” application
Level: User goal
Primary Actor: End user
Stake Holders and Interests:
Tourists have major concern with signup and login. They have to sign up and login for successful
utilization of services, communication with service providers and sharing their content in gallery and
blogposts.

Service providers also have major concern with sign up and login. They have to sign up successfully to
offer their services after signing the contract.

Admins & moderators monitor the contract signing process of service providers at the time of sign up.
They negotiate with service providers about contract if service providers have any reservations.

User authentication system verifies the user is not a scammer via captcha and password
authentications. If a user is found suspicious it notify to admins & moderators panel.

Pre Conditions:
For login, user must have signed up before.
For sign up, user must be an eligible person having complete knowledge of his role. Either he wants to
sign up as tourists or service provider.

User must agree to provide all required information and sign contract in case if he is a service provider.

Post Conditions (success guarantee):

User sign up successfully as tourist or service provider and be able to complete his profile.

User login successfully he already have an account.

Main Success Scenario (Basic Flow):

User opens the application. The home page is presented to the user, where he can explore different
features presented to tourists and service providers view gallery photos and videos and read blogposts.

If user is new to application and decides to continue, he chooses to sign up.

To sign up users are required to provide an email, password, username and specify whether he is tourist
or service provider.

If user is a tourist he can sign up successfully by specifying a unique email id, username and valid
password.

If user is a service provider a contact is presented to the user. User have to agree with it and sign the
agreement to continue.

If user signs the agreement, he can sign up by specifying a unique email id, username and password.

Before sign up, captcha verification is carried out to prevent cyber scams.

After sign up, the user is instructed to complete his profile.

If user already have an account, he can log in by providing password and email or username.

Extensions (Alternative Flow):

2a: User enters email that is already in use.
If user enters an email that is already in use, generate an error message.

Ask user to reenter the email or login to the existing account

If user reenters an email validate it and allow sign up if email is unique else generate an error message
again.

If user wants to login to existing account direct him to login page.

2b: User enters a username that is already in use

If user enters a username that is already in use generate an error message.

Ask user to login with that username if user have an existing account. Direct him to login page if he
selects to login.
Otherwise suggest some suitable available usernames to user. And ask to reenter username.

Revalidate the username, generate error if invalid. Allow signup if unique username is entered.

2c: User enters a weak password

If user enters a week password suggest him a strong password. Or suggest him the way to make a strong
password.

If user enters a strong password or use a suggested password allow sign up else generate error.

2d: Service provider don’t agree with contract and wants to negotiate
If a service provider don’t agree with contract he can call for help. Admins and moderators negotiate
with them to resolve their concerns.

They can provide customizations to service provider in contract. If they agree upon a contract, service
provider sign the contract and sign up the application.

2e: user forgets password

If user forgets his password, he can request for password reset.

On reset request, an auto generated email is sent to user to reset the password.

User can go to that link and reset password. If once link is opened it expires immediately as it is closed.
User can’t again use that link to reset password.

2f: user enters wrong username password

If user enters wrong username or password generate an error message.

Ask user to reset password or request recovery of account if user forgets his username.

Ask user to enter valid email registered with the application.

If user specifies a registered email, send an auto generated email for account recover or password reset.

Special Requirements:
Special features for blind user and illiterate users.

User authentication carried out before log in and sign up.

Multi lingual support for internationalization of the application.

Provide online help & support system.

Design UI by color theme that is supportive for color blind users.

Technology and data variations list:

Screen reader support

Captcha verification
Emails auto generation system

Frequency of occurrence:
Every time a new user come to the application sign up is required if he wants to continue with it.

Existing users are required to sign up if they haven’t logged in before, logged out or if they are using
from new device.

Open Issues:
What are parameters for strong password?

What type of customizations can be offered in contract?

What points of contract are negotiable?

What are the necessary things to be agreed upon in contract?

Use Case UC3: Manage pictures, videos and blogposts

Scope: “Let’s Xplore Pakistan” application
Level: User goal
Primary Actor: end users
Stake Holders and Interests:
Tourists have major concern with pictures, videos and blogposts. They can view photos, videos and blog
posts without login and can share these too after logging in.

Service providers can also view photos, videos and blog posts without login and share their content after
logging in.

Admins & moderators monitor and control the content being shared. They allow only relevant content
to be shared. They also monitor modification and deletion request for the content shared. Only the
owner of content can request for deletion. Every user can request for modification of content. But their
request is processes by the admins with the consent of content owner.

Pre Conditions:
User must be verified and logged in before sharing photos, videos via gallery or post in blogposts.

Post Conditions (success guarantee):

User must be able to view pictures, videos and blogposts. User can also share his own content if he log
in to the application.
Main Success Scenario (Basic Flow):
User opens the application. The home page is presented to the user, where he can explore different
features presented to tourists and service providers view gallery photos and videos and read blogposts.

If user is new to application he can only view photos and videos in gallery and read blog posts. He can’t
post new blog or share his own content.

If user is already have an account he can login to application to share his content.

If user wants to share his content, he can generate a request to share his content. He must specify his
content, a detailed description, and copy rights of the content while requesting to share it.

Admins process that request based on the content quality, relevancy and authenticity they decide either
to accept or deny the request.

If admins approve the content it is shared to relevant section with all copy rights reserved to the owner
of content.

Other users can view and request for modifications in that content. Only owner of content can request
deletion of the content.

If modification is requested content owner is requested to permits the modification of the content.

Extensions (Alternative Flow):

3a. content shared is not relevant or appropriate
If user request to share any content which is not appropriate or not relevant or tourism request is
denied.

An auto generated email is sent to user, explaining the reason of denial.

3b. content is appropriate but source is not verified

If user share an appropriate and relevant but unverified content clarification is demanded from user.

Unverified content can be any content whose source is not mentioned or authentic. If copy rights are
not mentioned clearly content lies under unverified too.

User is informed via email to provide proper information regarding content.

If user provide required information in 7 days content is published.

If user doesn’t respond back request is denied.

3c. content modification is not allowed by owner

If someone other than content owner requests to improve or modify published content he may request
for it.

On modification request, the owner of content is notified for permission. If owner allows within 7 days
modification is validated and published.
If owner don’t allow modification is rejected.

If owner don’t respond in 7 days modification is validated and published if valid.

3d. content becomes outdated

If any content published on the site becomes outdated, content owner is notified to update it via email.

If owner request an update in 7 days, update is validated and published if valid.

If owner don’t respond back in 7 days outdated content is removed from the application.

Special Requirements:
Special features for blind user and illiterate users.

Content validation carried out before publishing the content and modifications.

Multi lingual support for internationalization of the application.

Provide online help & support system.

Design UI by color theme that is supportive for color blind users.

Content must be reviewed to filter out outdated content regularly.

Technology and data variations list:

Screen reader support

Emails auto generation system

Support sharing of content from and to well know social media platforms like Facebook, Instagram and
linkden.

Auto monitoring system for out dated content alert.

Content plagiarism and copyright monitoring system.

Frequency of occurrence:
Every time a new user come to the application he/she must be able to view gallery and blogposts
content.

If user have signed up is, he/she must be able to share content in gallery and blogposts.

Open Issues:
What are parameters for testing plagiarism in content?

What type of copy right and licensing is demanded for content publication?

Is there any content which is intended to be private for signed up users only?

What are the parameters for any content to be outdated?

Which type of social media content sharing support can be provided?

Use Case UC4: Manage Services

Scope: “Let’s Xplore Pakistan” application
Level: User goal
Primary Actor: Service Providers
Stake Holders and Interests:
Tourists have major concern with services. They can explore and avail the services provided on the
platform.

Service providers can also have direct impact in management of services. They are providers and source
of these services and they can offer services. And they can also apply all crud operations on the services
provided via this platform.

Admins & moderators monitor and control the services provided, their authenticity and strive to
prevent from being used for scams. They allow only relevant and authentic services to be offered and
monitor the system for a clear dealing of demand and supply of services.

Online payment verification system interact with the system to provide a fast and secure system for
online payments management.

Audio, Video calling, online Meet, Emailing API helps in the communication and connection building of
the service providers and users of these services.

Government tax agency decides the tax percentages for different fields of business dealing. These taxes
are enforced on all the dealings carried out via our application.

Pre Conditions:
Service provider must have logged in to the system and authenticated.

Service provider provide authentic services that are verified and trusted for being offered on
application.

Service provider provide relevant services which are related and beneficial for promotion of tourism
industry.

Service providers intend to do a clear business and don’t work in a way that is against business rules or
harmful for compotators. For example, no one is trying to exploit system and generate monopoly.

Post Conditions (success guarantee):

Service providers offer services successful and these services are presented to tourists in a hierarchy of
places and services.

Users can visit them, book them, pay for them, and connect with service providers.
Service providers can perform crud operations for all of the services provided by them.

Main Success Scenario (Basic Flow):

Services providers login to the application where they are authenticated. If verified user they can log in
to the application.

Logged in service providers can offer their services. To offer a service they must specify the category and
location of service at first.

They must provide the mandatory information for the service they are offering like copyright, price,
type, contact information and special discounts if any, etc.

They can also add different sections to the service as per their requirements.

When user provides complete information, he can request for approval.

Admin & moderators panel look if there is any flaw or fallacy in the information provided. If there is any
service provider is updated about that and asked for correction within 7 days.

If the user respond back in 7 days information is revalidated and published if authenticated else service
provider is notified again and so on.

To publish, a page is generated with the all information of user interest relevant to the service displayed
on it.

Service provider can edit, update and delete the information provided by him/her.

Each edit and update is verified before publication.

Service are published in a hierarchy of places at first, all the provinces are separate categories, in a
specific province at first are the cities of that province and tourism spots in a particular city are
presented.

For each tourism spot hotels, restaurants, guides travel agents are displayed as distinct categories.

Extensions (Alternative Flow):

4a. Service is identified to be a scam
If any service provided by a particular user is identified to be a scam or misleading content, information
is discarded, publication is denied and user is marked as suspicious.

Service provider is issued a warning message to abide by the rules and regulations of the application and
contract.

If any service provider attempts to exploit the system twice, he/she is marked as suspicious and all other
services offered by that service provider are verified and re authenticated.

On third such attempts, service provider is black listed and his account is banned permanently.

4b. service is irrelevant.

Service provider add or offers a service that is not relevant to tourism and is not of the interest of
application scope.

Content publication is denied and service provider is notified with terms and conditions and relevancy
parameters of the service via email.

4c. information provided is ambiguous.

If the information relevant to a service is ambiguous or in complete publication is paused.

Service provider is notified to modify the information, according to required parameters.

If service provider respond back in 7 days information and re validated to be published or denied.

If user doesn’t respond back in 7 days information is discarded and publication is denied permanently.

4d. edit or update is unacceptable.

If a service is published and service provider makes an update or edit later that is irrelevant, misleading,
or scam edit or update information is discarded, publication is denied.

Service provider is issued a warning message to abide by the rules and regulations of the application and
contract in edits and updates too.

If any service provider attempts to exploit the system twice, he/she is marked as suspicious and all other
services offered by that service provider are verified and re authenticated.

On third such attempts, service provider is black listed and his account is banned permanently.

Special Requirements:
Special features for blind user and illiterate users.

Information validation carried out before publishing service and modifications.

Multi lingual support for internationalization of the application.

Provide online help & support system.

Design UI by color theme that is supportive for color blind users.

Technology and data variations list:

Screen reader support

Emails auto generation system

Support sharing of service from and to well know social media platforms like Facebook, Instagram and
linkden.

Auto monitoring of services for identifying scams and misleading content.

Auto generation of distinct and interactive page for each service offered and accepted for publication.
Support for different and trending communication Medias like audio video calls and online meeting API
etc.

Frequency of occurrence:
Every time a service provider comes to application he/she can add, delete modify and update the
services on application.

Open Issues:
What are parameters for testing information for a service to be complete and correct? What type of
modifications and updated are allowed?

What type of copy right and licensing is demanded for services?

What are the parameters for any service to be relevant?

Which type of social media sharing support can be provided?

What type of information is treated as ambiguous?

What are parameters to blacklist a service provider form application?

What are parameters to ban the account of a service provider?

What type of communication facilities should be provided?

Glossary
 Vision: An executive summary that briefly describes the project
 Features List: Provides a succinct summary of the functionality, irrespective of the
use case view
 SORT-BY PRICE: A list format that shows elements in ascending or descending
order with respect to their price
 FRUPS+: Functionality, Reliability, Usability, Performance, Supportability
 +: Requirements Other than FRUPS
 Xplore: Explore
 Sign up: Create Account
 Login: Open an already created and verified account
 Account Authentication: verification of user credentials from database
 Actors: The users that interact with the application
 Gallery: Containing Pictures and Videos
 Blogposts: A writing published on a blog
 StakeHolder: A person associated with the application, can either affect or
affected by the application
 Tourist: A person who wants to travel a place for pleasure
 Tourist guide: A person that guides/helps tourists
 Service providers: The people or systems that provide services, in our case they
are the tourist guides, hotel managers, airline management, travel agencies etc
 Know-how: Expertise knowledge
 NCOC: National Command and Operation Center
 NTCB: National Tourism Coordination Board
 PTDC: Pakistan Tourism Development Corporation
 Feedback: The reaction/ reviews about our app
 Contract: A promise signed after setting some rules
 Fully dressed format: In which all steps are written in detail
 Agreement: something like a contract
 Artifacts: Documents that are related to the project
 Domain rules: Generic rules related to the application
 Risks: Factors that can cause loss to the application
 Feasibility: The practical extent of how successful the project can be.

______________
 PA CK AGE D I AGR A M S

EX PL OR E PA K I ST A N

M anage hom e page L ogin/Sign Up M anage gallery and blogposts M anage Ser vices

Com m unications and

M anaging paym ents O nline Ser vices I nteraction

M anage and facilit ate Content m onitor ing and M anage U I and Custom isation
M anage help and suppor t control m anagem ent
searches

M anage application U I hierarchy

M anage Ser vice provider contracts M anage know - how section

M anage hom e page L ogin/Sign Up

L ogin
Sign up L ogin/Sign up as Tour ist

L ogin/Sign up as Ser vice Provider

Pictures D isplay
V iew Blogposts

L ogin/Sign up as A dm in

V iew roles
 M anage Ser vices
M anage Gallery and BlogPosts

A dd N ew Ser vices
Post Picture, V ideos

V iew Picture, V ideos D elete a ser vice

W r ite R eview s
Update a ser vice

R ead R eview s R eview a ser vice

M anaging Paym ents O nline Ser vices

Cash D eposit
O nline Paym ent

Cash R etur n
O nline booking of
hotels
Validit y Check for
full paym ent
O nline Booking of
Calculating dues transpor ts

Com m unications and

M anage and facilit ate searches
I nteraction

A udio Calling Sor t by M ostly

V isited

V ideo Calling Sor t by charges

O nline Chatbox Sor t by Feasibilit y

Em ailing Sor t by Features

Manage Help and Support
Content m onitor ing and control m anagem ent

M anaging FA Q 's Content Validation

M anaging any
er rors in
com m unication Rules A uthentication
m ethods
Providing video
tutor ial for how to use
the app K eeping count of
attem pts
H elp Users in clearly
identifying the use of
ser vices R elevence check

M anage U I and Custom ization

M anage ser vice provider contracts

Change T hem e
Contract duration Check

Change Background

A uthenticate Ser vice

Change Font st yle providers infor m ation

M anage app view

Update Contracts

M anage K now - how Section M anage A pplication U I hierarchy

M anage weather D isplay Road M ap H ierarchy of hotels

infor m ation updation

H ierarchy of cities,areas
I nfor m users about D isplay infor m ation of
dist ances guides
H ierarchy of T raspor ts

D isplay
infor m ation about toll D isplay I nfor m ation H ierarchy of ser vices
plazas about T ranspor ts and
airlines and their st aff
 BU SI N ESS LEV EL U SE CA SE D I AGR A M

System

Tourist Explore O nline paym ent ver ification

application system
w ithout login,
signup

Signup & L ogin

to the application

M anage pictures, A udio calling A PI

videos or blogposts

Ser vice provider M anage or use

ser vices

M anage and do V ideo calling A PI

online paym ents
Bookings

Tour ists and ser vice

providers?
com m unication and
O nline M eet A PI
interaction
M anagem ent

M anage and
facilit ate searches

M anage Em ailing A PI
hom e page
A dm ins & m oderators
M anage help
& suppor t
M anage content
m onitor ing and
control
User authentication system
M anage U I and
custom ization

M anage and sign

ser vice provider
contracts
M anage
know - how
Suppor t & H elp st aff sections

M anage hierarchy of
the application U I
 BU SI N ESS LEV EL U SE CA SE D I AGR A M

USER AUTHENTICATION
SYSTEM

Login & sign

VISITOR

manage
homepage ONLINE PAYMENT
AUTHENTICATION
Explore
application
without signu[
or login

Avail services

Manage
gallery and
TOURIST blogposts

Manage and
sign contract

Negotaite on
contract

ServiceProvider
Manage Ui &
Customization

AUDIO VIDEO CALLING API

Customiziing
the contract

Manage ONLINE MEET API

services

ADMINS PANEL

manage
communication
and
interactions

manage & EMAILING API

facilitate
searches

content
monitoring Manage GOOGLE MAP API
and control hierarchy of
managment the
application UI

Manage help manage know

& support how sections

WEATHER FORCAST API

 A N A LY SI S LEV EL U SE CA SE D I AGR A M

USER AUTHENTICATION
SYSTEM
login as
admin <<extend>>

login or Login & sign

signup as
VISITOR manage
tourisr login or
homepage
signup as
serviceprovider

ONLINE PAYMENT
AUTHENTICATION
Explore <<include>>
application <<include>>
without signu[
or login
View gallary
Avail services phots,videos
and blogposts

Manage
gallery and <<include>>
blogposts
TOURIST NOTE: Arrows without text
shows generalization.

Negotaite on
<<extend>>
contract

Manage and
sign contract
<<extend>>
Customiziing
the contract

Change color
ServiceProvider theme
Manage Ui & rearrange
Customization sections

AUDIO VIDEO CALLING API

Add new
change mode section
change font i.e to dark or
or light
background

add a service
edit or update
Manage a service ONLINE MEET API
services

ADMINS PANEL
delete a
service

manage
communication emailing manage &
and facilitate
interactions searches
EMAILING API

online oline meets

audio & video chatbox
calling

sort by rating
content sort by mostly
monitoring Manage visited GOOGLE MAP API
and control hierarchy of
managment the
application UI

sort by price

Manage help manage know

& support how sections

WEATHER FORCAST API

STATE CHART FOR USER