Annual Report

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. Purpose The purpose of this document is to give a detailed description of the requirements for the “Tahal” device. 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. Scope “Tahal” is an automated board with a mobile application which helps users to travel based on their specified location. The mobile application is available only to people owning the “Tahal” board. Users can provide the location they would like to visit. This information will act as the bases for the search results and “Tahal” board will take users automatically to defined location across a user selected path without any manual effort. The user can also change the path later by commanding “Tahal” Assistant. Furthermore, the software needs both Internet and GPS connection to fetch and display results. The device has the capability of taking turns, instantaneous response to obstacles, speed control.

Overview

This document includes three parts. The second one provides an overview of the system functionality and system interaction. This part also mentions the system constraints and assumptions about the product. The third part provides the requirements specification in detailed terms and a description of the different system interfaces.

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 works and introduce the basic functionality of it. The constraints and assumptions for the system will be also presented.

Product perspective

Figure 1 Block Diagram This system will consist of two parts: one mobile application and one board. The mobile application will be used to search locations; set paths’ while the board will be used for an actual movement like skateboarding and as a whole it will make an automated board. The mobile application will need to communicate to a GPS application within the mobile phone, which in turn communicates with a physical GPS device to find the location of the user. The GPS will provide the mobile application with locations of both the user and the final destination and the path between them.

Product functions

With the mobile application, the users will be able to search for visiting locations. The result of the search will be viewed in a map view. The map view will show each location as a pin on the map as well as the user’s own location.

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 provides. 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.

Assumptions and dependencies

One assumption about the product is that it will always be used on mobile phones that have enough performance. If the phone does not have enough hardware resources available for the application, for example the users might have allocated them with other applications, there may be scenarios where the application does not work as intended or even at all. Another assumption is that the GPS components in all phones work in the same way. If the phones have different interfaces to the GPS, the application need to be specifically adjusted to each interface and that would mean the integration with the GPS would have different requirements than what is stated in this specification.

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.

External interface Requirements

This section provides a detailed description of all inputs into and outputs from the system. It also gives a description of the hardware, software and communication interfaces and provides basic prototypes of the user interface.

User interfaces

A first-time user of the mobile application needs to register for using “Tahal” application which is only possible with a pin number assigned to avoid unauthorised access. A user can search for the location using the search bar. The map view shows each location by a pin, you can zoom into to check the available paths to follow your desired location. Hardware interfaces The hardware component of the system is the board which may conventionally look like a skateboard but works without any manual effort all with the use of GPS device which connects to both mobile phone and the device that feeds the data in the processor. Thereafter processor controls the motor and rotates the wheel to move forward take turns adjust speed.

Software interfaces

The mobile application communicates with the GPS application in order to get geographical information about where the user is located and the visual representation of it, and with the database in order to get information about the pointed location. Functional requirements This section includes the requirements that specify all the fundamental actions of the software system. User Class 1 - The User

Functional requirement

1.1 TITLE: Download mobile application.

DESCRIPTION: A user should be able to add the application through a shared link. Functional requirement 1.2 TITLE: User registration -Application DESCRIPTION: Given that a user has downloaded the mobile application, then the user should be able to register through the application using a given pin number.

Functional requirement

1.3 TITLE: Application - Search DESCRIPTION: Given that a user is logged in to the mobile application, then the user should be able to search for locations. A user should be able to select desired path options.

Functional requirement

1.4 TITLE: Mobile application - Search result in a map view DESCRIPTION: Search results can be viewed on a map. On the map, the relevant information according to the user’s position and movement status are shown. A specific pin will represent destined location. Another will represent user location.

Functional requirement

1.5 TITLE: Mobile application - Navigation DESCRIPTION: When a selection is made, the final location should be sent to the mobile phone’s GPS-navigation program. The user should then be navigated to the destination. Performance requirements The requirements in this section provide a detailed specification of quality of the user interaction

Prominent search feature TITLE: Prominent search feature DESCRIPTION: The search feature should be prominent and easy to find for the user.

Usage of the result in the map view TITLE: Usage of the result in the map view DESCRIPTION: The results displayed in the map view should be user friendly and easy to understand. Selecting a pin on the map should only take one click. System dependability TITLE: System Dependability DESCRIPTION: The fault tolerance of the system. If the system goes into some fault, it should slow down and stop in response to fault.

Safe travel option TITLE: Safe travel option DESCRIPTION: The board should be capable of responding to immediate obstacles. Speed Control TITLE: Speed Control DESCRIPTION: The user should be capable of controlling the speed from user interface. Prioritization and Release Plan and Software Models Software Models In order to get a view of how to divide the requirements and what requirements should be best suited prototype model is best opted for making of this device. Prioritization and Release Plan

First a prototype will be made to check the implementation of the functionality. After successful testing of object response, speed limits a human sized riding board will be made and henceforth that too will be tested at different speeds on different course paths. After satisfying test results the board will be released as a complete project. Figure 2 Functionality Diagram