Professional Documents
Culture Documents
Srs Example 2010 Group2 PDF
Srs Example 2010 Group2 PDF
Specification
Amazing Lunch Indicator
Table of Contents
1. Introduction ............................................................................................................................................... 1
1.1 Purpose................................................................................................................................................ 1
1.2 Scope ................................................................................................................................................... 1
1.3 Definitions, acronyms, and abbreviations ........................................................................................... 1
1.4 References ........................................................................................................................................... 2
2. Overall description .................................................................................................................................... 4
2.1 Product perspective ............................................................................................................................. 4
2.2 Product functions ................................................................................................................................ 4
2.3 User characteristics ............................................................................................................................. 5
2.4 Constraints .......................................................................................................................................... 5
2.5 Assumptions and dependencies .......................................................................................................... 5
2.6 Apportioning of requirements ............................................................................................................. 6
3. Specific requirements................................................................................................................................ 7
3.1.1 User interfaces ............................................................................................................................. 7
3.1.2 Hardware interfaces ..................................................................................................................... 8
3.1.3 Software interfaces ....................................................................................................................... 8
3.1.4 Communications interfaces .......................................................................................................... 9
3.2 Functional requirements ...................................................................................................................... 9
3.2.1 User Class 1 - The User ............................................................................................................... 9
3.2.2 User Class 2 - Restaurant Owner ............................................................................................... 14
3.2.3 User Class 3 - Administrator ...................................................................................................... 18
3.3 Performance requirements ................................................................................................................ 21
3.4 Design constraints ............................................................................................................................. 23
3.5 Software system attributes ................................................................................................................ 23
4. Prioritization and Release Plan ............................................................................................................... 27
4.1 Choice of prioritization method ........................................................................................................ 27
Appendix I: Selection for Cost-Value Approach ........................................................................................ 29
Appendix II: Prioritization Result of 10 selected Requirements Using Cost-Value Approach .................. 32
Appendix III: Five-Way Priority Scheme ................................................................................................... 36
Appendix IV: Release Plan ......................................................................................................................... 47
Appendix V: I-star ...................................................................................................................................... 55
1. Introduction
This section gives a scope description and overview of everything included in this SRS document. Also,
the purpose for this document is described and a list of abbreviations and definitions is provided.
1.1 Purpose
The purpose of this document is to give a detailed description of the requirements for the Amazing
Lunch Indicator (ALI) software. It will illustrate the purpose and complete declaration for the
development of system. It will also explain system constraints, interface and interactions with other
external applications. This document is primarily intended to be proposed to a customer for its approval
and a reference for developing the first version of the system for the development team.
1.2 Scope
The Amazing Lunch Indicator is a GPS-based mobile application which helps people to find the closest
restaurants based on the users current position and other specification like price, restaurant type, dish and
more. The application should be free to download from either a mobile phone application store or similar
services.
Restaurant owners can provide their restaurant information using the web-portal. This information will act
as the bases for the search results displayed to the user. An administrator also uses the web-portal in order
to administer the system and keep the information accurate. The administrator can, for instance, verify
restaurant owners and manage user information.
Furthermore, the software needs both Internet and GPS connection to fetch and display results. All system
information is maintained in a database, which is located on a web-server. The software also interacts
with the GPS-Navigator software which is required to be an already installed application on the users
mobile phone. By using the GPS-Navigator, users can view desired restaurants on a map and be navigated
to them. The application also has the capability of representing both summary and detailed information
about the restaurants.
Term
Definition
User
Admin/Administrator System administrator who is given specific permission for managing and
controlling the system
Restaurant Owner
Someone who has a restaurant and wants his restaurant to be a part the
application
Web-Portal
and admin
GPS
GPS-Navigator
Application Store
Stakeholder
Any person who has interaction with the system who is not a developer.
DESC
Description
RAT
Rational
DEP
Dependency
TAG
GIST
SCALE
METER
MUST
PLAN
WISH
DEFINED
1.4 References
[1] IEEE Software Engineering Standards Committee, IEEE Std 830-1998, IEEE Recommended
Practice for Software Requirements Specifications, October 20, 1998.
[2] Feldt R,re_lecture5b_100914, unpublished.
[3] Davis M A, Just Enough Requirements Management: Where Software Development Meets
Marketing, New York, Dorset House Publishing, 2005.
[4] Karlsson J, A Cost-Value Approach for Prioritizing Requirements, Norges TekniskNaturvitenskapelige Uni. 1997
1.5 Overview
The remainder of this document includes three chapters and appendixes. The second one provides an
overview of the system functionality and system interaction with other systems. This chapter also
introduces different types of stakeholders and their interaction with the system. Further, the chapter also
mentions the system constraints and assumptions about the product.
The third chapter provides the requirements specification in detailed terms and a description of the
different system interfaces. Different specification techniques are used in order to specify the
requirements more precisely for different audiences.
The fourth chapter deals with the prioritization of the requirements. It includes a motivation for the
chosen prioritization methods and discusses why other alternatives were not chosen.
The Appendixes in the end of the document include the all results of the requirement prioritization and a
release plan based on them.
2. Overall description
This section will give an overview of the whole system. The system will be explained in its context to
show how the system interacts with other systems and introduce the basic functionality of it. It will also
describe what type of stakeholders that will use the system and what functionality is available for each
type. At last, the constraints and assumptions for the system will be presented.
map view will show each restaurant location as a pin on the map as well as the users own location. In
both views the users will be able to either select a restaurant as target destination or get information how
to get there, or view the information of a specific restaurant.
The web portal will provide functionality to manage the system and the restaurant information. It will also
provide information about the system, for example show when there is a new update.
2.4 Constraints
The mobile application is constrained by the system interface to the GPS navigation system within the
mobile phone. Since there are multiple system and multiple GPS manufacturers, the interface will most
likely not be the same for every one of them. Also, there may be a difference between what navigation
features each of them provide.
The Internet connection is also a constraint for the application. Since the application fetches data from the
database over the Internet, it is crucial that there is an Internet connection for the application to function.
Both the web portal and the mobile application will be constrained by the capacity of the database. Since
the database is shared between both application it may be forced to queue incoming requests and therefor
increase the time it takes to fetch data.
would mean the integration with the GPS would have different requirements than what is stated in this
specification.
3. Specific requirements
This section contains all of the functional and quality requirements of the system. It gives a detailed
description of the system and all its features.
In Figure 5, the list view for the results is shown. When a user searches by price, this view should be the
default one. The sorting header allows the user to sort the results according to price, restaurant name,
distance, restaurant type and specific dish. Each result item includes information about the restaurants, a
link to the restaurants web-page and an information link, which provides a more detailed description of
the restaurant. There is also a filtering option, where the user can choose to filter the results by increasing
or decreasing the price or distance range, see Figure 7.
In the map view each restaurant is represented by a pin, see Figure 6. Next to every pin there is an
information link which provides a more detailed description of the restaurant, as mentioned for the list
view. The same filtering option, as for the list view, is included in the map view.
The restaurant owners and administrators interact with the system through a web-portal, see Figure 8. A
restaurant owner should be able to register on the web-portal in order to log in and manage the restaurant
information. An administrator should also be able to log in to the web-portal where he/she can administer
the system by for instance editing restaurant or user information.
about where the user is located and the visual representation of it, and with the database in order to get the
information about the restaurants, see Figure 1. The communication between the database and the web
portal consists of operation concerning both reading and modifying the data, while the communication
between the database and the mobile application consists of only reading operations.
3.1.4 Communications interfaces
The communication between the different parts of the system is important since they depend on each
other. However, in what way the communication is achieved is not important for the system and is
therefore handled by the underlying operating systems for both the mobile application and the web portal.
Search results can be viewed on a map. On the map, the relevant and closest restaurants according
to the users position are shown.
A specific pin will represent a specific restaurant location. On each pin there should be an
information link.
There should be maximally 100 results displayed. The map view should have a default zoom.
The map view should include a button that, when selected, should display different filtering
options in a filtering menu.
10
Search results can be viewed in a list. Each element in the list represents a specific restaurant.
Each element should include the restaurant name, telephone number, type of food, distance
according to the users position, average price, a short two-line description, a link to the
restaurants web-page and an information link.
There should be maximally 100 results displayed. If the result contains more restaurants than
what can be displayed on the screen at one time, the user should be able to scroll through them.
When searching by price the restaurants should be sorted according to the following order:
1. average price
2. distance
3. restaurant type
4. specific dish
When searching by a search option, other than price, the restaurants should be sorted according to
the following order:
1. distance
2. average price
3. restaurant type
4. specific dish
The list view should include a header with different selectable sorting options.
The list view should include a button that, when selected, should display different filtering
options in a filtering menu.
DESC: A user should be able to select a restaurant type in a given list as input. The result is displayed in a
map view by default.
RAT: In order for a user to search by restaurant type.
DEP: FR7
3.2.1.16 Functional requirement 1.16
ID: FR16
TITLE: Mobile application - Search by specific dish
DESC: A user should be able to select a specific dish in a given list as input. The result is displayed in a
map view by default.
RAT: In order for a user to search by specific dish.
DEP: FR7
3.2.1.17 Functional requirement 1.17
ID: FR17
TITLE: Mobile application - Free-text search
DESC: A user should be able to conduct a search by providing either restaurant name, restaurant
description, restaurant address, restaurant type or restaurant menu in the free-text search field. The result
is displayed in a map view by default.
RAT: In order for a user to search through the free-text search.
DEP: FR7
3.2.1.18 Functional requirement 1.18
ID: FR18
TITLE: Mobile application - No match found
DESC: If no match is found the user should be informed but kept on the search page in order to get the
possibility to conduct a new search right away.
RAT: In order for user to conduct a new search if no match is found.
DEP: FR5
3.2.1.19 Functional requirement 1.19
ID: FR19
TITLE: Mobile application - Sorting results
DESC: When viewing the results in a list, a user should be able to sort the results according to price,
distance, restaurant type, specific dish or restaurant name.
When sorting by restaurant name, specific dish or restaurant type the results should be ordered
alphabetically.
When sorting by price the results should be ordered from cheapest to most expensive.
When sorting by distance the results should be ordered from closets to furthest distance according
to the users position.
13
When the sort button for a specific search option is clicked, then the order should be reversed and ordered
in a descending matter. If the sort button is clicked again the order of the results should be reversed.
RAT: In order for a user to sort results in a list.
DEP: FR8
3.2.1.20 Functional requirement 1.20
ID: FR20
TITLE: Mobile application - Filtering results
DESC: When viewing the results in a list or a map, a user should be able to filter the results in a filtering
menu. The filtering options include:
When filtering the results, only the existing results shall be affected and a new search query should not be
sent.
RAT: In order for a user to filter results in a list or a map.
DEP: FR7, FR8
3.2.1.21 Functional requirement 1.21
ID: FR21
TITLE: Mobile application - Profile page
DESC: On the mobile application, a user should have a profile page. On the profile page a user can edit
his/her information, which includes the password, e-mail address and phone number. A user should also
be able to choose what language the mobile application should be set to. The different language choices
are Swedish, English, Spanish and French.
RAT: In order for a user to have a profile page on the mobile application.
DEP: FR1
3.2.2 User Class 2 - Restaurant Owner
3.2.2.1 Functional requirement 2.1
ID: FR22
Feature: Create an account
In order to create an account
A restaurant owner
Should register on the web-portal
Scenario: Required information for registration
Given the restaurant owner wants to create an account
And the restaurant owner does not have an account
14
15
17
21
22
SCALE: If a restaurant owner tries to log in to the web portal with a non-existing account then the
restaurant owner should not be logged in. The restaurant owner should be notified about log-in failure.
METER: 1000 attempts to log-in with a non-existing user account during testing.
MUST: 100% of the time.
ID: QR14
TAG: AdminLoginAccountSecurity
GIST: Security of accounts.
SCALE: If an admin tries to log in to the web portal with a non-existing account then the admin should
not be logged in. The admin should be notified about log-in failure.
METER: 1000 attempts to log-in with a non-existing user account during testing.
MUST: 100% of the time.
ID: QR15
TAG: RestaurantOwnerAccountSecurity
GIST: Security of restaurant owners accounts.
SCALE: A restaurant owner and IP address should not be able to log-in for a certain time period after
three times of failed log-in attempts.
METER: 1000 attempts to log-in during the lock period after user account has been locked because of
failed log-in attempts of three times.
MUST: The locking period should be half an hour, and during that period the log-in function is disabled.
ID: QR16
TAG: AdminAccountSecurity
GIST: Security of admin accounts.
SCALE: An admin and IP address should not be able to log-in to the web portal for a certain time period
after three times of failed log-in attempts.
METER: 1000 attempts to log-in during the lock period after user account has been locked because of
failed log-in attempts of three times.
MUST: The locking period should be half an hour, and during that period the log-in function is disabled.
ID: QR17
TAG: UserCreateAccountSecurity
GIST: The security of creating account for users of the system.
SCALE: If a user wants to create an account and the desired user name is occupied, the user should be
asked to choose a different user name.
METER: Measurements obtained on 1000 hours of usage during testing.
MUST: 100% of the time.
ID: QR18
TAG: RestaurantOwnerCreateAccountSecurity
GIST: The security of creating account for restaurant owners of the system.
SCALE: If a restaurant owner wants to create an account and the desired user name is occupied, the
restaurant owner should be asked to choose a different user name.
METER: Measurements obtained on 1000 hours of usage during testing.
MUST: 100% of the time.
25
3.5.4 Maintainability
ID: QR19
TITLE: Application extendibility
DESC: The application should be easy to extend. The code should be written in a way that it favors
implementation of new functions.
RAT: In order for future functions to be implemented easily to the application.
DEP: none
ID: QR21
TITLE: Application testability
DESC: Test environments should be built for the application to allow testing of the applications different
functions.
RAT: In order to test the application.
DEP: none
3.5.5 Portability
ID: QR20
TITLE: Application portability
DESC: The application should be portable with iOS and Android.
RAT: The adaptable platform for the application to run on.
DEP: none
26
27
The second release also includes important requirements. However, these requirements are not vital for a
functional application. They are more suited to act as additional features that can contribute to making the
software product more attractive.
The third release includes the requirements that can be afforded to discard if the project gets delayed or
overruns the budget.
For further details about the release plan, see Appendix IV.
28
47
FR2
28
FR3
44
FR4
39
FR5
41
FR6
10
10
10
10
66
FR7
10
10
10
10
64
FR8
10
10
10
10
64
FR9
51
FR10
39
FR11
31
FR12
40
FR13
47
FR14
34
FR15
41
FR16
39
FR17
28
FR18
36
FR19
35
FR20
40
FR21
34
FR22
47
29
FR23
43
FR24
10
10
10
58
FR25
28
FR26
45
FR27
55
FR28
41
FR29
40
FR30
29
FR31
10
50
FR32
47
FR33
27
QR1
49
QR2
44
QR3
43
QR4
45
QR5
35
QR6
10
56
QR7
57
QR8
49
QR9
10
57
QR10
27
QR11
28
QR12
55
QR13
40
QR14
47
30
QR15
46
QR16
53
QR17
38
QR18
42
QR19
49
QR20
45
QR21
45
QR22
54
QR23
49
31
Requirement ID Title
Requirement Type
FR6
Function
FR7
FR8
Function
FR24
Function
FR27
Function
QR6
Quality
QR7
System Availability
Quality
QR9
System Reliability
Quality
QR12
Communication Security
Quality
QR22
Internet Connection
Quality
Table 4 Value
Value FR6 FR7 FR8 FR24 FR27 QR6 QR7 QR9 QR12 QR22
FR6
1/3
1/5
1/3
1/3
FR7
1/5
1/5
1/3
1/3
1/3
FR8
1/7
1/3
1/6
1/4
1/4
1/5
FR24
1/7
1/5
1/4
1/3
1/5
1/5
1/3
FR27
1/6
1/5
1/9
1/5
1/5
1/7
QR6
32
QR7
1/3
1/3
QR9
1/3
1/3
1/3
QR12 1/5
1/5
1/2
QR22 1/7
1/5
1/3
1/4
1/2
1/8
1/7
1/5
1/9
Table 5 Cost
COST FR6 FR7 FR8 FR24 FR27 QR6 QR7 QR9 QR12 QR22
FR6
1/5
1/2
1/7
1/3
1/5
1/3
FR7
1/5
1/5
1/3
1/5
FR8
1/9
1/5
1/6
1/5
FR24
1/3
1/7
1/3
1/3
1/5
FR27
1/5
1/3
1/5
1/3
1/7
1/6
1/7
1/6
QR6
QR7
1/2
1/3
QR9
1/2
1/2
QR12
1/3
1/5
1/3
1/3
1/3
QR22
1/7
1/5
1/2
1/9
1/7
1/5
1/5
33
34
FR6
Cost
Value
5,31%
13,60%
FR7
9,18%
7,12%
FR8
FR24
7,91%
4,80%
7,65%
5,93%
FR27
QR6
QR7
QR9
QR12
35
QR22
3,71%
1,53%
Requirement
ID
Priority by Stakeholder
User
FR1
1
1
1
1
1
1
Restaurant owner
-2
-1
-2
-2
-1
-1,6
1
1
0
-1
0
0,2
Restaurant owner
-2
-1
-2
-2
-2
-1,8
1
0
1
0
1
0,6
Restaurant owner
-2
-2
-2
-2
-2
-2
0
0
1
0
0
0,2
Restaurant owner
-2
-2
-2
-2
-2
-2
1
1
0
Restaurant owner
-2
-2
-2
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Administrator
-2
-2
-2
-2
-1
-1,8
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
Customer
1
1
1
0
0
0,6
-3
1
1
0
1
1
0,8
-2,4
0
0
0
-1
0
-0,2
-4
41
User
FR5
Customer
29
User
FR4
Administrator
-2
-2
-2
-2
-2
-2
2
2
1
1
1
1,4
-1
34
User
FR3
Customer
13
User
FR2
Administrator
-2
-2
-2
-2
-1
-1,8
Magnus
Elmira
Niclas
36
0
0
-1
Faegheh
Sarah
Average
Sum
-1
0
0,2
-2
-2
-2
1
1
1
1
1
1
Restaurant owner
1
0
0
-2
0
-0,2
1
1
1
1
0
0,8
Restaurant owner
-2
0
-2
-2
-2
-1,6
1
1
0
0
0
0,4
Restaurant owner
1
1
1
1
1
1
1
1
2
2
2
1,6
Restaurant owner
-1
0
-2
-2
-1
-1,2
1
1
Restaurant owner
-1
0
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
Customer
1
0
-2
-1
0
-0,4
-3,2
1
1
-2
1
1
0,4
-0,2
0
0
-2
0
1
-0,2
-1,8
18
User
FR13
Administrator
-2
-2
-2
-2
-2
-2
1
2
-1
1
0
0,6
-0,6
5
User
FR12
Customer
36
User
FR11
Administrator
-2
-2
-2
-2
-2
-2
8
User
FR10
-1
-1
-0,6
-4,4
42
User
FR9
-2
-2
-2
Magnus
Elmira
37
0
0
Niclas
Faegheh
Sarah
Average
Sum
2
2
2
1,6
-2
-2
-1
-1,2
1
0
1
0
0
0,4
Restaurant owner
-1
-2
-2
-2
-2
-1,8
1
1
1
1
1
1
Restaurant owner
-1
0
-2
-2
-1
-1,2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
1
1
1
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
0
1
0,8
Rank of
Req.
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
Customer
1
0
-2
0
1
0
-2,2
Restaurant owner
-1
0
-2
-2
-2
-1,4
1
0
-2
-1
1
-0,2
-2,6
Restaurant owner
-1
0
-2
-2
-1
-1,2
1
-1
-2
-1
0
-0,6
-3
35
User
FR18
Administrator
-2
-2
-2
-2
-2
-2
1
-1
1
0
0
0,2
-3,2
31
User
FR17
Customer
24
User
FR16
Administrator
-2
-2
-2
-2
-2
-2
37
User
FR15
-2
1
1
0
-1,6
17
User
FR14
-2
-2
-2
-2
Magnus
38
Restaurant owner
-2
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
2
1
1
1,4
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
1
1
1
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
2
1
1
1
1,2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
0
1
0
-1
0
0
Rank of
Req.
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
Customer
1
0
-2
-1
0
-0,4
-3,4
Restaurant owner
-2
-1
-2
-2
-2
-1,8
1
1
-2
0
0
0
-2,6
Restaurant owner
-2
-2
-2
-2
-2
-2
0
0
-1
-1
0
-0,4
-4,4
43
User
FR22
Restaurant owner
-2
-2
-2
-2
-2
-2
32
User
FR21
1
0
-1
0
0,2
-2,2
38
User
FR20
-2
-2
-2
-2
-2
25
User
FR19
-1
-2
-2
-2
-1,8
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-2
-2
-2
-2
Rank of
Req.
Restaurant owner
2
2
2
2
2
2
2
2
1
2
1
1,6
-0,4
6
User
Restaurant owner
39
FR23
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-2
-2
-2
-2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-2
-2
-1
-1,8
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-2
-2
-2
-2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-1
-2
-1
-1,6
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
2
1
2
2
2
1,8
Customer
Administrator
1
0
2
2
1
1,2
Customer
Administrator
1
0
2
2
1
1,2
Customer
1
0
-2
-1
0
-0,4
-3,4
Restaurant owner
-2
-2
-2
-2
-2
-2
1
0
1
1
1
0,8
-1,4
Restaurant owner
0
1
1
-1
0
0,2
1
1
0
1
1
0,8
0,6
2
User
FR29
Restaurant owner
1
1
1
0
1
0,8
16
User
FR28
2
1
1
1
1
1,2
-1
39
User
FR26
-2
-2
-2
-2
-2
-2
14
User
FR25
1
2
2
2
2
1,8
-2
-2
-1
-2
-1
-1,6
Rank of
Req.
Restaurant owner
0
1
1
-1
0
0,2
3
40
1
1
0
1
1
0,8
0,6
User
FR30
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-1
-2
-2
-1
-1,6
Restaurant owner
0
0
0
1
1
0,4
0
0
0
0
0
0
Restaurant owner
-2
-2
-2
-2
-2
-2
-2
-2
-2
-2
-2
-2
Restaurant owner
0
0
0
1
0
0,2
-2
-2
-2
-2
-2
-2
Restaurant owner
-2
-2
-2
-2
-2
-2
2
2
2
2
2
2
Restaurant owner
-2
-2
-2
-2
-2
-2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
Administrator
1
0
2
1
1
1
Customer
Administrator
0
0
0
0
0
0
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
1
1
0
0
1
0,6
-0,4
1
1
0
1
1
0,8
0
0
0
-2
-1
0
-0,6
-4,6
44
User
QR1
Customer
4
User
FR33
Administrator
1
0
2
1
1
1
1
1
0
1
1
0,8
1,2
7
User
FR32
Customer
1
User
FR31
Administrator
1
1
2
2
2
1,6
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
10
41
2
2
0
1
1
1,2
-0,8
Req.
User
QR2
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
2
2
2
2
2
2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
0
1
0,8
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
1
1
1
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
1
0
0,8
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Restaurant owner
-2
-1
-1
-1
-1
-1,2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-1
-1,8
Customer
1
1
0
-1
1
0,4
-2
Restaurant owner
-2
-1
-1
-1
-1
-1,2
1
1
0
0
0
0,4
-1,8
Restaurant owner
-1
-1
0
1
-1
-0,4
1
1
-2
-1
0
-0,2
-1,8
20
User
QR8
Administrator
-2
-2
-2
-2
-2
-2
2
2
0
1
1
1,2
-0,8
19
User
QR5
Customer
21
User
QR4
Administrator
-2
-2
-2
-2
-2
-2
11
User
QR3
Restaurant owner
-2
-2
-2
-2
-2
-2
1
1
1
1
0
0,8
42
Restaurant owner
-2
-2
-2
-2
-1
-1,8
1
0
2
0
0
0,6
-2,2
Rank of
Req.
26
User
QR10
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-1
-1
-1
-1
-1
-1
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-1
0
-1
-1
-1
-0,8
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-1
-2
-2
-2
-2
-1,8
Customer
Administrator
2
1
2
2
1
1,6
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
-1
0
-1
-1
0
-0,6
-5,6
-1
0
-1
-1
-1
-0,8
-5,6
-2
-2
-2
-2
-2
-2
Restaurant owner
-2
-2
-2
-2
-2
-2
-2
-2
-2
-2
-2
-2
Restaurant owner
0
0
1
0
1
0,4
2
1
2
1
1,5
-0,7
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
Rank of
Req.
2
1
2
2
1
1,6
-0,8
12
User
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
-2
-2
-2
-2
-2
-2
-2
User
QR15
Restaurant owner
-2
-2
-2
-2
Restaurant owner
2
1
2
2
1
1,6
Rank of
Req.
QR14
Customer
46
User
QR13
Administrator
-2
-2
-2
-2
-2
-2
45
User
QR11
Restaurant owner
-2
-2
-2
-2
-2
-2
43
-1
2
2
2
1
1,2
Sum
-2,4
Rank of
Req.
30
User
QR16
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-2
-2
-2
-2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
2
1
1
0
0
0,8
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-2
-2
-2
-2
-2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-1
-2
-2
-1
-1,6
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Restaurant owner
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
Administrator
-2
-2
-2
-2
-2
Customer
0
2
2
1
1
1,2
-2
Restaurant owner
2
1
1
0
0
0,8
0
2
2
1
1
1,2
-2
Restaurant owner
-2
-1
-2
-2
-1
-1,6
2
2
1
2
1
1,6
-3,6
40
User
QR20
Administrator
-2
-2
-2
-2
-2
-2
-1
2
2
0
0
0,6
-2,8
23
User
QR19
Customer
22
User
QR18
Administrator
0
0
1
1
0
0,4
33
User
QR17
Restaurant owner
-2
-1
-2
-2
-2
-1,8
0
0
1
1
-1
44
Restaurant owner
-2
-2
-2
-2
-1
2
2
1
1
1
Average
Sum
0,2
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
-2
-1
-2
1
-1
-1
Rank of
Req.
Magnus
Elmira
Niclas
Faegheh
Sarah
Average
Sum
1
1
1
1
1
1
Rank of
Req.
Requirement ID
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
FR30
FR28
FR29
FR32
FR11
FR22
FR31
FR9
QR13
QR1
QR2
QR14
FR1
FR23
QR23
FR26
FR13
FR12
QR4
QR5
Restaurant owner
-2
-1
-2
-2
-1
-1,6
Restaurant owner
-2
0
-2
-2
-1
-1,4
15
Priority
1,4
-2,2
Administrator
-2
-1
-2
-2
-1
-1,6
Customer
Administrator
-2
-2
-2
-2
-2
-2
Customer
2
2
2
2
2
2
-2,2
28
User
QR23
-2
27
User
QR21
-1,8
45
1
2
1
1
1
1,2
-1,2
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
QR3
QR17
QR18
FR15
FR18
QR8
QR20
QR21
FR3
QR15
FR16
FR20
QR16
FR2
FR17
FR10
FR14
FR19
FR25
QR19
FR4
FR5
FR21
FR33
QR10
QR11
46
RE:
FR1
FR2
FR3
FR4
FR5
FR6
FR7
FR8
Dependencies
Description
Motivation
Download
mobile
application
FR1
FR1, FR3
FR1
FR4
FR6, QR22,
QR23
FR6, QR22
Release
Duration
80
Download and
notify users of
new releases
User
registration
User Log-in
Retrieve
Password
Search
Search result in
a map view
Search result in
a list view
47
FR10
FR11
FR12
FR7, FR8
FR7, FR8
FR7, FR8
FR8
FR13
FR7
FR14
FR12, FR13
FR15
FR16
FR17
FR7
FR7
FR6
Navigation to
restaurant
Switch result
view
Selecting the
information
link
Search by price
Search by
destination
Accepted input
for price and
destination
search
Search by
restaurant type
Search by
specific dish
Free-text
search
48
users.
FR18
FR5
FR19
FR8
FR20
FR7, FR8
FR21
FR1
FR22
FR23
FR27
FR24
FR25
FR23, FR25
No search
match found
Filtering
results
Profile page
Create account
- restaurant
owner
Log-in restaurant
owner
Selecting
preferred
language on
the web-portal
- restaurant
owner
Sorting results
49
FR26
FR27
FR28
FR29
FR30
FR26, FR22
FR26
FR26
FR26
Log-in - admin
Verify
restaurant
owner
Manage rest.
types administrator
Manage rest.
dished administrator
Manage rest.
info administrator
FR31
FR26
FR32
FR26
Selecting
preferred
language on
the web-portal
- administrator
Language
selection on
portal
Prominent
search feature
The ease of
usage of the
search feature
FR33
QR1
QR2
FR26
50
QR3
QR4
QR5
QR6
QR7
QR8
QR9
QR10
QR11
The ease of
usage of the
result in the list
view
This is a high-prioritized
requirement. But we have decided to
put this in the second release in favor
for more vital and higher prioritized
requirements.
The ease of
usage of the
result in map
view
This is a high-prioritized
requirement. But we have decided to
put this in the second release in favor
for more vital and higher prioritized
requirements.
The ease of
usage of the
information
link
System
response time
System
availability
QR22, QR23,
FR14, FR15,
FR16, FR17
System
dependability
System
reliability
Application
hard drive
space usage
Application
memory usage
51
QR13
QR14
QR15
QR16
QR17
QR18
QR19
QR20
QR21
FR22
FR23
FR3
FR22
Communicatio
n security
Non-existing
account
security for
rest. Owners
Non-existing
account
security for the
administrators
Log in security
for rest.
Owners
Log in security
for
administrators
User account
creation
security
Restaurant
owner account
creation
security
Application
extendibility
Application
portability
50
Application
testability
30
52
system expands.
QR22
QR23
Internet
connection
GPS
connection
53
54
Appendix V: I-star
Figure 12 SD diagram
55
Figure 13 SR diagram
56