ITAP2013 Software Engineering Report: Dinning Closely Application

This software engineering report provides a comprehensive analysis of the "Dinning Closely" GPS-based application. It begins with an introduction outlining the application's purpose, which is to assist users in finding nearby restaurants and making reservations. The report then defines the scope, constraints, and assumptions related to the application, followed by a detailed discussion of both functional and non-functional requirements. Stakeholders, including users, restaurant owners, and administrators, are identified. Project management aspects, such as time, deliverables, quality, and risk assessment, are also covered. The report includes a use case diagram and descriptions, along with a class diagram illustrating the application's structure. Finally, the report presents a user interface overview and references. The application allows users to find restaurants, check availability, book tables, and potentially order food and pay online. Restaurant owners can update restaurant information through a web portal, and the administrator ensures the accuracy of the data.

Running head: SOFTWARE ENGINEERING
SOFTWARE ENGINEERING
Name of student
Name of university
Author’s note:

1
SOFTWARE ENGINEERING
Table of Contents
1. Introduction:.........................................................................................................3
1.1 Purpose:................................................................................................................3
1.2 Scope:...................................................................................................................3
1.3 Definition, Acronyms:..........................................................................................4
2. Constraints:................................................................................................................5
3. Assumptions:..............................................................................................................6
4. Requirements:............................................................................................................6
4.1 Functional Requirements:....................................................................................6
4.2 Non Functional Requirements:............................................................................7
4.3 Other:....................................................................................................................7
5. Stakeholders:..............................................................................................................7
6. Project management...................................................................................................8
6.1 Time:....................................................................................................................8
6.2 Deliverables and Milestones:...............................................................................8
6.3 Quality:.................................................................................................................8
6.4 Risk Register:.......................................................................................................8
7. Use case diagram......................................................................................................11
8. Use case description.................................................................................................11
Use case description 1..............................................................................................11
Use case description 2..............................................................................................12
Use case description 3..............................................................................................13
Use case description 4..............................................................................................14
9. Class diagram...........................................................................................................16
10. User interface.........................................................................................................17
11. References:.............................................................................................................21
12. Appendix................................................................................................................22

2
SOFTWARE ENGINEERING
1. Introduction:
This document describes the GPS application used in the smart phones. Using this
application is quite advantageous as it provides various services which runs online.
1.1 Purpose:
The purpose of the document is provide the detailed information of the web
application called “Dinning Closely”, which is a Global Positioning System based
application. This document also aimed at describing the limitations, assumptions and
the functional requirements of the application. This document will be assisting to create
a proposal for the customer which requires approval. The purpose of the system is to
provide better service to find the restaurants with associated information.
1.2 Scope:
The scope of this mobile application is to help the users to find the nearest restaurants
according to the location of the user with necessary details. The availability details can
also be checked such as if seats are empty or not so that the user can book a table as per
the needs.
The payment transactions through online has the made the service of the application
better. Moreover, the restaurant owners can provide the relevant information of their
restaurants through the web-based portal since, the administrator is also involved it is
assured that information will be accurate as the administrator focuses on the correctness
of the data provided.

3
SOFTWARE ENGINEERING
To make the application run smoothly, the internet and GPS connection should be
enabled in the smart phones. As the software uses the GPS navigator which help to
track the restaurants online, all the data are fetched from web hence, availability of the
internet is must. At the back end process of the system, database is used to maintain
information from which the restaurant details are fetched or tracked.
1.3 Definition, Acronyms:
Users or Customers- The users will use the GPS based application through their smart
phones, the application need to be installed in the smart phone with other software or
features such as GPS connection, GPS- navigator software as there is requirement of
tracking the details and location through map.
GPS- Global Positioning System
GPS-Navigator It is a software which is need to be installed on mobile phones.
The Restaurant owner- monitors the activities of the restaurant and provide the details
of the information through the web application.
The Administrator- The person who is responsible to control and monitor the system
ensures that proper details of the restaurants is shared only after the permission. The
web based system or the web portal is handled by the administrator.
The web portal- the web based system that is used by the Restaurant owner serves
satisfaction as the information can be accessed by them for which the owner just need
to do the login.

4
SOFTWARE ENGINEERING
Application- The applications can be downloaded from the application store on the
smart phones in order to use the services.
Database- The information is stored in the database which is fetched through the web
server. The information system is handled the administrator and restaurant owner.
Web server- It is program or system which delivers information or content to the client
system, whenever a user or client searches for anything the web server provides the
matched data to the user.
2. Constraints:
Constraints refers to the limitation the software of application can have. According to
this scenario the web-based application that is used by the customers need to internet
connection and the smart phones should support the GPS facility. GPS is the technology
which uses radio navigation system i.e. it deals with the radio waves and satellites (Parmar et
al., 2013). The GPS receivers that is present is the smart phones receives signals to fetch the
data for tracking.
To use the application, first of all the user need to download it from the application
software. After downloading the application, the user need to login by creating an account.
Moreover without the internet availability the application cannot run on the phones as it will
not be able to fetch the information from the web.

5
SOFTWARE ENGINEERING
3. Assumptions:
It can assumed be that the application would fetch accurate data and the information
maintained by the restaurant owners are accurate. And the application can be downloaded
without paying any charge. The performance of the application is better than any other
similar application. The smart phones having the GPS features can have different interfaces
according to different smart phones hence, the application need to set according the
respective interfaces.
4. Requirements:
4.1 Functional Requirements:
 The ‘Dinning closely’ application need to be downloaded from the application
store.
 Availability of the internet and GPS navigator on the mobile phones
 The application system can notify the users or customers about the new
restaurants or dishes in any particular restaurants or even the availability of the
seats in the restaurants.
 Registration and login in in the application after downloading form the store
 Appropriate search options such as available restaurants, dishes, available
seats, price, etc.
 Display of the map with proper facility of zoom-in and zoom-out.
 Display system of the application should be attractive with proper menu and
options.
 Link of the restaurant should be proper I order fetch correct information

6
SOFTWARE ENGINEERING
4.2 Non Functional Requirements:
The non-functional requirements of the application can be the Performance, easy
access service, accurate data is fetched, availability of data, maintenance. The performance of
the application depends on these requirements, if the requirements are fulfilled then the
performance will be better.
4.3 Other:
The tracking system should work properly otherwise the system would not work
properly. The GPS navigator should track from the web. Best restaurants should be
recommended with proper ambience and food and good restaurant owners. These are filtered
according to the general ratings given to the restaurants by other customers.
5. Stakeholders:
The major contributors of the application software are the users, restaurant owners,
any project investor or organization (Broekx, 2013). The stakeholders plays an important role
to contribute in to the system, users and restaurant owners are the major stakeholders. If any
project investor gets attracted by the features of the application can dealing can be done to
enhance and expand the service.

7
SOFTWARE ENGINEERING
6. Project management
6.1 Time:
The response time of the application is an important factor (Kerzner, 2017). The software
should be delivered on time moreover, the performance of the application plays an important
role to work within a quick response. The detecting procedures, navigating procedures all
should work well.
6.2 Deliverables and Milestones:
Deliverables are itself the milestones which works for the development of the
application (Conforto & Amaral, 2016), which are, User Interface design and web-based
frames, welcome screen and registration page, functional documents which involves the
documentation of the application and software. Software would be delivered after proper
testing, maintenance and supporting facilities.
6.3 Quality:
The quality of the application depends on the performance, faster response with
fetching of accurate data. The user interface design should be attractive and easier in order to
serve best quality (Mir & Pinnington, 2014). The web-portal that is used the restaurant
owners should be easily handled with proper connection with the database.
6.4 Risk Register:
Risk refers to the potential that interrupt the running of the project successfully (Lam,
2014). Proper management of risk is very essential to efficiently run any project.
Sl. No. Risks Risk description Impact Probability

8
SOFTWARE ENGINEERING
1 Budget escalation If the budget and cost gets overrun then
the inflation in the company or
organization can occur(Winch, 2013)
V H H
2 Timeline Risk timeframe should be analysed
properly in order to build mitigation
processes
H H
3 Less number of
participants
Less participants can lead to less research
and work load can also increase for the
active performers
V H M
4 Network issues Can lead to run the application slow and
fetching can get interrupted
H L
5 Less number of
companies
The profits become less if there are less
companies to do the investment
V H V L
6 Entrance and exit
at on-ground
venue (Liang et
al., 2017)
If the safety and health measures are not
applied in the organization then it can
affect the efficiency
H L
7 Accidents at on-
ground venue
It again relates to the health and safety
measures
H V L
8 Natural calamities Back-up planning should be there if any
natural disaster occur to retrieve the
whole process
V H V L
9 Improper
management
Poor management lead to make the
project overrun scope, time and budget
H M
10 Lack in resources Project manager is responsible to collect
the resources such as finance, employees,
time. If not controlled properly then the
project may become inefficient (Cleden,
2017)
M V L

9
SOFTWARE ENGINEERING

10
SOFTWARE ENGINEERING
Probability
V H 5, 8 3 1
H
7 4 9 2
M
6
L 10
V l
V L L M H V H
Impact

11
SOFTWARE ENGINEERING
7. Use case diagram
Figure 1: Use case diagram of Dining closely
Source: (Created by author)
8. Use case description
Use case description 1
Use Case Login
Summary The customer opens the application of any restaurant for making
booking
Actor Customer