Scribd
Upload
22 views3 pages

Project Report Hanje Shu City Guide Over Android 1 3

The document outlines the functional and non-functional requirements for a city guide mobile application. It details requirements like showing maps, points of interest, events, reviews, communication between users, and making tour plans. It prioritizes the requirements and specifies they aim to make the prototype flexible, have a usable interface, and combine existing technologies.

Uploaded by

Saideep Ashala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
22 views3 pages

Project Report Hanje Shu City Guide Over Android 1 3

The document outlines the functional and non-functional requirements for a city guide mobile application. It details requirements like showing maps, points of interest, events, reviews, communication between users, and making tour plans. It prioritizes the requirements and specifies they aim to make the prototype flexible, have a usable interface, and combine existing technologies.

Uploaded by

Saideep Ashala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

City Guide Over Android

4.2 Requirement Specification


After exploring existing mobile city guides and scenarios, I list the functionalities in
different priorities. The priorities are given according to the importance of functions
for a city guide. For example, the function of showing map is very important for a
city guide. The priorities are divided into three different levels: High (H), Medium
(M), and Low (L). H is considered the most important for a city guide and
implemented firstly, M is less important and implemented after H, L is the least
important and considered to implement after the high and medium. Normally, city
guide should have basic functions: showing map and showing points of interest
(POIs) on map, providing some information about sights or events (e.g. when the
museum is open). In addition to them, we can add telephone function, the function of
adding review, the function of making tour plan, the function of event reminder and
so on. As well, I explore implementation of functionalities as many as possible based
on the features of powerful Android platform since investigating realization of a
tailorable City Guide application on the Android platform is the main purpose in the
project.

4.2.1 Functional Requirements


MAP
ID Requirement Priority
1 The city guide can show map of a city. H
2 The map can be zoomed in and out H
3 Users can move around the map H
4 The city guide can show user’s current H
position on the map
5 The city guide can show the route between M
different locations on the map
6 The city guide can see other users’ positions L
in the same group on the map
7 The map can show points of interest (POIs) H
8 The map only shows the points of interest M
users are interested in

Table 4-1: Map in Functional Requirements

24
City Guide Over Android

Information Retrieval
ID Requirement Priority
9 The city guide can retrieve information of H
points of interest
10 The city guide can retrieve information of M
events, which will happen right now.
11 The city guide can retrieve information M
about reviews of points of interest
12 Users can select what kind of POIs to show M
on map (i.e. different classifications. e.g.
hotels, museums, restaurants events, and so
on).

Table 4-2: Information Retrieval in Functional Requirements

Communication
ID Requirement Priority
13 The city guide can support communication M
between users in the same group through
telephone or short message.

Table 4-3: Communication in Functional Requirements

Review
ID Requirement Priority
14 Users can add review about points of interest. M
Table 4-4: Review in Functional Requirements

Reminder
ID Requirement Priority
15 The city guide can support event reminder H
like lunch time

Table 4-5: Reminder in Functional Requirements

Plan tour
ID Requirement Priority
16 Users can make a tour plan. (i.e. users can M
choose any POI and add it into their tour
plan.)
17 Share tour plan with other users L
Table 4-6: Plan Tour in Functional Requirements

25
City Guide Over Android

4.2.2 Non-Functional Requirements


According to the goal of the project, the resulting prototype should be extendible,
tailorable, and explore and put existing innovational technologies as many as
possible as building blocks in the project. And user interface should be readable,
easy to understand, and easy to operate.

ID Requirement Priority
18 The resulting prototype should be flexible H
(extendible and tailorable).
19 The user interface should be usable, easy to H
understand and operate.
20 The prototype should combine existing H
innovational technologies like Google Map
as many as possible.

Table 4-7: Non-Functional Requirements

26

You might also like